View Single Post
Old 08-15-2016, 01:10 AM   #669
mainframe
Human being with feelings
 
Join Date: Apr 2009
Posts: 48
Default

Quote:
Originally Posted by schwa View Post
There is no sense of a currently active track send, or currently active track send bank. NUM_SENDS in the config file is used only as a way to limit the amount of feedback REAPER sends.
This is a bit of a shame. It would make a lot of sense in my opinion to have this implemented. You could use this feature to heavily optimize the screen space on smaller devices. I often have 4+ sends on a track but rarely need access to all of them at the same time. 2 active ones would be more then enough so banking through them would be a perfect solution (DEVICE_PREV_SEND; DEVICE_NEXT_SEND and DEVICE_PREV_SEND_BANK; DEVICE_NEXT_SEND_BANK).
Is it too complicated to implement because the send slots in Reaper are not fixed?
mainframe is offline   Reply With Quote