Steinberg Cubase Pro 8

[barryfell]

When editing automation of any VST2 plugins, the nodes don't report a change to their value when selected or dragged, and the infobar value is always 0-100 rather than reporting the correct value on the correct scale for the parameter. (Such as db etc)

There is no such issue with VST3 versions of the same plugins.

This is making it very difficult to accurately program automation for VST2 plugins.

Is anyone else experiencing this issue?

[barryfell]

Does anyone using VST2.4 plugins have 2mins to check if they are experiencing the above bug please?

Thanks

[sin night]

I just tried with DC8C 2 (both as vst2 and vst3) and this is my experience:

1 - With vst2 on the infobar the values are always between 0 and 100, while with the vst3 they are the actual value.
2 - When I drag a point on the automation curve, the value on the infobar follows the changes with both versions
3 - When I change the value on the info bar, the point moves accordingly.
4 - While dragging a point, the tooltip shows the point position (measure, etc) and updates correctly both with vst2 and vst3; the parameter value shows, for vst2, the value of the control at the current playing position rather thant the value at the point being dragged, while for vst3 shows the value of the point being moved (and it updates in real time!)
5 - The value shown on the automation track next the parameter name (near the RW buttons) reports the value at the current playing position, both for vst2 and vst3. Sometimes (often) the value is updated slowly (there's a lag), or it doesn't event update at all unless you play the project. Ths value has the correct scale for both vst2 and vst3 (so with vst2 you see both the right value here and the "wrong", "different" value info bar).

This is with Cubase 8.0.5 on Mac OSX 10.10.1. I tried with other plugins too (some which are only vst2 or vst3) and the vst2 had the same behaviour as DC8C (for the record, I tried with Kombinat DVA and Steinberg Bitcrusher).

I think there's definitely something wrong in Cubase's behaviour, though I suspect it's a while it works this way. Unfortunately I don't use the automation much and I look more at the curve than the actual point value, but I recall seeing quite often the 0-100 scale in the past. I never bothered checking the consistency across the daw, I always thought it was the plugin displaying automation values that way.
Not a deal breaker to me, but definitely wrong in my view.


I think this should be reported to the technical support (I'm not sure if it means writing the support or it's enough writing on Steinberg forum, the first looks like the correct way to me but I don't know it they are handling the support both ways nowadays).

[SJ_Digriz]

I think this should be reported to the technical support (I'm not sure if it means writing the support or it's enough writing on Steinberg forum, the first looks like the correct way to me but I don't know it they are handling the support both ways nowadays).

It is not both ways. The forum is a user to user support area, not official support. There are Steinberg folks chiming in from time to time and there is an issues reporting area .. but it is not official and it is only partially moderated. It is always best to go through official support.

[barryfell]

I just tried with DC8C 2 (both as vst2 and vst3) and this is my experience:

1 - With vst2 on the infobar the values are always between 0 and 100, while with the vst3 they are the actual value.
2 - When I drag a point on the automation curve, the value on the infobar follows the changes with both versions
3 - When I change the value on the info bar, the point moves accordingly.
4 - While dragging a point, the tooltip shows the point position (measure, etc) and updates correctly both with vst2 and vst3; the parameter value shows, for vst2, the value of the control at the current playing position rather thant the value at the point being dragged, while for vst3 shows the value of the point being moved (and it updates in real time!)
5 - The value shown on the automation track next the parameter name (near the RW buttons) reports the value at the current playing position, both for vst2 and vst3. Sometimes (often) the value is updated slowly (there's a lag), or it doesn't event update at all unless you play the project. Ths value has the correct scale for both vst2 and vst3 (so with vst2 you see both the right value here and the "wrong", "different" value info bar).

This is with Cubase 8.0.5 on Mac OSX 10.10.1. I tried with other plugins too (some which are only vst2 or vst3) and the vst2 had the same behaviour as DC8C (for the record, I tried with Kombinat DVA and Steinberg Bitcrusher).

I think there's definitely something wrong in Cubase's behaviour, though I suspect it's a while it works this way. Unfortunately I don't use the automation much and I look more at the curve than the actual point value, but I recall seeing quite often the 0-100 scale in the past. I never bothered checking the consistency across the daw, I always thought it was the plugin displaying automation values that way.
Not a deal breaker to me, but definitely wrong in my view.


I think this should be reported to the technical support (I'm not sure if it means writing the support or it's enough writing on Steinberg forum, the first looks like the correct way to me but I don't know it they are handling the support both ways nowadays).

Thanks for your help.

This issue has been reported and at least flagged on Steinberg's issue forum by tech support.

I'll raise it with official support as well.

[hibidy]

Here's a question not sure if anyone can answer. Cubase 8 is available as a download, but you need a steinberg key. Guitar Center has the key for 25 bucks, but I don't know for sure if it's compatible. It would be easier if the dingbats would just put the demo out already

[julioelgenio]

Here's a question not sure if anyone can answer. Cubase 8 is available as a download, but you need a steinberg key. Guitar Center has the key for 25 bucks, but I don't know for sure if it's compatible. It would be easier if the dingbats would just put the demo out already

If it's this, it should work, also if you have reFX Nexus, the one supplied with it also will work. it's been more than a month, waiting on a demo too


sorry for the big picture

[JonSolo]

Well you really helped me to see the big picture.

[hibidy]

Yeah, it say "elicencer"

Thanks

[jancivil]

(I'm not sure if it means writing the support or it's enough writing on Steinberg forum, the first looks like the correct way to me but I don't know it they are handling the support both ways nowadays).

The forum is not *Support*.

[julioelgenio]

Okay maybe I chose wrong photo but hopefully idea was understood LOL

[hibidy]

Okay maybe I chose wrong photo but hopefully idea was understood LOL

We're just joking, thanks again!

[Guillermo Navarrete]

Hello,

Here's a question not sure if anyone can answer. Cubase 8 is available as a download, but you need a steinberg key. Guitar Center has the key for 25 bucks, but I don't know for sure if it's compatible. It would be easier if the dingbats would just put the demo out already

If it's this, it should work, also if you have reFX Nexus, the one supplied with it also will work. it's been more than a month, waiting on a demo too


sorry for the big picture

Only the Cubase Pro 8 updates and upgrades are available as a download, which means that you already have a Cubase version that requires a USB-eLicenser, the full version is only available as a Box version because it comes with the USB-eLicenser. Are you purchasing an update/upgrade?

Best regards,
GN

[Compyfox]

I asked Steinberg this question several times - but... "why" only a download?

What about the Upgraders from pre C7.0 and C7.5 versions that want a box?


Oh and, once more:

To get back on topic however:
Did Cubase get an update on the time stretching and pitch shifting algo's? Weren't Celemony's SDK's updated in recent months? The MPEX Algo's are slowly showing it's age.

Not to mention:
When is the demo due?!

I slowly have the impression, that Steinberg wants to hide what's wrong with Cubase's development, and trusts on "happy comments" and "defending" from early adopters. But if I jump a bit through KVR, GS and Steinberg's own forum, the feedback is even more negative than with C7.

Don't tell me that this is "too much work" to release a demo at the beginning of the release. I can't follow this analogy.

[hibidy]

I'm confused now. I do not want an update. The full version is available as a download, elicenser is required. The one from GC seem to do the trick.