@davide 
maybe you can point this midi issues again to Ableton. That’s what I done yesterday. But maybe you as a developer will have more impact on them.
2 Likes
Scaler 3 is a step forward in every respect. With a few teething troubles. And it is actually better in terms of the practical process as it has now been designed. It is a well-known fact that Ableton is the only product that makes noises here and is otherwise not accommodating to customers, as can be seen from ARA, which has probably been the most requested function for years. It would be more interesting if Scalermusic enabled data synchronisation with @JRoot3D and then delivered this as a package to Ableton users. But I’m not a technical expert.
I publish two M4L devices
2 Likes
Thanks a lot man!!! I really appreciate it… i just came to my office but today i think i wont work…
Trying now and get back… 
hi Davide and congratulations for the new version!!! It will wipe out everything else similar, i understand that its of outmost importance solving first the “Childhood diseases” especially the catastrophic ones. Although the multi-sync is almost of ultimate importance of Ableton users in order to be really usable.
Thanks a lot and keep up!!! 
Thank you we are on it. Will report back soon.
I love the open scaler button also that opens the app from any track!!!
Great job i reaaaaaaaaly appreciate it!
1 Like
Can you guys also add the option to stop sending MIDI from a Scaler track that’s been muted? Scaler 3 sending the MIDI for muted tracks has completely broken my particular workflow. I generally sketch out ideas track by track in Scaler and drag and drop the MIDI into my Ableton tracks for further editing. So like, I’ll have Scaler driving my chords track, I’ll come up with something, drag that from Scaler to the chords track, then disable Scaler’s input for that track and enable it on the next track I want to work on. Then I duplicate the original progression and use the editing section to assign the melody or bassline or whatever for the new track, get that where I want it, drag the MIDI to that Ableton track, rinse and repeat. This way I’m able to use a single Scaler instance without the need for sync. When I do this now though, as you know, MIDI from all the tracks gets sent to whatever track is using Scaler’s input.
1 Like
Until they implement that i suggest to use those two FREE M4L devices that work like a charm!
Just remember to save the scaler project before closing Ableton because currently the devices does not save the scaler state. Then you can disable scaler input through those devices.
https://forum.scalermusic.com/t/ableton-midi-routing-for-scaler-3/19586/65?u=omonymos
After toon hours of investigating maxforlive and wrapping plugins inside max, I have some summary.
Impossible to save state for plugins like Scaler, because max can save data that only can be mapped to CC or automation. Chord progressions and other data in Scaler are hard to bring to data type which can be saved inside the max wrapper.
Hey JRoot3D, just sent you a DM on how I adapted your wrapper to output the “native” scaler 3 sounds while sending midi to other tracks. Great stuff on your wrapper!!
1 Like
This solution is just for Suite and not Standard or Lite correct?
Suite and Standard with Max license
Hi JRoot3D, Could you share that solution? Thanks much.
Hi I just purchased my copy of Scaler and I really like it! I was also facing this challenge with Ableton.
Glad to hear its getting worked on. Hope this can get addressed soon 
There is a pretty serious and hidden issue in the device that makes Undo impossible.
For each track of scaler it creates undo things each time a chord changes for each instance of Receiver… i suppose its something that you can disabled in code?
Check for example the following image. In a complex project i got 5000-6000 undo things… that makes undo unusable in Ableton
That does work, thank you.
Just want to let everyone know that we are working on introducing ‘Live Sync’ to Scaler 3.1 which works similarly to Scaler 2.
This will sync your Main Track across all instances and across all DAWs.
ETA Mid April.
There’s also a 3.0.1 update coming next week with a few stability improvements and a few goodies…
12 Likes
Devices updated with fix.