You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As mentioned on the Cockos forum, I've found that when using the Realearn function to Solo the selected track, any of the tracks it sends to or are nested under do not solo. My assumption is this is an issue between "exclusive solo" and "solo". Exclusive Solo appears to carry any routing with it while regular Solo does not.
For example, I will have something like the following:
-- DRUM BUS [Realearn here] -- DRUM FX BUS
-- FX BUS
--- GLOBAL REVERB
In this scenario, the DRUM BUS and DRUM FX BUS are nested in the DRUM CONTAINER folder. The FX CONTAINER folder holds an FX BUS which holds a GLOBAL REVERB
My DRUM BUS will send through the DRUM CONTAINER to the MASTER. It will also send to the DRUM FX BUS and the GLOBAL REVERB.
If I use my mouse on the MCP and hit the Solo button on the DRUM BUS, it will solo the DRUM BUS and anything it sends to (as clicking on it appears to activate the solo in Exclusive Solo mode).
If I map Realearn to the Solo of the track it sits on, it will solo just the track. If I have it nested in a folder or bus, no audio is passed to the MASTER. There is no option in the drop down in Realearn for Exclusive Solo.
Having said all that, Exclusive Solo is not available from the Actions. So I'm not sure if that will be a hurdle.
The text was updated successfully, but these errors were encountered:
Just to add another voice to the 'change of solo behaviour' request. As stated, ReaLearn solo currently does not respect routing. If I have a number of tracks bused to another track with master/parent disabled, soloing one of the bused tracks results in silence. Using the individual numbered track solo option works, to a point, but if you move tracks around, the association is lost.