I’m not sure if this is intentional, or if it has potential to cause problems in the long run but it’s something I’ve noticed….
By default Live comes set up to make new layers with Sonic 7 as the end-point.
So, I’ll open a simple template project that has nothing in it but a Layer and Stack for an external bit of kit (Roland Fantom XR).
I’ll click the + button to add a new layer and it quickly loads with HALion Sonic as the endpoint. I’ll open that Sonic instance and pop out the left pane. Here I see that while the instance is clearly Sonic 7, Live has tagged it as Sonic SE.
If I clear the layer (set to nc) and then choose a new instance of Sonic, it’s different…
- No default pluginstate/multi-program is loaded.
- In the left pane the Main is named differently.
- In manually forced Sonic instances I get the option to link extra output busses back into the same Live mix bus. With the default “SE” variant that’s not an option.
Left Pane with default Sonic:
Notice HSSE doesn’t list itself as an option for bus routing.
Left Pane with manually loaded Sonic:
In this case the Main bus is named “HALion Sonic” with busses named “HS”, and the extra HS outputs can be linked back to the same bus.
I also notice that when linking multiple busses back to “HALion Sonic”, the extra outputs are not added to the Live Mixing Console.
With 3rd party plugins (I.E. bidule), the plugin is not getting notification that extra busses have become active.
Would it not be proper for the host to automatically set that up and report to the plugin that the bus is ready for use?
I have a more detailed post on the ‘multiple audio busses issues’ here:
I thought it might be helpful to isolate that I noticed a reference to Sonic SE, and that it behaves ‘differently’ than other Sonic instances here in a thread of its own.