Need testers for my x86 to x64 vst adapter

VST, AU, AAX, CLAP, etc. Plugin Virtual Instruments Discussion
Post Reply New Topic
RELATED
PRODUCTS
jBridge jBridgeM

Post

I don't get Waves V8 to work. I bridged the waveshell (deselect 'thorough file analysis) but Cubase 6 64 bit quit during the scanning of the plug-ins with an error message. Cubase scans most of the plug-ins from Waves, the error message is always at scanning the IR 360 tools.
I deinstalled Waves V7 at the installation of V8.

Post

I got it to work by creating a sub-folder in my x64 VST plug-in folder which only contains the bridged "waveshell8.64.dll" and ".txt" files. Then I deleted all VST-related information of Cubase (in something like "documents and settings/user/application data/steinberg/cubase 6_64"), started Cubase and set only this sub-folder as the VST2 folder. At the next start-up, Cubase starts scanning only Waves 8. I had crashes while scanning some "IR" plug-in, too, and had to repeat the scanning after another crash (at some later plug-in) twice. Finally, Cubase got through all the Waves plug-ins, which took very long, and then I set the VST2 folder to my standard VST2 folder, which means that Cubase does not scan the Waveshell8 any more (because it remembers that it has already scanned that sub-folder), but only all other plug-ins.

Post

Great, thanks for the tip, it works now. But I didn't do anything but starting Cubase x64 once more :-) It seems that Cubase has problems with some of the bridged IR plug-ins. Cubase has scanned all other VST2 plug-ins before so only the waveshell was scanned at start, no need for creating the subfolder in the way you described. And after 3-4 starts Cubase got through the IR plug-ins...

Post

Hi, guys.

I've been investigating this same issue for another person, could you email or pm me with your user details?

I am testing a more "elegant" solution for this. :)
Free MIDI plugins and other stuff:
https://jstuff.wordpress.com
"MIDI 2.0 is an extension of MIDI 1.0. It does not replace MIDI 1.0(...)"

Post

pm sent.

Post

Can somebody please verify an issue I'm facing:

Win7x64, cubase6x64, vst2 plugin BootEQmkII x32 Jbridged to x64:

1) playback an Audio file in cubase
2) insert jbridged BootEQmkII in an insert Slot, Open the GUI
3) change the program of BootEQmkII in the Plugin GUI

I get Audio stutter and/or asio Buffers repeating for a few seconds. Then normal playback.

When Switching programs After that, I get CPU spikes

Does Happen with a Lot of Plugins, BootEQmkII is just an example...

Post

Hi! where can I download a new demo(1.26 or 1.27)for testing?

Post

Hello.

Email me and I'll send you a beta version of the latest build I'm working on.

The next official version will probably be 1.28, as 1.26 and 1.27 had some unexpected issues with some plugins that worked well in 1.2, so I am taking my time to refine this one, to make sure there's no regressions.
Free MIDI plugins and other stuff:
https://jstuff.wordpress.com
"MIDI 2.0 is an extension of MIDI 1.0. It does not replace MIDI 1.0(...)"

Post

Hi.
I got a problem with JBridge 1.27 and Nebula 3 x64 (1.3.465 latest) wrapped in Sonar X1A (x32).
When Sonar load a project with a wrapped Nebula x64 i got that error popup :

"auxhost64.exe - System Error : the program can't start because cudart64_30_14.dll is missing from your computer.Try reinstalling the program to fix this problem.".

Well im with an ATI card not nVidia so CUDA is not installed on my system,an you can't install,of course!
I must click OK to all the popus (for all the Nebula wrapped instances in the project) and after all works fine,but that's really annoyng!
There's any workaround?
Can you send me the beta 1.28 so i'll give it a try?
JB is registered to my real name : Carlo Gosamo.

Thanx.

Post

Hello.

Check your email, please. :wink:

( let me know if it makes any difference for the missing *.dll message )
Free MIDI plugins and other stuff:
https://jstuff.wordpress.com
"MIDI 2.0 is an extension of MIDI 1.0. It does not replace MIDI 1.0(...)"

Post

Sorry Joao,i've just try the beta (unistalling the old before) but the error message remains.Nothing changes.
I've forgot to say that the error appears every time you load an instance of the wrapped Nebula not just only when you open a saved project in Sonar.

Post

Hello.

Could you confirm if it also happens when you load the plugin unbridged in a 32bit host?
Free MIDI plugins and other stuff:
https://jstuff.wordpress.com
"MIDI 2.0 is an extension of MIDI 1.0. It does not replace MIDI 1.0(...)"

Post

The error don't appear in the plugin when unbridged!Normal x32 Nebula works without problems.
I don't have Sonar x64 installed to try if the problem appears with a regular x64 Nebula (witouth JB wrapping).

Post

Hi, Carlo.

Hum, that's weird, that dll seems to be related with NVIDIA's CUDA. Have you ever had any NVIDIA card in your system?

The 32bit Nebula, when bridged, doesn't show that message, you say? In that case, could you try the 64bit Nebula in a 64bit host and see if it also shows the same message?

( So that we can be sure if it's an issue with the plugin itself or not )
Free MIDI plugins and other stuff:
https://jstuff.wordpress.com
"MIDI 2.0 is an extension of MIDI 1.0. It does not replace MIDI 1.0(...)"

Post

I know that .dll is cuda related.
I have an Nvidia card in the past but i've uninstall it from months.
Also i've try nebula x64 on sonar x1 x64 and all works fine.No error popup at loading.
Just to give your some clues,Nebula comes also as "Cuda powered" there's an option to use the video card to "accelerate" the Nebula dsp's to free cpu power.
Anyway im using a normal Nebula without Cuda option activated,and as you know cuda don't works with ATI and i've uninstalled all related to nVidia/CUDA,before installing ATI card some months ago.

Post Reply

Return to “Instruments”