#Cubase 10.5 vs 11 how to

If the entire track is in Write mode then any change to any parameter will create breakpoints for that parameter if only placing specific parameters into Write mode, then automation will only be written for those parameters. When in Write mode, modifying a parameter while Cubase is playing, whether by adjusting an onscreen control with the mouse or using an external hardware controller, will cause automation data to be written to the track. When you do this, the corresponding R (Automation Read) button will also light up. This is done by clicking on the W button that’s shown on tracks, automation lanes, and at the top of plug-in windows. For the latter to work, the track, parameter or plug-in has to be placed into Automation Write mode. You can create automation offline by drawing and manipulating breakpoints and curves in the project window, or in real time while Cubase is playing your project. Similar problems can arise when rearranging a part within its own track. Unless you do this in the right way, the automation data will be left behind. You may create a repeating saw-wave shaped automation curve to drive a reverse bass effect, but then move that part to another track.

#Cubase 10.5 vs 11 how to

We’ll look at how to modify this later.Īn automation curve is tied to its track and the timeline, not to the parts on the track, and this can create problems. Where you have set a value manually, a breakpoint marker is drawn, and Cubase calculates – or ‘tweens’ – the curve between consecutive breakpoints. The automation data itself is shown as a continuous line, referred to as a ‘curve’, representing the value of the associated parameter.