Automation: Read/Latch/Touch/Write Modes Behaviour
|
10-06-2009 11:52 AM
|
|
Moderator
|
|
Automation: Read/Latch/Touch/Write Modes Behaviour
When a track is set to other mode than "trim/read", vol/pan/mute envelopes do not set themselves to current value when enabled
1. Insert a new track
2. Set its volume to -12dB's or else.
3. Set its automation mode to read
4. Enable its volume envelope
Result: Automation curve shows 0.0dB's and overrides previous value (-12dB's)
Expected: Automation curve sets itself to current value (-12dB's)
This behaviour is extended to latch/touch/write modes.
|
|
Issue Details
|
Project
Deprecated REAPER issue tracker
Category Audio recording and playback
Status Fixed
Priority 5 - Medium
Affected Version 3.12
Closed Version 3.13
Yes votes
7
No votes
0
Assigned Users
(none)
Tags
Alien invasion, Automation, Envelope, Envelope state
|
|
10-08-2009 09:49 AM
|
|
Administrator
|
|
|
I agree this is confusing, in fact it took me a little while working with it to understand exactly how it works. The track envelopes (not FX envelopes) are all trim envelopes. The basic reason for this is that there are 2 separate volume and pan envelopes per track, prefx and post-fader, and you can automate both separately. They can't both be absolute envelopes, and you can use the same fader to automate either envelope.
But creating either envelope, by using auto-add-arm or explicitly adding the envelope, does not change the track output level or pan, so there is not a bug in the sense of the automation not working correctly. The issue is that the visual feedback is confusing. There have been a number of threads about this in the past, but feel free to start a fresh one.
|
10-08-2009 01:27 PM
|
|
Administrator
|
|
|
After some daring laboratory experimentation at Cockos HQ, we have decided to reclassify this as a bug, and mark it as Fix Coming Soon.
|
10-08-2009 01:30 PM
|
|
Human being with feelings
|
|
|
Great news, it'll speed up my work flow no end :)
|
All times are GMT -7. The time now is 09:34 AM.