FabFilter User Forum
Editing automation point values Cubase 5.5.3
I use various VTS(i)'s/plugins in Cubase 5.5.3..
I use alot of automation.
For some plugins I can type the automation values for points in the info bar, and they will be edited accordingly. Sylenth 1 is one of these plugins, and I praise it for that..
Other plugins like Fabfilter do not edit the same values(it jumps to COMPLETELY EXTREME VALUES) when entered in the info bar, and as a result you have to edit/draw the points accordingly with your mouse, which can be hard when it comes down to specific values..
Why is that? Why can't there be just one universal automation value code for all VST plugins? I hate fighting it all the time..
Thanks!
Jovas — Mar 10, 2012
Hi Jovas,
We'll look into this problem for future plug-in updates. Are you using the VST 2 or VST 3 plug-ins in Cubase?
Cheers,
Hi Frederik,
Thanks for your attention!
I'm using both situations in a test project on windows 7 Home Premium 64bit using Cubase 5.5.3 32bit and Twin 2 32bit:
I add two instrument tracks, one Twin 2 VST2, and one Twin 2 VST3. I add an automation track to automate the filter 1 freq on both versions of the tracks. Now this is what happens when I draw a few automation points and enter their values in the info bar of Cubase:
- VST2: It shows a scale ranging from 0-100, which does not correspond to the filter freq of Twin 2 which ranges from something like 5 to 76000 hz.. this makes editing points guessing/hard.
- VST3: It shows the same parameter scale as the Twin 2 freq range, however, when you enter a value of example 35 hz in the Cubase info bar, it jumps to it's highest value of about 76000hz.. This makes editing automation points guessing/hard.
I know VST, DAW's and plugins are complex software coding things, it's hard to make all daws and plugins work well together with each their own codings and laws.. It takes alot of work and time to make every DAW copy various Fabfilter parameter values, and make them act accordingly..
I do like to thank you for your time, and I hope automation editing will become more easy in the future, for at least with Cubase versions, but more likely with every DAW supporting Fabfilter!
I have just tested some more with Cubase 5. All parameters in all VST plug-ins always seem to be interpreted as a percentage value. So e.g. if you type '50' for a frequency value in Twin 2, it jumps to the middle of the range. This is the same in Sylenth1, but there most parameters range from 0 to 10 so it makes a bit more sense (but try e.g. a panning parameter). Even though VST 2 provides a way for the host to show and type values in the correct domain, Cubase does not use it.
In VST 3, Cubase 5 does in fact use the correct range for parameter values and e.g. a frequency value in Twin 2 is shown in Hz properly (at least in the latest version). I found however that we don't correctly interpret newly typed values. We'll fix that in future plug-in updates.
Cheers,
Yeah Steinberg refuses alot, I know.. ;)
Offcorse in Cubase I use the VST 3 versions when possible and it would be great if it would work accordingly..
But how do you program stuff like that? Do you communicate with the people who code the automation paramater stuff, VST and info bar data within Steinberg? How does this work?
Looks complex with all different DAW's and programmers..
Thanks anyhow!
I noticed that this problem is fixed in Saturn, can you please also fix it in the other plugins?
Thanks!