chip mcdonald
10-08-2007, 11:20 AM
A quibble, but a confusing one:
If a track is soloed *other than one you're setting receives up on*, it would probably be a good idea to have the track default to getting soloed once you start selecting a receive on a new track.
In other words - Reaper's routing is a bit confusing to start with, but if you're trying to setup an elaborate send/receive arrangement and forget you've got something soloed, you can end up wasting 5 minutes as I've just done trying to figure out why a routing scheme doesn't seem to be working as you'd expect...
(... exacerbated by the fact that the routing menu pops up covering the TCP of said track... you might think you already soloed the track, but if you didn't it becomes a wild goose chase...)
If a track is soloed *other than one you're setting receives up on*, it would probably be a good idea to have the track default to getting soloed once you start selecting a receive on a new track.
In other words - Reaper's routing is a bit confusing to start with, but if you're trying to setup an elaborate send/receive arrangement and forget you've got something soloed, you can end up wasting 5 minutes as I've just done trying to figure out why a routing scheme doesn't seem to be working as you'd expect...
(... exacerbated by the fact that the routing menu pops up covering the TCP of said track... you might think you already soloed the track, but if you didn't it becomes a wild goose chase...)