I was trying to automate the mix control of an insert effect via the info Line and noticed the values didn’t look right. After poking around I realized that instead of displaying the value of a selected data point the Info Line was showing the value from the Cursor position.
In the Images below the 1st automation value should be 0.00 and the second 1.00. But instead of showing those values they both show 0.30 which is the automation level at the Cursor. If I move the Cursor to a location where its value is 0.55 the Info Line values for the automation points would also show as 0.55.
OK, this is moving into haunted house territory. After making the post above I left to get some lunch. When I got back the data point in the 2nd pic was now at the bottom of the Lane - just where it should be if it’s set to 0.00. But it was at the top of the Lane (where I’d originally created it) an hour or so earlier.
Yes this does seem to be the case. It looks to be confined to the AAS Insert plug-ins Multiphonics CV-3, and Objeq Delay 2 but not their VSTi counterparts. If someone has these and can confirm the issue that would be great.
For the delay the value displayed was even stranger
These issues appear only in Cubendo because it’s the only DAW that implements the full specification of VST3. Other hosts ignore the parts they don’t like, and text conversion of parameter values is often one of them. Similarly, plugin devs tend to dismiss these issues as VST3 (hence Steinberg) bs.
There is something off with how C15 handles VST automation however.
Going through all my old projects and converting to C15 (mostly from SX3 but also some from 8 and 12) and for some third party plugins automation in the older versions of Cubase for some parameters would be a number from 0 to 100 but that same plugin (for example a volume parameter) is now showing in Cubase with a max of +6.02 and minimum of infinity. Dont even know how to type infinity into the info bar so you have to drag the automation point with the mouse… which is a pain because they are now harder ro see in C15.
Ive even seen this behavior trying to copy the volume automation on a standard group channel from a group created in old version to a new group in C15. Have to recreate from hand most of the time.
No big deal if its a ramp with 4 points. Can take a whole day if it was recorded with a knob.
All in all I have no complaints with C15 when starting with a new project created in C15.. but anything created in an older version is just a nightmare to workwith.
Its just far less tolerant of anything that is not exactly meeting current specs…
That sounds like a VST2 plugin has been replaced by its VST3 version. This may have happened because C15 has VST2 disabled by default. VST2 parameters are plain 0-100, no text conversion, no scaling. Not all plugins are automatically replaceable like this, they have to declare themselves so. For minus infinity, usually -inf works, but this is up to the plugin, as each one implements its own text/value conversion routine.
Im still using VST2 in many cases .. but was unaware of the 0 to 100 thing you mentioned. That explains a lot … And explains why this is such a pain in the behind.
I know the plugins above it looks like a plugin issue… but steinberg hasn’t exactly made it easy on folks
I personally think 0-100 was too raw, at least the scaling was necessary, but the text-value conversion seems a little over-engineered, which is a usual accusation for VST3 features. Still, at this point, after 18 years, people could stop complaining and just implement the frigging thing. It’s not terribly complicated anyway.
I eventually figured out that if I put the cursor at the same location as the automation data I can adjust the values normally since the value of the data and the value at the cursor will always be the same.
But you still can’t edit the value text box, it ignores changes and keeps the previous value after pressing enter. That’s the really bad part for me, having to make all adjustments with the mouse.
