Go Back   Cockos Incorporated Forums > REAPER Forums > REAPER Bug Reports

Reply
 
Thread Tools Display Modes
Old 09-08-2014, 03:26 AM   #1
-nicolas-
Human being with feelings
 
Join Date: May 2014
Location: France
Posts: 31
Default Major automation bug: in write mode, un-armed lanes won't read

- set track to write mode
- record automation on some lanes
- un-arm these lanes to protect them, but leave them enabled so that they read.
- arm other lanes
- hit play: the previously recorded lanes won't read


Here is a gif showing this bug.
- first it shows that EQ automation is reading normally in read mode
- EQ automation lane is enabled and un-armed
- then I choose write mode, it shows EQ automation is not playing any more


https://stash.reaper.fm/21762/automat...RITE%20bug.gif


OSX.6.8 and Reaper 4.721

Last edited by -nicolas-; 09-08-2014 at 03:31 AM.
-nicolas- is offline   Reply With Quote
Old 09-17-2014, 05:13 PM   #2
-nicolas-
Human being with feelings
 
Join Date: May 2014
Location: France
Posts: 31
Default

Still not working in 4.73.

In write mode, when not armed, Volume and Pan envelopes are read correctly.
Though, FX envelopes such as ReaEQ or Reasurround parameters are not read.

Nicolas
-nicolas- is offline   Reply With Quote
Old 09-17-2014, 05:20 PM   #3
airon
Human being with feelings
 
airon's Avatar
 
Join Date: Aug 2006
Location: Berlin
Posts: 10,411
Default

Confirmed for Reaper 4.73 x64.

If this is by design, it is inconsistent. In WRITE mode either all or none are read.

I'd actually expect none to be read that aren't armed, though I have yet to get in to a situation where I need plugin automation to be read while using WRITE mode. Disarming plugin parameters is just too much work, so I never do it. That all might change for when new developments are introduced in to automation facilities.
__________________
Dialogue/FX Editor & Re-Recording Mixer
(Video)Using Latch Preview
"My ego comes pre-shrunk" - Randy Thom
airon is online now   Reply With Quote
Old 09-17-2014, 10:40 PM   #4
-nicolas-
Human being with feelings
 
Join Date: May 2014
Location: France
Posts: 31
Default

Quote:
Originally Posted by airon View Post
I'd actually expect none to be read that aren't armed, though I have yet to get in to a situation where I need plugin automation to be read while using WRITE mode.
When you do automation on a parameter, you always need automation you have done before on other parameters to be replayed. It is a common behaviour on all software and hardware automation devices. If you don't want automation to be replayed, you disable the parameter.
-nicolas- is offline   Reply With Quote
Old 09-18-2014, 05:07 AM   #5
Lawrence
Human being with feelings
 
Join Date: Mar 2007
Posts: 21,513
Default

I agree with Airon. If a plugin parameter is in literal Write mode, it starts writing new automation at it's current setting as soon as the transport rolls so there's really nothing to read until you come out of write mode.

Touch is a different story, it will read until you touch it, and then it too will stop reading and start writing until you let it go. but in Write, it should just sit there and overwrite everything until you punch out, then start reading again.
Lawrence is offline   Reply With Quote
Old 09-18-2014, 06:22 AM   #6
DarkStar
Human being with feelings
 
DarkStar's Avatar
 
Join Date: May 2006
Location: Surrey, UK
Posts: 18,059
Default

Maybe I misunderstand, but isn't -nicolas- talking of reading the automation envelopes of the other parameters when one parameter is being Written?

Say you have a synth with 2 parameters (A and B) automated. You want to rewrite the envelope for A from your MIDI controller, while hearing the effect of the automation of both A (essentially arriving from your keyboard controller AND B (from its existing automation envelope).
__________________
DarkStar ... interesting, if true. . . . Inspired by ...
DarkStar is online now   Reply With Quote
Old 09-18-2014, 06:46 AM   #7
Lawrence
Human being with feelings
 
Join Date: Mar 2007
Posts: 21,513
Default

Yeah, it's kinda weird. I can reproduce the behavior he talks about though.

It's ... different in Reaper because the "modes" (read, write, touch, etc) seems to be global to the track. I mean, it should be reading in either case but setting "Write" applies to the entire track unless you disable arming, which is kinda different from what I'm used to. In other cases every plugin (and the track itself, vol, pan, mute) can independently be in read, write, touch, etc, so it never comes up.

I mean, can you just go into ReaEQ below and put it in "Touch" or "Read" mode while ReaSurround is in "Write" at the same time or are those modes global to everything on the track?



Here's what I mean below where there are three plugins on a track. One plugin is in "Read", one is in "Touch", and the other plug is in "Write" and the track itself (Volume, Pan, Mute) isn't enabled for anything. But in Reaper that switching seems to always be global to the track, at the track level, so I may not be fully understanding it.



The modes above are "plugin specific", i.e. you can't have one parameter on a plugin in Touch while another parameter on that same plug is in Write, but the modes are independent for every device on the track, which is more of what I'm accustomed to.

Last edited by Lawrence; 09-18-2014 at 07:06 AM.
Lawrence is offline   Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -7. The time now is 03:32 AM.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2019, vBulletin Solutions Inc.