Exporting / Storing & Reading back automations and data flow from Live
Sep 08 2020 | 10:18 am
Hi dear C74 community, I'm working on a way to do offline rendering also with Max. (for reference purpose, the thread related to the jitter part here is there)
As my visuals react to some external bits (sound analysis, midi triggers, midi CC curves), I have to find the best way to record (or export) all these bits ( sound analysis, midi triggers, midi CC curves ) and to make my patch able to read it back while offline rendering. Live is used for the sound part, here. For automations, midi triggering, I have some options in mind : - exporting by using a max for live based patch: you select the clip (or the track) from which you want to store data and it exports things. Actually, I don't see any benefits from this compared to export MIDI files (as far as I can imagine right now) - exporting Clip as MIDI files - recording flows from Live to Max (using MuBu library maybe)
For sound analysis, I just saw that MuBu library can do it (and store it) realtime or not realtime. In my setup, I often use sound analysis only for some tracks... so I can easily do it and store it, I think. The idea is: it as to be the most accurate possible. Considering that jitter rendering, if I go to 60fps, or even 120fps while rendering not real time, it means I'd need 120 values to be read back per second... this is low sampling rate. BUT for instance, I have a midi trigger occuring NOT at the exact time position, it wouldn't be considered. Would require some quantization maybe.. could be a mess to design.
If some people have some experiences with that, I'd be happy to read any feedbacks and patches about this. If I end up with something decent, I'll share it here.
Thanks and take care, Julien