How to stop Reaper from adding automation point on stop

[Thonex]

Hi gang,

Is there a setting or pref to have it so when I stop the transport while I'm writing automation (Touch mode for examples) that it doesn't add another automation point equal to where it started?



I don't want that last point (in red) added upon stop.

Thanks.

Cheers,

Andrew K

[mccrabney]

__EDIT__
for those reading, you can track other posts on this issue here:

the most detailed post in tips/tricks: https://forums.cockos.com/showthread.php?t=252010
a bug report: https://forum.cockos.com/showthread.php?t=273056
another bug report, from 2017: https://forum.cockos.com/showthread.php?t=192204
a post in general: https://forum.cockos.com/showthread.php?t=254798
a feature request: https://forum.cockos.com/showthread.php?t=251752
a "why is this happening" thread: https://forum.cockos.com/showthread.php?t=190663
a post in newbieland: https://forum.cockos.com/showthread.php?t=274395
__END__

no, there's no option to disable this, and it makes for a really discouraging process when you're trying to record automation in a loop.

https://forum.cockos.com/showthread.php?t=251752

please let us record our hardware movements without these additional return values ahead of the record cursor. this should not be default envelope behavior

[Thonex]

Thanks McCrabney,

Ugh… not great.

I’ll pipe in on whatever feature request thread.

Thanks,

Andrew K

[mccrabney]

yeah, not great, and shocking that more noise isn't being made about this.

Thonex, while searching for more posts on this, i found your video and thread about this from last year. i wanted to add them to this thread for reference.

devs, if you haven't seen the video, it illustrates the issue perfectly: users are unable to set final values for parameters using automation record modes.

https://www.dropbox.com/s/v7d0wk8zws...forum.mp4?dl=0

https://forum.cockos.com/showthread.php?p=2321405

[mccrabney]

thonex, i've also found this discussion from 2017:

https://forums.cockos.com/showthread.php?p=1850948

wherein the actions "Automation: Write current values for actively-writing envelopes from cursor to end of project" is suggested as a solution.

1) as far as i can tell, this action doesn't work on AI
2) on a portable install, it doesn't seem to work as expected anyway, since you don't get an envelope point at exact position of record stop. this results in an artifact (see gif below)
3) we shouldn't have to run additional actions to convince an envelope to stay at the position where we manually left it. that is why we moved it there.

[Thonex]

Originally Posted by mccrabney

yeah, not great, and shocking that more noise isn't being made about this.

Thonex, while searching for more posts on this, i found your video and thread about this from last year. i wanted to add them to this thread for reference.

devs, if you haven't seen the video, it illustrates the issue perfectly: users are unable to set final values for parameters using automation record modes.

https://www.dropbox.com/s/v7d0wk8zws...forum.mp4?dl=0

https://forum.cockos.com/showthread.php?p=2321405

LOL... it's rather hilarious (and sad at the same time) that I post threads for the same thing a year later... completely forgetting that I had posted that thread!

I've actually had the same thing happen to me for scripting... I'll post a question in the Scripts forum... only to have it answered by a younger version of myself LOL

Cheers,

Andrew K

[Thonex]

Originally Posted by mccrabney

thonex, i've also found this discussion from 2017:

https://forums.cockos.com/showthread.php?p=1850948

wherein the actions "Automation: Write current values for actively-writing envelopes from cursor to end of project" is suggested as a solution.

1) as far as i can tell, this action doesn't work on AI
2) on a portable install, it doesn't seem to work as expected anyway, since you don't get an envelope point at exact position of record stop. this results in an artifact (see gif below)
3) we shouldn't have to run additional actions to convince an envelope to stay at the position where we manually left it. that is why we moved it there.

Yeah... I may have already seen that. All I know is that in my searches I haven't come across a solution. And I don't want to write a defer script for something like that... and it would probably be too hard for me anyway!


Cheers,

Andrew K

[Thonex]

Yeah... so what I really want is this... from Cubase/Nuendo

[mccrabney]

^ if "to end" == "to end of AI" then yes, exactly.

same thing for your first pass of recording automation in Ableton. desired behavior: ~3 seconds into gif. no surfing envelope points ahead of your edit cursor, erasing other envelope data in the future.

note, however, the undesired behavior that happens at ~13 seconds: that when i re-enable record to record another layer of automation, you get the same issue as in REAPER: an assumption that the user wants to return to the previous automation point. no good.



all we need to do is look to CCs for how this should behave. envelope points are momentary, informing the value in between that point and the next one. if there is no next one, it should inform the parameter until project/ai end -- NOT have a point programmatically inserted at stop.

[mccrabney]

not to mention the bugs caused by time selection and "return speed" causing dead areas where your automation movements aren't recorded properly:

https://forum.cockos.com/showthread.php?t=251994

[Thonex]

Originally Posted by mccrabney

not to mention the bugs caused by time selection and "return speed" causing dead areas where your automation movements aren't recorded properly:

https://forum.cockos.com/showthread.php?t=251994

That's a very good point!! Yes.

Cheers,

Andrew K

[mccrabney]

someone should write a script that automatically adds audio and/or MIDI content to the end of all new recordings to properly illustrate how wrong this behavior is

"it looks like you're trying to record automation. want me to return it to its previous position?"

[laser558]

Sorry to pick up on a reasonably old thread but in reference to Thonex, I too, experience this issue and it is infuriating. My get around is to simply push undo should a rogue automation point occur upon stop. Not elegant, I know but it might help.

[mccrabney]

thanks for the suggestion. UNDO does not help here.



recording an AI that resembles a normal fade is still impossible in REAPER. "write envelope from current position" actions do not help.

[vitalker]

Does anyone know how to do that without workarounds?

[skylar_battles]

Maybe the best solution for now is for someone capable to make a delete final point action and then to make a custom action that engages this action whenever the relevant modes are used after playback is stopped?

[vitalker]

Originally Posted by skylar_battles

Maybe the best solution for now is for someone capable to make a delete final point action and then to make a custom action that engages this action whenever the relevant modes are used after playback is stopped?

That's a really bad workaround.

[skylar_battles]

I don't disagree at all I wish it just behaved as it should

[mozart999uk]

Originally Posted by skylar_battles

I don't disagree at all I wish it just behaved as it should

Me too. Seems to be falling on deaf ears :-(

[Adn_71]

+1 to this.

[laser558]

As I have mentioned, I use undo butit clearly is a fault and should be addressed by the devs. I have been in a position where I have completed a mix, only to discover one of these points has passed me by unnoticed.

[skylar_battles]

But how does the last point get removed by using the undo action? I think I have to alt click it to clear it.

[laser558]

Originally Posted by skylar_battles

But how does the last point get removed by using the undo action? I think I have to alt click it to clear it.

From my point of view, it is the last action that Reaper would have performed and therefore, undoing that last action, the automation point, seems to do the trick for me but I do stress, this is a workaround for me.

[skylar_battles]

I’m just confused because the final envelope point is part of the single action to write automation for me. Did you do something so that you could undo the last point with the undo command?