![]() Here's a good video on Reaper's routing options, from a dude that gets Reaper on a whole higher level than I do: But you could also use it in your case to disable it from going through the main hardware 1/2 outputs to your monitors. It's handy if you only want "wet" signal from some track that's sent to an aux send. That's a powerful little checkbox that tells each track whether it goes through the master bus or not. One thing you can mess with is the little check box on each send menu that says "Parent send". Plus I only have 4 channels of outboard compression, so I'm getting used to doing a lot of stem rendering during every project. It's still weird when you want to use it on nested folder tracks, but I've learned to work around that. They finally addressed some of the hokey behavior recently. Up until a few versions ago, ReaInsert was a major pain in the ass. ![]() ReaInsert is what I use to loop in my hardware compressors. ![]() The only other way that comes to mind is to use something like ReaInsert on each channel, and only pay attention to the send, and ignore the return, maybe routing the return to some dummy channel. I think that using the sends achieves the same end, and I'd bet that the results would be reflected in the routing matrix display if you used the send menus to route signals. I've checked it from time to time when I couldn't figure out why I wasn't getting a signal from one place to another, but it's really abstract and esoteric for me. I'm sure that you can use the routing matrix for this purpose, but I've just never been much of an expert on using it.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |