Awesome! Where is the max for live download link? Great work 
This is my under-development project
I’m trying to fix some issues 
2 Likes
So sick!! Can’t wait until it’s out. Thank you for taking the time
NEVERMIND it doesn’t work so far only my method; Scaler state isn’t saved inside of the wrapper 
Only my original method works not this one
UPDATE WITH MAX4LIVE: Reddit - The heart of the internet
this is a great solution
but Scaler 3 doesn’t save the state inside this wrapper
If you make the mistake and save the project… it never opens again… It opens and it shows the scaler window for a split second and then Ableton Crashes. I had to load an empty project and drag the items manually in order to be able and make the project usable again.
1 Like
Very interesting.
If you need testing please send us a link. Beware that Multi-Midi VST Wrapper crashes ableton in you open a saved project.
1 Like
I use it at the moment with latest Beta of Live 12. No Problem to load and save Projects in Live. No Crash when opening Scaler3 from the m4l device.
Only important is that you have to save your work in scaler as a preset. If not all is gone after reopening the live project because you get an empty Scaler 3.
MacOS: seqouia 15.3.2
WIP. Trying to fix the issue with saving Scaler 3 state.
1 Like
This is not such a huge issue since we can save the state inside scaler. It may not be perfect but at least it works.
Hi Michael, I tried this and it works - BUT when I save the project and then reopen, it crashes Ableton 12. I have one instance of wrapper with Scaler 3 chosen, Bus 1.
I appreciate all the efforts in workarounds and trying to address a massive shortfall in Ableton.
Can I ask though, wouldn’t this just be all solved with multiple syncable instances?
No need to route MIDI on channels, just have multiple instances serving different instruments?
It’s exactly what I do in Scaler 2.
I find it much more convenient and efficient to have all tracks in the arranger, rather than having to jump between different instances of Scaler.
I guess it reminds me of the old maxim:
“Everyone loves innovation, but hates change…”
1 Like
It’s an innovation that isn’t working though
After many tries and tests
Impossible to save Scaler 3 state inside Max4Live wrapper
Scaler doesn’t send all needed data to Max
Great work though mate, do you have a page for your Max stuff and maybe to donate? I’ve been using a wrapper by another developer allowing an instrument and midi on the same lane which halved my Ableton channels
Edit: just seen your links above…cheers
Not working for you, that is…
I personally find it a great improvement over Scaler 2 and, judging from a large number of comments I have seen, so do many others.
There are some bugs and issues but I would rather the team delivered a minimum viable product quickly, rather than spend forever aiming for perfection.
Also, just like Scaler 2 was, it will be enhanced and refined over time.
3 Likes
Not just me, it’s quite a long thread - see above - and many other topics. There’s been quite a large drop of money based on the amount of users. Undoubtedly people work hard. There seems to be this really odd sense of lashing out when people question some issues. Very strange.
Glad that you like it, I want to also. It just doesn’t work for me at the moment. Is that ok?
1 Like
Of course that’s ok - I wasn’t suggesting it wasn’t.
Hopefully, some of the issues you have might be addressed in future updates. Once the chaos of the launch dies down perhaps you could suggest to the devs that they be put on the roadmap?
The real problem, however, lies with Ableton and their shoddy midi implementation…
1 Like
I think if we can get multi-sync in there you’d be happy right?
As @zzrwood Is pointing out we’ve been using it Ableton live for months. Sure, could things be easier with Main Track sync? Yes, but developing it would take a few weeks when there are so many other elements we were trying to get right. Probably didn’t foresee the strong demand from our Ableton users. I don’t think one of our Ableton beta testers mentioned it or lack of it In testing.
Some patience and understanding is appreciated here. I think this issue is one of the main things we’d like to get to. Let me come back to you with some news when I have it.
1 Like