Aliases for Sends (allow custom names)

[J Riley Hill]

SUMMARY:

It would be great to have the ability to give sends(and the matching receives) an alias or custom nickname. Much in the same way you are able to give fx and fx parameters an alias.

This would allow one to quickly identify whether a send was being used to send to a parent, side-chain, do parallel processing etc.

WHY IT WOULD BE COOL:
REAPER's routing is the most robust of any DAW but sessions can get confusing when there is a lot of weird routing going on. If you have multiple sends to one track for different purposes there is currently no way to quickly see which send is which.

IMPLEMENTATION IDEA:
I feel like a mock-up or visualization isn't necessary but two implementation ideas I would love to see are:

1. The ability to assign a mouse modifier to click on a send and bring up a rename window.
2. The ability to double-click on the name of the send in the routing window for the track and start typing the new name.

[andyp24]

+1 for this.

It would make life a lot easier.

[ashcat_lt]

I feel like I've seen this request before, but it is a good one. I'd like to able to alias track channels too, but this alone would be a big step closer.

[heda]

excellent idea. will do it for Track Inspector at least.

[Judders]

+1

Would love this

[andyp24]

+1 for aliasing track channel names too (because I've now started using aschat-lt's trick of routing sends through multichannel folders which leaves the MCP sends looking very confusing!)

[Masi]

+1 great idea

[deeb]

yes yes please!

[deeb]

Originally Posted by andyp24

+1 for aliasing track channel names too (because I've now started using aschat-lt's trick of routing sends through multichannel folders which leaves the MCP sends looking very confusing!)

got curious! in what does it consists? "aschat multichannel folder"? : )

[ferropop]

This would be incredible. The routing possibilities keep getting more used, and more complex, and being able to keep track of what's happening is essential.

[ashcat_lt]

Originally Posted by deeb

got curious! in what does it consists? "aschat multichannel folder"? : )

Assume you've got a folder or submix bus. A number of tracks mix into that, and you control the overall level of that group of tracks from the fader. But then you've got sends from some of those tracks to some other track like a Reverb bus. The mix of these tracks at that bus is not the same as at the first. If you just move the fader of the first submix bus, then you mess up the wet/dry balance of all the tracks it controls. People try to use VCA to get around that by using one fader to adjust all of those individual tracks instead of the folder/bus, but then what if you want something like a compressor on the bus? Changing the individual track levels means you have to change compressor settings. So...

Send from the individual tracks to unused channels on the folder/submix, and then from there to the reverb. Then changing the folder/bus fader keeps the wet/dry mixes without having to readjust the compressor, and you're rocking.

Here's a quick licecap to illustrate the basic premise:


Except that all those sends go to the one track, so it's hard to tell exactly where the ultimate destination is meant to be. So if we could alias those sends...

[deeb]

Originally Posted by ashcat_lt

..

Thank you ashcar_it! got it! very nice : )

[kgarello]

Thanks ashcat!