Search the Community
Showing results for tags 'automation write'.
Found 2 results
Hi All, I'm a very (19years) long time user of Cakewalk and never encountered a problem I couldn't sort out, but this has me stumped. I'm trying to write the fader movements from my Softube Fader (I have the Console 1 MK II as well). I'm familiar with drawing and recording automation for native CW features as well as available plugin lanes. I'm familiar with arming automation 'write' and 'read' etc Whether I choose to 'write' the CW volume envelope or select Volume from the plugin for Console 1, it will not write. All fader movements aren't registered as soon as I hit play with 'write' enabled etc. Other than this the Console and fader are flawless. For static mixing I have even tried to add Console 1 (Fader) as a MIDI input device (which shouldn't be necessary) but CW reports that there is not enough memory as reported by windows and therefore is unchecked. Any help or suggestions would be greatly appreciated!!!
I'm trying out using an X-Touch Mini controller to record an automation envelope for a soft synth. What I'm trying to achieve is a smooth volume envelope that moves up and down through the track. After I've done a pass with write automation enabled, what I end up with can be seen in the attached image. So basically lots of 'jump' nodes when what I really want is them all to be 'linear' for a smoother transition. When I listen back on headphones I can hear lots of very subtle clicks each time it passes a jump node. So firstly is it possible to set default write automation nodes as 'linear' instead of 'jump'? Or is there another way to achieve this? I thought I might be able to bulk select a group of nodes and change them all to linear but that doesn't seem possible unless I've missed something. The only workaround I've found is to kind of manually average out sections by looking for linear places and delete lots of nodes and replace them with one long linear line. But not only is it a pain to do over long tracks (and kind of defeats the purpose of the more natural method of gradually turning a physical knob or slider) but it seems quite buggy. I'll highlight an area with lots of nodes by right clicking and dragging then press delete on the keyboard only to see that it doesn't delete all the nodes I selected. Say I mass select 40 nodes and click delete, it leaves behind maybe 10 of them that I then have to highlight again and delete.