Hi folks - I have Ableton and cubase and for different reasons I can’t get multi out working (by multi out I mean, sending the chords out via one midi channel to one vst synth, bass out via another midi channel to a different vst synth, and so on.
The process in scaler 3 is simple, the DAW side is not!
Ableton - as far as I can tell it is not capable of doing it due to its habit of collapsing all midi into channel one from a vst (Bluecat workaround is unsatisfactory as you can’t use Ableton native synths, M4L workaround is buggy and crashes Ableton)
Cubase - as far as I can tell, it CAN do it, but the midi routing is confusing to me and leads to cubase crashing.
I’ve spent weeks on this now (and lots of money) and can’t find a way. Please help!!
I came here hoping to find a solution to this.
I couldn’t figure out how to separate midi channel in Ableton.
(I also have Cubase but I didn’t tried yet, I thought it would be easier since you can select midi channels)
I thought with the new arrange page and everything we could stop using multiple instances but maybe that’s not the case? I didn’t find the live sync option tho
It seems like you’re experiencing problems with routing various MIDI outputs to separate VST synths within Ableton and Cubase, both of which have their own idiosyncrasies with multi-output configurations. Within Ableton, the problem you’re experiencing is a result of its behavior of sending all MIDI from a VST to one channel, which can be restrictive when you require each part to have its own separate channel. The Bluecat workaround is not perfect since it does not support Ableton’s native synths, and M4L is not reliable for your purposes. On the Cubase end, while it does support multi-output MIDI routing, it can be difficult to set up and crash-prone if not properly configured. To fix this, I suggest you double-check your MIDI routing in Cubase—have each instrument configured on its own MIDI track with unique channel assignments, and have a check to see that your system’s resources (such as CPU) aren’t maxed out, because this can lead to instability. For Ableton, you may need to investigate implementing third-party MIDI routing plugins or change to a more flexible DAW configuration like Bitwig, which has native multi-output routing capabilities. It’s an annoying bug, but with some fiddling and patience, a solid workaround can often be established.
“To fix this, I suggest you double-check your MIDI routing in Cubase—have each instrument configured on its own MIDI track with unique channel assignments.”
Yes, precise instructions from someone who has done it successfully in cubase was exactly what I was hoping for when I posted this.
Hello SNC, I just tried in Cubase and it’s working fine: I created a new instrument track, in the routing section I’ve selected scaler 3 as midi input, and the right channel in the box just below.
Of course you have to enable rec or monitoring on the track to hear the incoming notes
Seems working with no crashes right now.
If you have some money to spend, you can buy Bitwig that manages multi-out very well and easily, with the further advantage that it can import Ableton Live projects
Moreover, it is rock-solid (hard to crash) due to sand-boxing
Hi folks. As pointed out Ableton Live combines all internal MIDI routings into one channel. One effective strategy to get around this on Mac OS is to create a virtual MIDI bus, effectively turning them into external MIDI routings, which do work across multiple channels. Here is Ableton’s article on setting it up. https://help.ableton.com/hc/en-us/articles/209774225-Setting-up-a-virtual-MIDI-bus
Works natively on Mac OS but does require 3rd party software on Windows. But still a viable solution.
After setting this up and doing some testing. It does work, but for my setup was extra crashy. I do have a complex template though, that might be the issue
