# Undoing - - First - - Automation point should return fader/parameter back to previous position

**URL:** <https://forums.steinberg.net/t/undoing-first-automation-point-should-return-fader-parameter-back-to-previous-position/148984>\
**Category:** Cubase\
**Tags:** feature-request, cubase-10\
**Created:** [May 23, 2020, 12:53pm UTC](https://forums.steinberg.net/t/undoing-first-automation-point-should-return-fader-parameter-back-to-previous-position/148984 "2020-05-23T12:53:27Z")\
**Posts on this page:** 18\
**Page:** 1

<div class="post-metadata">

**Author:** ![vncvr](https://avatars.discourse-cdn.com/v4/letter/v/f14d63/32.png) [@vncvr](https://forums.steinberg.net/u/vncvr)\
**Post date:** [May 23, 2020, 12:53pm UTC](https://forums.steinberg.net/t/undoing-first-automation-point-should-return-fader-parameter-back-to-previous-position/148984/1 "2020-05-23T12:53:27Z")

</div>

Happens all the time, am I the only one?

Don’t you feel it would be a logical protocol for undoing automation point #1 that it returns the parameter to its previous stat?

I’ve never intentionally put a first automation point and ‘undo’ it just to set fader positions.

---

<div class="post-metadata">

**Author:** ![Martin.Jirsak](https://avatars.discourse-cdn.com/v4/letter/m/85f322/32.png) [@Martin.Jirsak](https://forums.steinberg.net/u/Martin.Jirsak)\
**Post date:** [May 25, 2020, 4:18pm UTC](https://forums.steinberg.net/t/undoing-first-automation-point-should-return-fader-parameter-back-to-previous-position/148984/2 "2020-05-25T16:18:11Z")

</div>

Hi,

Could you describe the issue in step by step manner, please?

---

<div class="post-metadata">

**Author:** ![matthewmooremusic](https://avatars.discourse-cdn.com/v4/letter/m/48db29/32.png) [@matthewmooremusic](https://forums.steinberg.net/u/matthewmooremusic)\
**Post date:** [May 26, 2020, 8:57am UTC](https://forums.steinberg.net/t/undoing-first-automation-point-should-return-fader-parameter-back-to-previous-position/148984/3 "2020-05-26T08:57:10Z")

</div>

My understanding of the issue:

> **[Automation undo problem.mkv](https://www.dropbox.com/s/ghikynxlyx4knxc/Automation%20undo%20problem.mkv?dl=0)**
>
> Shared with Dropbox

When you click undo, the fader should return to zero???

---

<div class="post-metadata">

**Author:** ![vncvr](https://avatars.discourse-cdn.com/v4/letter/v/f14d63/32.png) [@vncvr](https://forums.steinberg.net/u/vncvr)\
**Post date:** [May 26, 2020, 9:31am UTC](https://forums.steinberg.net/t/undoing-first-automation-point-should-return-fader-parameter-back-to-previous-position/148984/4 "2020-05-26T09:31:26Z")

</div>

> [@matthewmooremusic](#):
>
> My understanding of the issue:
> 
> [Dropbox - Automation undo problem.mkv - Simplify your life](https://www.dropbox.com/s/ghikynxlyx4knxc/Automation%20undo%20problem.mkv?dl=0)
> 
> When you click undo, the fader should return to zero???

Yes exactly, it’s not a bug or anything, I just think the protocol should be different. Accidentally placing an automation point on a group or FX volume in the edit window is not a rare occasion. I know, pretty OCD of me.

---

<div class="post-metadata">

**Author:** ![Martin.Jirsak](https://avatars.discourse-cdn.com/v4/letter/m/85f322/32.png) [@Martin.Jirsak](https://forums.steinberg.net/u/Martin.Jirsak)\
**Post date:** [May 26, 2020, 10:56am UTC](https://forums.steinberg.net/t/undoing-first-automation-point-should-return-fader-parameter-back-to-previous-position/148984/5 "2020-05-26T10:56:19Z")

</div>

Hi,

I see. If you 1st click (and release the mouse) to add the Node, then you move the node down, you get 2 entries to the History. So then you can Undo the move and then Undo the Add Node.

---

<div class="post-metadata">

**Author:** ![matthewmooremusic](https://avatars.discourse-cdn.com/v4/letter/m/48db29/32.png) [@matthewmooremusic](https://forums.steinberg.net/u/matthewmooremusic)\
**Post date:** [May 26, 2020, 1:10pm UTC](https://forums.steinberg.net/t/undoing-first-automation-point-should-return-fader-parameter-back-to-previous-position/148984/6 "2020-05-26T13:10:51Z")

</div>

Thanks Martin. That does work. Unfortunately it’s where you might have accidentally clicked, created a node and dragged all in one go that makes it difficult to get back to the previous setting.

Is it possible to tag this as either a bug or a feature request?

---

<div class="post-metadata">

**Author:** ![steve](https://dub1.discourse-cdn.com/steinberg/user_avatar/forums.steinberg.net/steve/32/193789_2.png) [@steve](https://forums.steinberg.net/u/steve)\
**Post date:** [May 26, 2020, 2:11pm UTC](https://forums.steinberg.net/t/undoing-first-automation-point-should-return-fader-parameter-back-to-previous-position/148984/7 "2020-05-26T14:11:58Z")

</div>

> [@matthewmooremusic](#):
>
> Is it possible to tag this as either a bug or a feature request?

yes. Topic moved. 🙂

---

<div class="post-metadata">

**Author:** ![mitchiemasha](https://dub1.discourse-cdn.com/steinberg/user_avatar/forums.steinberg.net/mitchiemasha/32/116605_2.png) [@mitchiemasha](https://forums.steinberg.net/u/mitchiemasha)\
**Post date:** [May 26, 2020, 3:15pm UTC](https://forums.steinberg.net/t/undoing-first-automation-point-should-return-fader-parameter-back-to-previous-position/148984/8 "2020-05-26T15:15:11Z")

</div>

Yes this is super annoying. I often accidentally click in a node, then undo it, track fader doesn’t return to the potion it was, it simply removes the node. Remembering where the fader was to move it back is always a never. The sense of dread when you see the line move and instantly go through the process of trying to remember.

---

<div class="post-metadata">

**Author:** ![vncvr](https://avatars.discourse-cdn.com/v4/letter/v/f14d63/32.png) [@vncvr](https://forums.steinberg.net/u/vncvr)\
**Post date:** [May 26, 2020, 8:04pm UTC](https://forums.steinberg.net/t/undoing-first-automation-point-should-return-fader-parameter-back-to-previous-position/148984/9 "2020-05-26T20:04:37Z")

</div>

> [@mitchiemasha](#):
>
> Yes this is super annoying. I often accidentally click in a node, then undo it, track fader doesn’t return to the potion it was, it simply removes the node. Remembering where the fader was to move it back is always a never. The sense of dread when you see the line move and instantly go through the process of trying to remember.

Yes, and to make things worse. Mixer Undo has no affect here.

---

<div class="post-metadata">

**Author:** ![matthewmooremusic](https://avatars.discourse-cdn.com/v4/letter/m/48db29/32.png) [@matthewmooremusic](https://forums.steinberg.net/u/matthewmooremusic)\
**Post date:** [May 27, 2020, 8:16am UTC](https://forums.steinberg.net/t/undoing-first-automation-point-should-return-fader-parameter-back-to-previous-position/148984/10 "2020-05-27T08:16:25Z")

</div>

> [@mitchiemasha](#):
>
> Yes this is super annoying. I often accidentally click in a node, then undo it, track fader doesn’t return to the potion it was, it simply removes the node. Remembering where the fader was to move it back is always a never. The sense of dread when you see the line move and instantly go through the process of trying to remember.

That sense of dread…omg yes!!!

---

<div class="post-metadata">

**Author:** ![vncvr](https://avatars.discourse-cdn.com/v4/letter/v/f14d63/32.png) [@vncvr](https://forums.steinberg.net/u/vncvr)\
**Post date:** [May 27, 2020, 7:22pm UTC](https://forums.steinberg.net/t/undoing-first-automation-point-should-return-fader-parameter-back-to-previous-position/148984/11 "2020-05-27T19:22:40Z")

</div>

This mostly occurs when trying to make a click-drag selection of events and thinking your clicking into empty space and accidentally click dragging in a node. Easily happens, especially if zoomed out and working quickly.

---

<div class="post-metadata">

**Author:** ![mitchiemasha](https://dub1.discourse-cdn.com/steinberg/user_avatar/forums.steinberg.net/mitchiemasha/32/116605_2.png) [@mitchiemasha](https://forums.steinberg.net/u/mitchiemasha)\
**Post date:** [May 28, 2020, 9:08am UTC](https://forums.steinberg.net/t/undoing-first-automation-point-should-return-fader-parameter-back-to-previous-position/148984/12 "2020-05-28T09:08:59Z")

</div>

I do believe it was mentioned some time ago but it seems to have dropped from focus as a serious issue.

---

<div class="post-metadata">

**Author:** ![theodorozzz](https://dub1.discourse-cdn.com/steinberg/user_avatar/forums.steinberg.net/theodorozzz/32/313447_2.png) [@theodorozzz](https://forums.steinberg.net/u/theodorozzz)\
**Post date:** [May 28, 2020, 11:15pm UTC](https://forums.steinberg.net/t/undoing-first-automation-point-should-return-fader-parameter-back-to-previous-position/148984/13 "2020-05-28T23:15:31Z")

</div>

Yes, this topic appears time to time and it super annoying issue.  
Esspecially on latest mixing stages, when you accidentally touch the automation line and cant return it to the previous volume. Please change it’s behaviour!

---

<div class="post-metadata">

**Author:** ![vncvr](https://avatars.discourse-cdn.com/v4/letter/v/f14d63/32.png) [@vncvr](https://forums.steinberg.net/u/vncvr)\
**Post date:** [May 29, 2020, 4:51am UTC](https://forums.steinberg.net/t/undoing-first-automation-point-should-return-fader-parameter-back-to-previous-position/148984/14 "2020-05-29T04:51:09Z")

</div>

This is a great protocol change for Cubase 11.

---

<div class="post-metadata">

**Author:** ![mitchiemasha](https://dub1.discourse-cdn.com/steinberg/user_avatar/forums.steinberg.net/mitchiemasha/32/116605_2.png) [@mitchiemasha](https://forums.steinberg.net/u/mitchiemasha)\
**Post date:** [May 29, 2020, 3:03pm UTC](https://forums.steinberg.net/t/undoing-first-automation-point-should-return-fader-parameter-back-to-previous-position/148984/15 "2020-05-29T15:03:10Z")

</div>

> [@lovegames](#):
>
> This is a great protocol change for Cubase 11.

Yes… lets hope so.

---

<div class="post-metadata">

**Author:** ![vncvr](https://avatars.discourse-cdn.com/v4/letter/v/f14d63/32.png) [@vncvr](https://forums.steinberg.net/u/vncvr)\
**Post date:** [July 27, 2020, 8:39pm UTC](https://forums.steinberg.net/t/undoing-first-automation-point-should-return-fader-parameter-back-to-previous-position/148984/16 "2020-07-27T20:39:31Z")

</div>

> [@mitchiemasha](#):
>
> > [@lovegames](#):
> >
> > This is a great protocol change for Cubase 11.
> 
> Yes… lets hope so.

Fingers crossed.

---

<div class="post-metadata">

**Author:** ![Tweswend](https://avatars.discourse-cdn.com/v4/letter/t/50afbb/32.png) [@Tweswend](https://forums.steinberg.net/u/Tweswend)\
**Post date:** [March 24, 2022, 6:42am UTC](https://forums.steinberg.net/t/undoing-first-automation-point-should-return-fader-parameter-back-to-previous-position/148984/17 "2022-03-24T06:42:31Z")

</div>

Hi,  
I see this topic about undoing the first automation point was raised over 1 year ago but it seems that the same issue is still there in cubase 12. So I am here to resubmit this problem because many of cubase/nuendo users I know find it really annoying and should be solved.  
p.s. I am sorry that my voice might be impolite here as I am not good at expressing things in English 😢

---

<div class="post-metadata">

**Author:** ![Timo00](https://dub1.discourse-cdn.com/steinberg/user_avatar/forums.steinberg.net/timo00/32/199903_2.png) [@Timo00](https://forums.steinberg.net/u/Timo00)\
**Post date:** [March 24, 2022, 3:28pm UTC](https://forums.steinberg.net/t/undoing-first-automation-point-should-return-fader-parameter-back-to-previous-position/148984/18 "2022-03-24T15:28:54Z")

</div>

+1 for this. Also, I would love to see a mode where you can only select existing automation points (to edit them), which would remove the accidental creation of new automation points (and vice versa, a mode where you can only add new automation points and don’t run the danger of accidentally selecting an existing one and moving it). While on the topic, it would also be great to have a “snap to” grid for automation values, say, only integer percentages or integer dB values.

Maybe some of these features exist and I just don’t know about them?
