- JBRIDGE FILE NOT FOUND PATH IS NOT WORKING INSTALL
- JBRIDGE FILE NOT FOUND PATH IS NOT WORKING 64 BIT
Yet the plugin list shows it’s correct location. I loaded some VST’s succesfully, but now I tried to load my CamelPhat plugin, from a new location, and Cubase says: Unkown architecture or file not found (Is D:\VSTx32-Plugins…CamelPhat3.dll the correct path? ), which is the wrong address, not specified by me. Now a strange thing happened, which perhaps might make some of you who actually know what you are doing, be able to pinpoint the problem. It’s in finnish and I will try to translate it later but now I gotta go for now. dll’s with JBridge from the original 32-bit files, and it reports a problem with “auxhost”. But now I cannot load fresh instances of the plugins in a different directory without Cubase crashing. Java Access Bridge files listed in Table B-1 into the JRE 1.4.2 directory.
JBRIDGE FILE NOT FOUND PATH IS NOT WORKING 64 BIT
Changing the shared folder to “C:\Program Files\Common Files\Steinberg\VST2” solved the problem. Java Access Bridge and JAWS are not certified on Windows Vista at this time. I solved the problem by buying/using JBridge which is a 32 bit to 64 bit bridge. Embarrassingly, it was a screwup on my part I think. Next time I start Cubase, the path “D:\JBridgeVST-Plugins” will have returned. However, updating by pressing “Update” does NOT remove the plugins from the list after removing the folder from the locational tree, nor does pressing “Update Plug-in information”. Removing “D:\JBridgeVST-Plugins” from the list with the remove button, removes it from the list. But I don’t know what to do next.Ĭ:\Program Files\Common Files\Steinberg\VST2īoth of these locations are visible every time I start. I would hope to get Cubase to at least open without these problems, and hopefully then be able to reopen the project. I am kind of lost, I don’t really know what I’m doing at this point anymore.
JBRIDGE FILE NOT FOUND PATH IS NOT WORKING INSTALL
Why does Cubase load the old, crashed location for the VST plugins even after initializing and re-installing? Thanks richierichie-ThinkPad-T430: go version Command 'go' not found, but can be installed with: sudo snap install go version 1.11.2, or sudo apt install golang-go sudo apt install gccgo-go See 'snap info go' for additional versions. However, now it seems I can’t even start a new project and get my plugins to work, or even make sense of what it is that Cubase is trying to load. I thought at the very least I would like to open the project without the plugins and just continue from there. However, every time Cubase starts it still loads the old plugin paths. I did manage to get the project open by removing the faulty plugins. Everytime I open Cubase it remembers the old path for the VST2 plugins. Waveshell crashes again and now the projects will not load again even with the renamed file, unless it was renamed yet again. Wow Success All my projects loaded again But it is not over yet. I renamed the file to WaveShell-VST3 9.2圆4BLAH.vst3. So yeah, removed Cubase, initialized preferences, also tried different combinations, like renaming Cubase Prefs but not VST folder, the other way around and so forth. This file is found here and this put me on the right path: C:Program FilesCommon FilesVST3. Now it seems that even though I initialize my preferences, Cubase for some reason still remembers the VST folder location. In fact, even loading an older version of the project made Cubase 5 64-bit crash. Afterwards opening the project resulted in a crash. Yesterday I got a BSOD while loading a project.