Cubase 5 Automation Bug
Top Comments
All Comments (27)
-
Your examples only show the weakness of this software design when there is no automation before or after the automation being written, e.g fade ins and fade outs. If you had preexisting automation immediately following your violin swell, and the levels did not default back to the starting point after your new automation was written in (your violin swell), the new automation would upset the preexisting automation, making for a more complicated fix than simply deleting the default point.
-
Change your automation mode and you will live longer. It's not a bug.
-
thanks for clarifying...
-
This is Cubase, not Nuendo. Virgin Territory would be fine if it worked that way in Cubase, but it doesn't.
They've since changed it. Now it is all virgin territory and your end point is where you let go of the fader, so it won't return to the position it started at.
-
this is NOT a bug but a very well documented feature. Look in your Nuendo manual at page 225. This is called Virgin Territory, you can turn it on or off in the Automation Control panel. I find this incredibly useful by the way because lots of times I just want to do a quick dip and have it go back to where it started.
-
so treu. I work with alot of automation and this is really annoying.
-
fixed this in like 2 months of getting this software wich isent to bad sense i was a beginner
-
@Fredco1 agreee not even tt big of a deal
This is known as an automation mode. The defualt is set to Touch (Top left). The modes are: Touch, Auto-Latch, Cross-over, Overwrite and Trim. Each has its own uses.
Touch means that the automation will record what you do when you touch it. As soon as you let go it will return to where it started. What you want is Auto-Latch. Cheers
FuzzboxUK1 2 years ago 8
You're an idiot, that is CORRECT behaviour.
If you are changing a bit of automation in the middle of a song you want the last position to overwrite everything you had previously done?
It is worrying the level of peoples intelligence, this is clearly not a bug it just doesn't fit with your idea of how you would like it to perform. Taking 2 seconds to THINK you would have seen why it behaves as it does before regarding it as a bug, tard.
dogbodynigga 3 years ago 8