Cubase 8.0.20 Maintenance Update Released

[Keith99]

I had a similar issue and tracked it down to a problem with the VST32 version of Satin. No idea why 8.0.2 suddenly raised this though. Anyway what you need to do is rename your plugin folder and see if you can now load the project and then add plugins back one by one until you find the culprit

[Guillermo Navarrete]

Hello,

So after having started the 32 bit version, I now succeded in loading a project as well as opening an empty one. However, trying to open the instrument rack crashes cubase with "a serious error has occured". I think I´ll downgrade till somebody knows what to do about this..
Best Regards
Roman Empire

Your problem sounds like a 32bit VST Plug-in from a third party is crashing the Bridge, you should start loading your plug-ins and VSTi one by one until you find the cause of the crash.

Best regards,
GN

[Roman Empire]

What I don´t understand here is how the bridge can crash if I open an empty project?
Anyway, even if it is, it´d be too much work to find out which plugin is causing it, and if I did - what if it´s one that I actually need? I rolled back to 8.0.10, hoping that there´ll be a fix for this problem in the next update..

Best Regards

Roman Empire

[Guillermo Navarrete]

Hello,

Because Cubase is still reading the plug-in even if you don't load it on a project, you should check the blacklist, probably it has been listed there.
How can we fix it if we don't know which plug-in is causing it, how do we even know if it is Cubase the one causing the problem? Perhaps you need to update that plug-in and the problem will be solved. If it is one that you "need", you can always look for its 64 bit version or request the developers for an update.

The blacklist is inside the preferences folder and it is called blacklist.xml

Best regards,
GN

[EnGee]

What I don´t understand here is how the bridge can crash if I open an empty project?
Anyway, even if it is, it´d be too much work to find out which plugin is causing it, and if I did - what if it´s one that I actually need? I rolled back to 8.0.10, hoping that there´ll be a fix for this problem in the next update..

Best Regards

Roman Empire

Just an idea might be useful in general. Why you don't separate the 32 plugins and the 64 bit ones in two folders, then install the two versions of Cubase 32 and 64 bit?
Most of the plugins that have 64bit, have also 32bit versions, so install both, then if you want to use an only 32bit plugin, you load the 32bit version of Cubase.

For example, I have 2 Vstplugins folders and point each version to its folder (Cubase 64bit to Vstplugins of 64bit ...etc), so I never use any bridge and eventually it is very easy to spot the problem (if there is one). This applies also on all other DAWs I have.

[VitaminD]

Just an idea might be useful in general. Why you don't separate the 32 plugins and the 64 bit ones in two folders...

This is very useful indeed. I do the same thing. Not for multiple instances of Cubase, but for general purpose usage. Plus, in situations such as this, it makes it a bit easier to troubleshoot troublesome plugins.

so I have:
X:\VSTPlugins\32-bit\Instruments
X:\VSTPlugins\32-bit\Effects
and
X:\VSTPlugins\64-bit\Instruments
X:\VSTPlugins\64-bit\Effects

Then I can enable/disable any of these individually.

[Roman Empire]

I do have my 32 and 64 bit plugins separated already. What I do not understand is why upgrading Cubase to 8.0.20 all of a sudden makes Cubase crash because of particular plugins.

Anyway, when I get the time for it, I´ll reinstall 8.0.20 and play around with the 32 bit plugins.

Thanks

Best Regards

Roman Empire

[Googly Smythe]

What I do not understand is why upgrading Cubase to 8.0.20 all of a sudden makes Cubase...

...export MP3 files a full 5db quieter than WAV files? Never had this problem 'till this update.
Also, in the piano roll MIDI editor - the divider between the piano roll and controller sections vanishes - never had this problem before either.
Hey ho.

[thebutler]

What I do not understand is why upgrading Cubase to 8.0.20 all of a sudden makes Cubase...

...export MP3 files a full 5db quieter than WAV files? Never had this problem 'till this update.
Hey ho.

Wow... is that still the case..? Just been over at the Steinberg forums and didn't notice other reports like it (but that could just be me..!). No-one here either; which is hopefully suggesting that its something you should be able to sort yourself, on your system.

I'm aiming to try the update here in about a week or so, after I finish this current band project. Not touching a thing til that's done..

[Gonga]

I do have my 32 and 64 bit plugins separated already. What I do not understand is why upgrading Cubase to 8.0.20 all of a sudden makes Cubase crash because of particular plugins.

Anyway, when I get the time for it, I´ll reinstall 8.0.20 and play around with the 32 bit plugins.

Thanks

Best Regards

Roman Empire

Once they're separated, then go through and make sure none of your 64-bit vsts are also in the 32-bit folder...if they are...delete. Then the 32-bit folder has vsts which are not found in the 64-bit folder. This always works for me. Hope it helps.

[Googly Smythe]

