Quote:
Originally Posted by nofish
Thing is the master/parent send tickbox is enabled for new tracks by default because when created as top level tracks they would be silent otherwise (because not sending to master).
Now when putting a top level track in a folder the master send becomes a parent send which you don't want right?
So you'd need an option saying along the lines of "automatically disable master/parent send when track is a child"?
I don't think this option exists currently (someone may correct me) but maybe worth a feature request?
edit:
Hm..I guess you want child tracks to directly send to the master instead?
I wonder if that's even possible currently, not that I know..
|
Sorry, I had a very busy Monday and have not had a chance to keep up with this thread, nor have I had a chance to do more testing.
But let me be a little more specific about my situation. I don't use folder tracks in reaper the way most people use folder tracks in reaper. I never liked the way things get routed and I wanted to be able to place my busses together in my screen-sets so I use folder tracks for visual purposes only. In other words I deliberately disable all routing to parent tracks. These tracks have no input or output intentionally. Instead I use these tracks for collapsing groups and visual reference only. I intentionally lock their screen height and controls. For me this works better, as I can place all my busses in one place on the screen. It also makes more sense to me because sometimes I have a track going to multiple busses.
Now what happens is if I need to move a particular group and I select the entire group including the parent tracks, and then accidentally drop them underneath another parent folder trying to position them correctly (which can happen quite easily the way the mouse works trying to decide where or what level you want to place the track) then all of the routing for all of those tracks that I was moving seems to get reset and routed to the new parent track which was supposed to receive no input. (Remember that there are no master/parent since checked here. All tracks have this feature to disabled.) This not only screws up the tracks I moved but all of the tracks that were originally underneath the parent folder as well. The children tracks seem to be reassigned to the wrong bus. But
reassigning the sends to the proper bus no longer works for some reason. Even after reassigning the tracks to the proper bus, although reaper says the tracks are assigned to the proper bus, that bus never gets their signal. The only way to fix the problem is to destroy the bus and re-create all of the sends. If there are a lot of tracks between the new and old original children this can be quite tedious and annoying.
Granted, I don't do a lot of wholesale moves like this very often but it's still a pain. I know now to do a save directly preceding the move so that if I screw something up I can reload the project and try again. Still it would be nice if there was a way to disable this auto routing feature reaper. Unfortunately I'm not seeing that there is a way to do that. It's not the end of the world, but I was curious if anyone else had ever had the need to disable that feature.
For what it's worth, I've had the behavior of the disappearing sends occur once or twice before and was never able to understand what caused it. By that, I mean that a bus would stop working even though several tracks were assigned to send to it. The tracks would show meter and all of the connections would indicate that they were where they were supposed to be but the bus track would never receive any audio. Destroying the bus track and re-assigning always fix the problem.
@domzy: No I'm not using any scripts for this, just dragging the group with the mouse.
Turn off auto route for folders
Linear Mode
