“You can use it just like Scaler 2” and “The passmark for me was always that you can use it just like Scaler 2” I would say is unambiguous. You see this differently.
I would say “If you were seriously basing Davide simply saying”
“seek a refund and there you go”
“that is an assumption you made and now need to be good with”
“you simply made assumptions that did not come to pass”
…could be taken as defensive or aggressive language. I’m just not sure how previous posts have led to this.
In my case, I just hoped that SC3 was able to fix 2 issues I had with SC2, i.e. unreadable gray fonts and jumps in keys-lock notes, and just the first issue was fixed
And I also hoped in the option to edit MIDI patterns to kill the deja-vu effect, and this part seems improved indeed
BTW, I was a beta tester, so I was aware of those good and bad; notably I was aware that the SC3 path differs a lot from the past, due to marketing questions (most users asked for a different tool) and I have no problem with it
I have another tool that lets me composing with ease, and I have another tool that helps me for solos; the only reason why I’ll follow the SC3 development keeping it, is that the tools I have cannot be synced, and syncing (i.e. using SC3 as a conductor) is a must-have even if I don’t use orchestra tools
If you find this defensive or aggressive - I cannot do anything about that - except offer my apologies.
Not my intent whatsoever.
S
Cool, no worries, thanks for saying. No offence intended here either. Peace
I did talk about a way to do this on KVR - which involved spending money on other plugins to make it work - but my ultimate solution was to use Reaper as my main DAW because it’s so much better for routing lots of MIDI and Audio than Ableton Live.
So far as I can tell, no Multi-Voice output either, no mention of it in the manual. Replaced entirely with this insta-composer style garbage. Also not sure why they support IAC ins but not outs
I also tried that, but too much cumbersome
So I sold Ableton on KnobCloud, then I bought Bitwig
BTW, Bitwig can import almost all Ableton projects, and it can sandbox plugins, so if one plugin crash the rest is saved
Yes, I use Bitwig too and it can handle that routing ok. It is a shame about Ableton but I can do so much inside DAWs with VCV Rack that I have to live without it until they fix the issues with multichannel MIDI output plugins.
I just posted a valid workaround that keeps scaler 3 daw-synced and openable from within ableton, so for all intents and purposes in the box. Most importantly it’s all done with free software and it’s reliable and noninvase. Waiting on the mods to approve my post. The issue at core here lies with Ableton and not Scaler; non-existent midi channel routing is literally a decade plus problem for this DAW.
There is a fix for Ableton that is completely free, consistent, and provides DAW-Sync capabilities. You have to set it up, but once it’s running it’s no issue, and no fiddling on startup. You do have to install virtual midi channels but these are completely noninvasive compared to typical virtual audio cables. I’ll do a full writeup tomorrow once I have time; I spent a good 4 hours banging my head against the wall to try and make something work that is free, not too hacky, and actually workable.
Why Ableton forces me to use this workaround is beyond me; it’s completely archaic that I can’t use my DAW to route midi channels internally. HOWEVER once this is set up you don’t have to touch anything! I can’t embed images so only links for now. I also can’t post links as I’m a new user smh my head here’s the pastebin to all the images: https:// pastebin. com/ad3fu0Vp
The short of it:
Download Element (free and very good VST host alternative to BlueCat’s PatchWork; loadable and syncable in Ableton): Element - Kushview
Download loopMIDI (endorsed by Ableton): loopMIDI | Tobias Erichsen
Install loopMIDI, then create a virtual midi port (click the plus bottom left) and title it whatever you want (Ignore Ableton Clock, that was from testing).
IMAGE 1 HERE
Then install Element. It needs to find your plugins first before you load them into the floaty box area. Mine didn’t scan right away, so go to View → Plugin Manager and scan for them there.
IMAGE 2 HERE
Make sure to select your virtual midi channel in file → preferences too. No idea about the transport, I just turned that on too:
IMAGE 3 HERE
Inside of Element, set up the routing as follows (ignore everything else, can be deleted):
IMAGE 4 HERE
To get the ScalerOut Midi block on the right, right click in the area where all the boxes float, get the pop up menu, and select your virtual midi channel:
IMAGE 5 HERE
In the Node dropdown window on the left (click on Scaler 3, then open this up), make sure it looks like this (MIDI Channel to 16 rather than Omni):
IMAGE 6 HERE
Make sure to save the current setup.
IMAGE 7 HERE
You can now play Scaler 3 inside of Elements and you’ll see that you get both audio and the amount of data in loopMIDI is increasing, meaning that it’s transmitting. Make sure to obviously set the channels of the individual midi tracks in Scaler 3 to what you want them to be outputting.
IMAGE 8 HERE
You can press play/pause with the spacebar and it syncs to the scaler instance. It also opens and closes up whenever you close or open elements; very noninvasive.
You now have a workaround to Ableton’s archaic lack of Midi Channel routing by hosting Scaler 3 inside of a VSThost, forcing it’s midi channel multi-output to a virtual midi channel. Next steps: Ableton setup.
To set this up in Ableton is relatively straightforward. Open Ableton and load Element into a new track all on it’s own. Open Element and load the session you just made; for some reason the session saved for me a folder back and not in the sessions folder.
IMAGE 9 HERE
Next, set up your tracks corresponding to the midi channels in your Scaler instance. The “Midi From” dropdown menu will now have your virtual midi channel included in it (Mine: ScalerOut), so click on it. Next, for the specific midi channel routing just select channels 1 through 16 (Ch.1, etc.). Make sure you set the Monitor to In. Make sure to mute the instrument in Scaler 3 just for raw midi output to your DAW.
IMAGE 10 HERE
Done!
IMAGE 11 HERE
For proper DAW Sync you have to select EXT inside of Element when its loaded inside of Ableton in the top left of the window:
IMAGE 12 HERE
You can now only start/stop Scaler 3 (and everything running in Element) when you have Ableton selected.
loopMIDI channels persist across PC restarts but the loopMIDI application itself has to be open for the channels to actually show up. To not have to tinker anything else on startup just put the loopMIDI .exe (a shortcut of it is fine too) in the startup folder. Otherwise loopMIDI minimizes to tray if you close it.
IMAGE 13 HERE
OOPS! Seems like I wrote a full guide. Well, here it is. I’ll make a full post and update the existing troubleshooting thread for this problem. I also have 0 idea what I’m doing in terms of routing Bitwig-esque stuff so if there’s a step extra or something finnicky do give me feedback. But anyway, this worked for me, and it meets my standards of not being too hacky and annoying to deal with on every restart and still providing a good workflow albeit with an extra window and a few extra clicks. For me, personally, much more worthwhile to control all instruments from one scaler instance.
Fair word of warning, though, Elements is quite prone to crashing (on 11 Suite for me, at least, and quite consistently) if you try to delete it without closing out of your current preset (make a new file inside Elements where nothing is connected, then close the whole project) or if you close ableton too quickly after saving. Or I may just have too many plugins, idk lol.
Enjoy!! 
Why is there no MIDI OUT on the Standalone Version, but only MIDI IN? Or is there a setting somewhere? Can you guys help?
It’s not missing from Scaler 3. Ableton does not support Multi Channel MIDI out -. Possibly the only DAW that doesn’t. Please do post feedback over at Ableton.
Reasoning to the matter, I think that the SC3 mixer, the plugin mixer because I never tested the standalone, was made ALSO to circumvent the Ableton lack
In practice, you create the MULTI-MIDI out tracks into SC3 (acting as a plugin container) and ONLY AFTER you send the completed project to Ableton Live Channel 1
Does it make sense?
Quote from @davide about Midi out from the standalone and why it’s absent.
Ah, sorry for my comment above
I never imagined that the standalone has no MIDI out; so my reasoning above is nonsensical
I am not sure if this is what you want:
Install the “multi midi wrapper” and multi midi receive" “max4Live” tools. (I think they are default with 12.) You need them as well for instacomposer where you can find the links to the downloads.
Then in the “multi midi wrapper” you choose scaler 3 as the program to be used and you can create the song inside scaler.
Inside Scaler set the midi ports according to the tracks in Ableton.
In Live, before each instrument , set the midi receiver M4L and choose the corresponding midi channel.
I would have provided some screenshots but not possible here.
This works for me.
Michael
Yes and please midi out from the stand alone like in
I would not use the Wrapper since it doesn’t allow for DAW Sync. I’ve reformatted my post above over on r/Ableton.
Here it das work. When I click in Live Arrangement mode the curser in Scaler starts at the same position than in Live