This may slip through the cracks otherwise, so I'm calling out to all mixers in the forum to go and visit these feature requests in the issue tracker, and vote for them if they find them useful. They all deal with automation workflows, and are all useful for users who have no control surface as well. Ideas brought forth in the discussion threads of the requests, as well as those posted in this thread will find their way in to the original request if they make sense.
Airon is really doing a great job of highlighting a weak spot in the midst of a whole bunch of strengths. What he's saying is really true. I've done post work for many shows in Reaper but never a final mix, and pretty much for the reasons Airon describes. The track counts get very high, the session lengths are usually quite long which pushes automation to the forefront. When mixing in this way automation is generally applied to everything if for no other reason than to "lock" the mix and prevent accidental changes from happening throughout the duration. There are certainly cool tricks to get around some of these issues in the sound fx, dialog and foley compositing in a show (mainly item fx/automation) but when all the pieces come together continuous automation needs to be quick to enable and apply.....so +1. :)
Bumped. Don't forget there are plenty of other useful feature requests out there. Take a look at some of them. You may find something you're likely to support. Also, check out a small compilation of useful requests presented in the thread. The three requests presented here are in that list as well.
Has anyone made a request for correct delay compensation on oversampled plugins or etc.? If so, I can't seem to find it.. This would be my #2 mixing request after trim volume envelopes.
You'll want to discuss that in the bug forum, because it would be a bug. If the bug is confirmed and discussed to rule out user error, or perhaps we need to start pointing fingers at a particular plugin, we can post a bug report in the issue tracker. That's step 2. If it's a bug and they can fix it, it'll be fixed by the next release.