Update: Resolution posted to force Cubase to re-scan XTC plugins without renaming hassles:
http://www.planetz.com/forums/viewtopic ... &forum=3&0
===========================================
[Original Post]
I'm currently having an error if I try to save a CubaseSX3 Project if I have any synth from SynthPackage1 (miniscope, mkII, bluesynth, vectron player, etc) loaded in a VSTi slot in the project. Cubase gives a "serious problem" error -
No other Synths or Effects being loaded into my XTC/Cubase project cause this problem.
History: on initial installation of the XTC setup, loading a synth from SynthPkg1 to VSTi slot caused an error on finding the necessary DSP file for SynthPkg1 (Scope Error). I copied all DSP files from the Scope 4.0 Install CD to SFPAppDSP and have since been able to load the synths without error. Now, the same group of synths cause the save error in Cubase.
I've also deleted the DSP.IDX file and let it be rebuilt by Scope (also checked off all read-only, etc. file attributes for all files under SFP main folder).
If you have any insights, I'd be appreciative. Thanks!
<font size=-1>[ This Message was edited by: narly on 2005-06-22 11:48 ]</font>
<font size=-1>[ This Message was edited by: narly on 2005-07-04 16:27 ]</font>
Synth Package 1 DSP Error / Cubase SX crashes on save (Solve
More research and it seems like that the Plugin info stored in Cubase is invalid because the devices were attempted to be loaded while the DSP file problem existed. Specifically, the synths are shown in the plugin information as having '0' parameters.
New Question: Short of blowing away Cubase installation and starting over, is there another way to get the correct info into Cubase SX 3's Plugin-Information store?
I have tested by re-naming my .dev and matching .dll files to a new name and Cubase put's it into it's database as a new plugin. However, anything with the original plugin name ends up with the bogus plugin-data from the initial failed plugin-scan...
New Question: Short of blowing away Cubase installation and starting over, is there another way to get the correct info into Cubase SX 3's Plugin-Information store?
I have tested by re-naming my .dev and matching .dll files to a new name and Cubase put's it into it's database as a new plugin. However, anything with the original plugin name ends up with the bogus plugin-data from the initial failed plugin-scan...
I tried to cycle the "Use" flag in the Plugin Information window, with restarts of SX between, but no joy.
Problem is, it seems that I had the wrapper in place, so Cubase took it's info from there and makes it a valid plug-in as far as it is concerned - even though the .dev wasn't there to provide all the necessary info. Once it's in there and showing 0 parameters for the plugin, it's toast - no way to get the plug to work in Cubase under that name (the plug WILL actually work once the .dev is in place, but it borks out when saving the project). Renaming the dev/dll files must be the only way...cause Cubase apparently won't let you rebuild/modify/wipe the VST database once it has something in there. I have a post on Cubase.net, but no one is apparently capable there...
Not to give up hope - if you have other ideas, I'll be glad to give it a try!
BTW; purging the Cubase install and re-installing doesn't seem to get things reset either...
<font size=-1>[ This Message was edited by: narly on 2005-06-22 17:56 ]</font>
Problem is, it seems that I had the wrapper in place, so Cubase took it's info from there and makes it a valid plug-in as far as it is concerned - even though the .dev wasn't there to provide all the necessary info. Once it's in there and showing 0 parameters for the plugin, it's toast - no way to get the plug to work in Cubase under that name (the plug WILL actually work once the .dev is in place, but it borks out when saving the project). Renaming the dev/dll files must be the only way...cause Cubase apparently won't let you rebuild/modify/wipe the VST database once it has something in there. I have a post on Cubase.net, but no one is apparently capable there...
Not to give up hope - if you have other ideas, I'll be glad to give it a try!
BTW; purging the Cubase install and re-installing doesn't seem to get things reset either...
<font size=-1>[ This Message was edited by: narly on 2005-06-22 17:56 ]</font>
how about-
start cubase, open the plugin info window, remove the shared vst folder, point to a folder with no plugins and rescan.
restart cubase, remove the new(bogus) vst folder, point to the old vst folder and rescan.
restart cubase(in xtc) and enable any plugs that are not enabled. this may help.
if this doesn't work, someone here who's a little more informed about registry files may be able to tell you what file is keeping these plugins from working properly, but i would suggest that nuking everything and starting over properly might save a lot of time and trouble in the long run(after backing up your personal files, of course).
start cubase, open the plugin info window, remove the shared vst folder, point to a folder with no plugins and rescan.
restart cubase, remove the new(bogus) vst folder, point to the old vst folder and rescan.
restart cubase(in xtc) and enable any plugs that are not enabled. this may help.
if this doesn't work, someone here who's a little more informed about registry files may be able to tell you what file is keeping these plugins from working properly, but i would suggest that nuking everything and starting over properly might save a lot of time and trouble in the long run(after backing up your personal files, of course).
The swapping of paths didn't seem to help when I tried it. I ended up reverting to an earlier image of my system and then better orgainzing everything before starting in XTC mode. For any isolated plugins that still didn't appear to be in the plugin-information "database" correctly, I went ahead with renaming the VST wrapper and Cubase .dev files which get's the correct info into the dataset. Simply removing them or relocating them didn't seem to help. I'd hoped for a way to force Cubase to re-scan all plugins, whether by nuking the original dataset (file, registry, etc.), or some special Cubase command - but that's apparently not happening.
I'd had a similar thing happen before when I used an incorrect wrapper dll (synth<>effect). Cubase wouldn't recognize the proper plugin type after swapping the wrapper dll - I had to do the rename thing...pretty wierd! :?
I'd hoped for a way to force Cubase to re-scan all plugins, whether by nuking the original dataset (file, registry, etc.), or some special Cubase command - but that's apparently not happening.I'd had a similar thing happen before when I used an incorrect wrapper dll (synth<>effect). Cubase wouldn't recognize the proper plugin type after swapping the wrapper dll - I had to do the rename thing...pretty wierd! :?