I hope someone is knows what i mean on here cos it is really getting to me now.
I have Vital, Spire, Dune3, Omnisphere2 and many more.
BUT!
BTW, I know it’s not a bug as such.
I have a issue with cubase not able to change a node in the automation lane.
Scenario: I do the automation on Filter Cutoff then say i want to change a node, so i click on the node, go up to the info line (just above the inspector) double click the value and enter 20.00 hit enter and it snaps up to 70 semitones (the full amount basically) for some effed up reason.
I know its a issue with some parameter conflict or something, but does anybody have an idea, cos this is putting so much time on my editing.
Cheers in advance to my fellow Vitalist’s
John
It does the same for me, however, I’ve never encountered it previously.
Might I suggest you assign the mod wheel to the filter cutoff then you can automate that.
It has values in the info line from 0 to 1 with increments of .01
I actually often use my mouse wheel as each click is also the same increment.
The other added bonus is you can assign all sorts of other things to the mod wheel and have them all move at the same time
AA
Hi arielleandrist,
I don’t have a problem with the automation activation, it’s the nodes in picture illustration. in picture i cannot edit a different value, it just keeps going/reverting back to 535
My specific problem is with editing on the nodes (for finer detail), all cubase “stock” plugins have not got a problem with this particular operation, but third party plugins do.
JV
If I automate the same ‘mod_wheel’ parameter in Spire the minium and maximum values for that lane are 0.00 and 100.00 respectively and I can set any value between those without any problem. I don’t use a single stock plugin and have only come across what you are describing once before, probably 8 - 10yrs ago.
If yours is sitting at 535 (it’s the next node, not the one you are indicating) that would indicate a 0 -1000 range. Can’t remember seeing one of those in a while.
I assume you are running x64 vst3 for all your plugins??
Ok Ariel,
I drew the red line to the wrong node 
my bad.
0-1000 range is allover spire dude, and Vital has it in a couple of places also.
Yes i’m using VST3 x64
Are you a mac user btw?
John.
Ok, I have to admit something, the spire track I was looking at was imported from an older project. It’s a vst2…
So I opened a new project, and a new instrument track with Spire vst3 and I get a worse issue than you!
No matter what the automation lane is controlling, every node is represented by a “C” in the info line, no matter the value.
I loaded another track with Spire vst2 and it works fine. So weird…
It is one of the few I have a vst2 loaded however, practically everything else is vst3 only. All x64 however.
Try the 2, see if you get the same results?
I’m on PC…
A quick look thru the steinberg forum and it appears to have been going on for rather a few years.
I’m surprised I have not encountered it previously. I def don’t have the issue with Vital so it’s curious that you might.
I’ll keep investigating
Dont have vst2 atm but i’m begrudged on reinstalling them.
Literally every TP plugin i have is affected by this (omnisphere2 used to be fine but now that is ef’d)
Yeah i have had this problem for a few years!
Sorry i have created a problem for you!
Which CB are you using?
I have tried a new topic with Cubase forum (“Ongoing Automation issues for to long”)
John
I’m on 14 pro, I haven’t yet encountered it with anything else. Mostly use Vital, Hive2, Pnuema Pro, Dune3, Fabfilter, all appear to be ok…
I’m gonna have a better look at Spire (vst3) and a few others I rarely use to see if I can recreate it.
Bizzare for certain
I’ll admit I’m not tech savvy, I know enough to get by, but I am racking my brain on thinking is it something in my setup that I have done! While I’m on about it, I have a PC of some 6 years, a SSL 2+MK2 interface and a Arturia Keylab mk2 midi controller Keyboard.
