Ableton Forum

I am sorry for not replying right away - I was away from home for over a week.

Here's an example project.
https://www.dropbox.com/s/35fe1tmergpfh ... t.rar?dl=0

There are only 2 tracks:
1) "Lead" - routed to Return A
2) "Meow" - routed to Return B

Return A's output is routed to Master (as by default);
Return B's output is routed to G_Returns (the group for returns).

Yet if you click Solo on "G_Returns", you will hear both tracks (Lead and Meow) playing. Why???

Thank you very much for the interest so far and for the help in advance.

Anyone? Please!!!

Auto2000 -

From the Ableton manual, p.224:

"Soloing a clip track leaves any return tracks audible, provided that the Solo in Place option is enabled in the Solo button’s [right-click](PC) / [CTRL-click](Mac) context menu. Solo in Place can also be set as the default behavior by selecting the entry in the Options menu."

In the case of your example set, "Solo-in-place" is, in fact, checked on. This means that when you hit the "solo" button on an audio channel (in your case, the "G_Returns" channel, you still hear the "Lead" track because it is routed through Return A, which is NOT muted when you hit the solo button.

If you control click on the G_Return solo button and UNCHECK "solo-in-place," you will find that soloing the G_Return track behaves as you would like - you'll only hear "Meow."

sounddevisor wrote:
In the case of your example set, "Solo-in-place" is, in fact, checked on. This means that when you hit the "solo" button on an audio channel (in your case, the "G_Returns" channel, you still hear the "Lead" track because it is routed through Return A, which is NOT muted when you hit the solo button.

If you control click on the G_Return solo button and UNCHECK "solo-in-place," you will find that soloing the G_Return track behaves as you would like - you'll only hear "Meow."

Good catch. There's also another thing.

Auto2000 wrote: Return A's output is routed to Master (as by default);
Return B's output is routed to G_Returns (the group for returns).

Yet if you click Solo on "G_Returns", you will hear both tracks (Lead and Meow) playing. Why???

The "solo in place" setting that sounddevisor mentioned is the reason. You also have a dry signal present in your Trueverb, which is usually not what you want in a return track and contributed to the perception of hearing more than the returns. Uncheck the direct signal like this if this was unintentional:
.

Thank you so much, guys. That's a brilliant find.

However I still don't understand one thing.
If with 'Solo-in-place' enabled I'm supposed to hear all the returns, then why I do hear them when I solo the 'G_Returns' group, but I don't hear them when I solo 'Lead' or 'Meow'?

Thank you very much in advance for taking the time.

I'm not gonna help you, sorry, but this is the most interesting topic I've read in a while.
Greatly inspires me - if you read my other stuff you may know I'm in a 3-piece band, all of us going into one computer running ableton, so soloing is obviously an issue, for want of a better word - I'm the 'drummer' sometimes I want to solo my kicks and hear the synth and lead, sometimes I want to solo them and only get kicks. It was a problem I was leaving for another day as it seemed massively complex, but actually sounds like this is exactly what I want, and its no real problem!

Cheers Abletonians.

This issue turned out to be a lot more complicated than I expected...

Update:

My experience is actually a lot like how the OP describes it now in every project in Live 9.6.2 and all the 9.7 betas. Soloing a return plus a track sending to it also play back tracks not sending to it. That's just whacked.

Any ideas? In my opinion this is indeed a bug. I'll evaluate with more details later.

Stromkraft wrote:Update:

My experience is actually a lot like how the OP describes it now in every project in Live 9.6.2 and all the 9.7 betas. Soloing a return plus a track sending to it also play back tracks not sending to it. That's just whacked.

Any ideas? In my opinion this is indeed a bug. I'll evaluate with more details later.

Made a test and it's clear this is not always so in every project. I'll make some more testing and open a new discussion when I've attempted to identify the circumstances.