More routing options for return tracks

[Nauree]

Would love more viable routing options for return tracks, currently it's a hassle to route it anywhere beyond the master channel (audio tracks being the only thing you can route to now doesn't really work when it picks up a lot of other sources as well). Lots of DAWs allow you to route your return/FX tracks to your buss/group and that just makes life way easier.

[Stromkraft]

Would love more viable routing options for return tracks, currently it's a hassle to route it anywhere beyond the master channel (audio tracks being the only thing you can route to now doesn't really work when it picks up a lot of other sources as well). Lots of DAWs allow you to route your return/FX tracks to your buss/group and that just makes life way easier.

As a buss could be an audio track — that's what I use for busses and aux's — then it would seem that you would like groups to be able to take an audio input? This rather than return tracks getting some new feature. Because now as it is, a return can be routed to anything that can take an audio input. You see what I'm saying?

I route my returns to

• audio tracks with processing (including dummy tracks)
• audio tracks acting as a buss, most often than not my "Main Buss" (the only track I have that is routed to Master) . I don't really use groups as busses, one reason being returns can't come back to them. When I have groups I send the member's output to a buss instead.
• side-chain inputs on any track with a plug-in that has available inputs

[Nauree]

Would love more viable routing options for return tracks, currently it's a hassle to route it anywhere beyond the master channel (audio tracks being the only thing you can route to now doesn't really work when it picks up a lot of other sources as well). Lots of DAWs allow you to route your return/FX tracks to your buss/group and that just makes life way easier.

As a buss could be an audio track — that's what I use for busses and aux's — then it would seem that you would like groups to be able to take an audio input? This rather than return tracks getting some new feature. Because now as it is, a return can be routed to anything that can take an audio input. You see what I'm saying?

I route my returns to

• audio tracks with processing (including dummy tracks)
• audio tracks acting as a buss, most often than not my "Main Buss" (the only track I have that is routed to Master) . I don't really use groups as busses, one reason being returns can't come back to them. When I have groups I send the member's output to a buss instead.
• side-chain inputs on any track with a plug-in that has available inputs

I realize there are workarounds, my request is for it to be possible to route your return tracks to your groups. I use groups quite extensively and unfortunately routing your return track to an audio track inside the group causes some issues, one of them being that you can no longer solo anything inside the group and the return track picking up the audio from several of your other tracks for some reason.

[Stromkraft]

I realize there are workarounds, my request is for it to be possible to route your return tracks to your groups. I use groups quite extensively and unfortunately routing your return track to an audio track inside the group causes some issues, one of them being that you can no longer solo anything inside the group and the return track picking up the audio from several of your other tracks for some reason.

Well, my point was that if groups had its audio inputs available also from anywhere else but member tracks, then return tracks and any other type of track could send signal also to group tracks, without being a member.

Of course, lifting this limitation may be most important to you in connection with return tracks, so I understand your request. If there's no side-effects stopping this implementation I'd suggest any non-member track should be able to send to the Group track input.

As for the solo issue you experience, I do think this is a bug and not intentional (because it doesn't make any sense to me).

I haven't been able to make a sure-fire way to reproduce this, so I haven't reported it I think. I intend to though.

[Nauree]

I realize there are workarounds, my request is for it to be possible to route your return tracks to your groups. I use groups quite extensively and unfortunately routing your return track to an audio track inside the group causes some issues, one of them being that you can no longer solo anything inside the group and the return track picking up the audio from several of your other tracks for some reason.

Well, my point was that if groups had its audio inputs available also from anywhere else but member tracks, then return tracks and any other type of track could send signal also to group tracks, without being a member.

Of course, lifting this limitation may be most important to you in connection with return tracks, so I understand your request. If there's no side-effects stopping this implementation I'd suggest any non-member track should be able to send to the Group track input.

As for the solo issue you experience, I do think this is a bug and not intentional (because it doesn't make any sense to me).

I haven't been able to make a sure-fire way to reproduce this, so I haven't reported it I think. I intend to though.

Right, I see what you mean, I specifically mentioned return tracks because you're not able to route those to the group while audio and midi you can just put inside the group which is effectively the same thing as routing it to the group.

Also, my bad, I just noticed what I wrote was completely wrong and not what I intended to write at all, you can solo tracks inside the group.

What I meant was that the audio track inside the group that receives the return tracks also picks up every other return track not routed to it so you can't solo that audio track and hear just what your returns are doing. It doesn't seem to double up the effect, but it's kinda strange nonetheless and ideally it wouldn't.

Alternatively an option to route your tracks through the group first before going into the return track would be welcome as well, it's the copy pasting of group automation (especially filtering) onto the return track that's somewhat of a workflow irk to me.