The multiple midi tracks in Scaler 3 cannot be routed to separate tracks in Ableton Live, as Ableton doesn’t support this feature. I tried to run plugins within the single Scaler track in Ableton, but this doesn’t work.
I am running Ableton on an Mac Studio M1 Max, with tons of RAM and easy buffer settings. With just 2-3 vst plugins running within the Scaler track, the CPU useage of Ableton spikes to 100%, and Ableton crashes. Per my understanding, a single Ableton track will only use one performance core of the CPU. Thus, a single Ableton track running Scaler 3 with multiple plugins will overload this single CPU core, and crash the system. Consequently, the idea to run all the Scaler midi lanes in one track, with multiple plugins, is a nonstarter for Ableton users!
Please add back the Scaler 2 feature, in which multiple instances of Scaler can run on separate tracks at the same time, and the track data updates from the master track, as the master track is changed.
I think it was a very bad idea, to remove the Scaler 2 multitrack feature from Scaler 3. For Ableton users, the best part of Scaler 3 (running multiple instrument tracks simultaneously) is non-functional.
The “drag your midi into your DAW” solution is not a real solution to this problem.
All good @ScaleyDude This feature is being introduced in 3.1 which will be here around mid April. It’s worth pointing out that everything in Scaler 3 is rebuilt from the ground up. So it’s not a case of leaving things out but whether we reintroduce them. I wanted Live Sync as a Logic user of MIDI FX plugins but the team felt strongly about the mitigating factor of Live Sync not being needed due to multitrack hosting and Multi channel midi out.
Quite surprising to see the Ableton community miss this feature and be quite vocal about it so we have prioritised this!
Thank you… much aporeciated. I’ve spent several hours, trying to find workarounds with other plugins, and trying to route Scaler 3 midi data from Logic to Ableton. Nothing works!
I also looked into workarounds for this in Ableton this weekend (also tried writing a patch in Max MSP) and haven’t found an ideal solution. Thanks for looking into this!
A quite simple solution would be to have a secondary VST named “Scaler Midi Receiver” that receives midi notes from the main plugin instance. The receiver could be a simple interface where you select which track to listen to from the main instance. I’ve seen this cross-plugin communication model in some other plugins like the ones from Izotope and have liked the design pattern. It could be a very lightweight solution so that you don’t need a bunch of full plugin instances on each track.
I thought you might appreciate this idea. Thanks again for looking into it.
Yeah, JRoot3d I actually found your max patch earlier. I tried fixing the saving issue in Max, but the vst~ object in max doesn’t seem to work with pattrstorage. So you have to remember to manually save your work in scalar as a new preset before you close the project. It was still very helpful though!