We are back again and a new Pre-Release 2.2.1 is online. You can download it here. If you found new bugs or bugs which are not fixed, please create a new thread and title it with [2.2.1y].
This version improved the Chase situation for DMX and MIDI. We have realised that there are many wishes about the Chase situation.
Global “Chase Events” control to the Preferences
It’s now possible to enable and disable “Chase Events” for MIDI and DMX.
I tested it again by deleting the old stack, deleting the inputs on the track and re-registering them, the automation worked correctly, I don’t know how to explain it, but it works for now, I’ll test it again tomorrow
and again the automation stopped working as in my video above, I don’t know what’s going on in version 2.2 everything works perfectly
Unfortunately, multi-processing is still broken for me on a Mac Studio with an M1Max processor. As soon as I activate it, the performance meter shows constant spikes, and the audio plays with continuous distortions or crackles. I deactivate it and everything works normally.
@Cucuso at toggle MP you will surely notice a CPU spike, you might rather hit STOP first, toggle, hit PLAY i guess. Does it makes diff?
Tested, but can’t find such. Tell me a few words how your signal flow looks like, how FX-'s are distributed (4pcs in STACK… or there are a few in the track, that goes to… etc…)
Hi @Spork …and 2.2.1 fixed a hidden issue I was struggling a while (…, I know…):
earlier replaced a “master FX” in my live proj, saved, reopened and “old FX” was present insted of the “new FX”.
But seems 2.2.1 is saving this correctly (thank you!)
there is one thing, that I can’t repro with a sandbox-blank project, just with my “LIVE proj”: the video-view1 appears me at every single project loading despite of having “auto-load” and “open-fullscr” OFF !! so my first reacting for a few weeks were… oh, what happened… these days I know… I need to close that blank window first (of course if not using it).
@fkalmusI have tried all possible ways, but with multiprocessing enabled it doesn’t work. Even enabling multiprocessing. Closing the program. Restarting the system. Opening VST Live. New project. Empty. It already shows jumps in the CPU meter. I load a song with an audio track, without any effects. Noises and cracks. I disable multiprocessing and everything works perfectly. Without multiprocessing I load large projects and the CPU load is minimal. I’m on a Mac M1 max. For now it’s not a big problem, since I can work without activating multiprocessing, it just seemed strange to me, since others have commented that as of this version multiprocessing is working ok.
