Touch Automation in Cubase

Hello all (Please UPVOTE this if you agree),

TLDR:
PLLEEEAASEEEEEE :pleading_face: :pleading_face: :pleading_face: can you make this a feature that can be enabled/disabled? It just seems really silly and counter-intuitive to FIRST have to find the automaton I would like to write, create an end value, BEFORE I can even think of writing the automation in touch mode. This work-around seems to honestly defeat the whole purpose of touch automation in my opinion. So pleeasseeee I am pleading… make it a feature that can be enabled/disabled if you don’t want to make it a global thing for your software for whatever reason you have.

Yes, I am aware that this is a topic that has been beaten to death. I even went as far back as to read up on why the touch mode behaves the way it does in Cubase. I’ve only ever used Cubase as my main DAW so for the many years I have been trying to do touch automation, I felt it was broken because the parameter I was automating would never automatically return to the initial value. I cycled through the various modes and was never able to achieve this. I thought to myself, perhaps I don’t understand how automation works. Ever since then I have to manually draw in the automation to return to its previous value. This has been for years now.

Sometime ago, I decided to try Logic Pro for a while after I was convinced to by my brother. To my surprise, when I automated something for the first time, it automatically returned to its initial value after I let the fader go. I was so shocked that I started researching the different automation modes. To my surprise again, it is touch mode that gives you this behavior. So why in the world was this not working in Cubase I thought to myself…

I also tried Studio One 5, and Pro Tools, and ALL of them seem to behave as expected when in touch mode and writing automation…

It was only not too long ago that I finally looked this up in the forums here and found that many users have been reporting the same experience. It would seem Cubase doesn’t want to implement this feature for various reasons.

So can I just plead… PLLEEEAASEEEEEE :pleading_face: :pleading_face: :pleading_face: that you make this a feature that can be enabled/disabled? It just seems really silly and counter-intuitive to FIRST have to find the automaton I would like to write, create an end value, BEFORE I can even think of writing the automation in touch mode. This work-around seems to honestly defeat the whole purpose of touch automation in my opinion. So pleeasseeee I am pleading… make it a feature that can be enabled/disabled if you don’t want to make it a global thing for your software for whatever reason you have.

Thank you.

1 Like