Wow... is that still the case..?

No, I'm a dumb-ass... I noticed that somehow I'd set the deafult gain in the pre-filter to -5db! Gawd knows how

However, the MIDI edit window problem is still there, and doesn't occur in my 7.5 installation (Win7 Ultimate, all 64-bit bar OP-X).

[Roman Empire]

I do have my 32 and 64 bit plugins separated already. What I do not understand is why upgrading Cubase to 8.0.20 all of a sudden makes Cubase crash because of particular plugins.

Anyway, when I get the time for it, I´ll reinstall 8.0.20 and play around with the 32 bit plugins.

Thanks

Best Regards

Roman Empire

Once they're separated, then go through and make sure none of your 64-bit vsts are also in the 32-bit folder...if they are...delete. Then the 32-bit folder has vsts which are not found in the 64-bit folder. This always works for me. Hope it helps.

You say "always works for me" as if it´s been happening alot to you during a longer period of time. But this never happened before the update to 8.0.20, which is only a few weeks old.
Yes, I´ve had crashes before due to incompatibility between bridge and 32 bit vst´s, but only upon loading projects or cubase itself. Never in an empty project when simply trying to see the (empty) instrument rack. So if you refer to previous issues as those described above, I´m not sure if it´s wise to think that they´re curable in the exact same way.
And, are you saying that you cannot have for instance vst64/synth1-64.dll and vst32/synth1-32.dll (two separate folders, one each for different bit numbers) anymore, but will have to delete the 32 bit version....?

[Guillermo Navarrete]

Hello,

I do have my 32 and 64 bit plugins separated already. What I do not understand is why upgrading Cubase to 8.0.20 all of a sudden makes Cubase crash because of particular plugins.

Anyway, when I get the time for it, I´ll reinstall 8.0.20 and play around with the 32 bit plugins.

Thanks

Best Regards

Roman Empire

Once they're separated, then go through and make sure none of your 64-bit vsts are also in the 32-bit folder...if they are...delete. Then the 32-bit folder has vsts which are not found in the 64-bit folder. This always works for me. Hope it helps.

You say "always works for me" as if it´s been happening alot to you during a longer period of time. But this never happened before the update to 8.0.20, which is only a few weeks old.
Yes, I´ve had crashes before due to incompatibility between bridge and 32 bit vst´s, but only upon loading projects or cubase itself. Never in an empty project when simply trying to see the (empty) instrument rack. So if you refer to previous issues as those described above, I´m not sure if it´s wise to think that they´re curable in the exact same way.
And, are you saying that you cannot have for instance vst64/synth1-64.dll and vst32/synth1-32.dll (two separate folders, one each for different bit numbers) anymore, but will have to delete the 32 bit version....?

Do you have any crash logs that you could send us or attach to the thread?
If you are in Windows you will find them under MyDocuments > Steinberg > Crash Dumps >

Best regards,
GN

[kelldammit]

I'm trying the demo after many years away, and mostly, no real surprises, but is there any way to tell what the values are for points when using volume curves on audio tracks (aka "clip gain" style automation)?

if you adjust the gain for the entire clip, it displays easily enough, but none of the points for actual curves show any information anywhere that i can see.

Also, very happy not to see the grey background window anymore when you close a project, but not cubase itself! Windows also no longer overlap underneath the taskbar. (this is all win8.1 x64)

[Roman Empire]

Hello,

I do have my 32 and 64 bit plugins separated already. What I do not understand is why upgrading Cubase to 8.0.20 all of a sudden makes Cubase crash because of particular plugins.

Anyway, when I get the time for it, I´ll reinstall 8.0.20 and play around with the 32 bit plugins.

Thanks

Best Regards

Roman Empire

Once they're separated, then go through and make sure none of your 64-bit vsts are also in the 32-bit folder...if they are...delete. Then the 32-bit folder has vsts which are not found in the 64-bit folder. This always works for me. Hope it helps.

You say "always works for me" as if it´s been happening alot to you during a longer period of time. But this never happened before the update to 8.0.20, which is only a few weeks old.
Yes, I´ve had crashes before due to incompatibility between bridge and 32 bit vst´s, but only upon loading projects or cubase itself. Never in an empty project when simply trying to see the (empty) instrument rack. So if you refer to previous issues as those described above, I´m not sure if it´s wise to think that they´re curable in the exact same way.
And, are you saying that you cannot have for instance vst64/synth1-64.dll and vst32/synth1-32.dll (two separate folders, one each for different bit numbers) anymore, but will have to delete the 32 bit version....?

Do you have any crash logs that you could send us or attach to the thread?
If you are in Windows you will find them under MyDocuments > Steinberg > Crash Dumps >

Best regards,
GN

Hi Guillermo,

I´ll have a look for that in a few days when I´m back home.

Best Regards

Roman Empire