.OK we are post 2.09 so is this on the roadmap for a fix yet? I’m sorry to have to keep bringing this up but please understand that the current implementation basically makes recording synths with automation unworkable for me at present and I see this as a very serious issue – to show how serious I took this screenshot which I hope demonstrates the extent of the problem
here I think it is plain to see in this relatively simple sequence example every time I adjust the cutoff and then switch to the res knob, the cutoff drops to zero and every time I adjust the res and then switch back to cutoff it does the same – all the time having the cutoff at zero makes the sound silent so I would hastily adjust it back only to then have the res drop down and have to be corrected. It’s like I was fighting the host all the way and this is just a simple example.
This is not a bug with this particular VSTi (Korg Legacy Cell) – I have encountered similar behaviour with every synth and effect I have tried to automate and I chose LC as the example as it is widely known to be a stable and well established “classic VSTi. No host should do this – it takes away control from the musician – not one of those drops to zero in either param was intentional and even if I could edit them out afterwards the whole flow of the track and of my playing was ruined.
@aMUSEd wrote:
OK we are post 2.09 so is this on the roadmap for a fix yet? I’m sorry to have to keep bringing this up but please understand that the current implementation basically makes recording synths with automation unworkable for me at present and I see this as a very serious issue – to show how serious I took this screenshot which I hope demonstrates the extent of the problem
here I think it is plain to see in this relatively simple sequence example every time I adjust the cutoff and then switch to the res knob, the cutoff drops to zero and every time I adjust the res and then switch back to cutoff it does the same – all the time having the cutoff at zero makes the sound silent so I would hastily adjust it back only to then have the res drop down and have to be corrected. It’s like I was fighting the host all the way and this is just a simple example.
This is not a bug with this particular VSTi (Korg Legacy Cell) – I have encountered similar behaviour with every synth and effect I have tried to automate and I chose LC as the example as it is widely known to be a stable and well established “classic VSTi. No host should do this – it takes away control from the musician – not one of those drops to zero in either param was intentional and even if I could edit them out afterwards the whole flow of the track and of my playing was ruined.
Did you record the MIDI notes and the knob automation at the same time?
I assume that the curve sequences were not set to the full length of the arrangement from the start, but rather gradually extended as recording progressed?
Cool If it helps I’ve got a worse example here from this afternoon:
I was trying to automate mallet stiffness in Lounge Lizard to create a more organic feel but it wouldn’t even let me move off the zero for more than a second or two – every time I tried to get it where I wanted it to be it would snap back to zero – this time even though I was not moving to another param as in the example above – as you’ll appreciate I gave up as it was impossible.
