KVR Audio

Restless · Post by **Restless** » Mon Mar 22, 2010 10:27 pm

Olá João

I am experiencing some issues with the new Soundtoys bundle and windows 7 64/Cubase 5.1 64.

When I load a project with any soundtoys plugs I get a message about a a crash and two opcodes are usually mentioned. I can use them inside a Kore 2 FX with Jbridge, but not on their own.

I can send you a project, if it helps.

Thanks

Nuno

umd · Post by **umd** » Mon Mar 22, 2010 10:33 pm

Olá, Nuno.

Sure, send me the test project and I'll give it a run here.

Cheers.

Pinnsvein · Post by **Pinnsvein** » Tue Mar 23, 2010 11:00 am

Hi again J,

I tried to bridge a Waves plugin but I need to reinstall it. Now everytime I launch Cubase, JBridge is asking for the missing file (which was deleted when I uninstalled). Is there a way to configure Jbridge to stop searching for this missing file? (Waves shell.dll)

umd · Post by **umd** » Tue Mar 23, 2010 11:31 am

Hi.

Sure, you just need to locate the folder where you placed the bridging files and remove the .dll and .txt that correspond to the Waves shell.

Cheers.

themossinator · Post by **themossinator** » Wed Mar 24, 2010 10:34 pm

umd wrote:Hi.

Any difference with the separate GUI mode for the remaining problems?

No, for impOSCar the crosshair is still there even with sluggish hack and seperate GUI mode and the control is somehow different - its almost like the knob control is set to circular mode, or thats its not set to circular mode, i dont exactly know but its not how it should be - its the same for all my uad plugs as well

umd · Post by **umd** » Thu Mar 25, 2010 10:28 am

Hi.

I am seeing the crosshair too here with the demo, I'll see if I can find what causes it.

Pinnsvein · Post by **Pinnsvein** » Thu Mar 25, 2010 6:02 pm

Just to highlight a problem I have experienced a few times when I have had to remove a VST instrument or effect (such as Waves and EZ drummer which I had some problems with).
After I uninstalled these programs, I also uninstalled manually the bridged .dll files that were created with Jbridge. When I thereafter start Cubase, the program sometimes freezes during the loading procedure (when Midi Device Mgr comes up). Other times, my installed Midi devices had disappeared and I had to install them everytime I launch Cubase. I have also had problems with my ASIO driver which did not connect properly in Cubase.

After a complete uninstall / reinstall of Cubase, everything works fine again however, incl. my JBridged VSTs.

I do not know if you had this problem before but it has now happened several times (and can only be fixed by reinstalling Cubase). Perhaps the system does not like the manual deleting of the Jbridged .dlls? Maybe a function should be added in Jbridge so that you can properly uninstall the Jbridged VSTs if necessary?

paveloso · Post by **paveloso** » Thu Mar 25, 2010 6:21 pm

Hey João!

Congrats on a great little app, man! This is a VERY useful tool indeed.

I've successfully bridged all my x86 plugins, except my Waves plugs (V7 Waveshell). Is this a known limitation of jBridge? Might there be a workaround?

Many thanks in advance!

umd · Post by **umd** » Thu Mar 25, 2010 6:58 pm

Hi.

@Pinnsvein:

I don't know why your MIDI devices disappeared, but I assure you that your problem has nothing to do with jBridge ( and you should delete the corresponding bridging files if you uninstall a plugin, so what you you did was correct ). For your host, it's just like a regular plugin and it doesn't access the MIDI devices subsystem.

I would bet on a driver issue.

@paveloso:

Thanks, glad it's being useful to you.

Shell plugins (i.e., Waves) aren't supported by the current 1.19 version, you'll need to use an utility called shell2vst to create regular VST's from the Waves shell, and then bridge the created files.

( I am working on an update which will support shell plugins properly )

Here's a copy/paste from a post I found describing shell2vst's usage:

1 - download and unzip this: http://www.xlutop.com/buzz/zip/shell2vst.zip
2 - copy the extracted shell2vst.exe into the C:\Program Files\Waves\Waveshells folder (this just makes it easier to use)
3 - drag and drop each "WaveShell-VST x.x.x.dll" onto the shell2vst.exe
4 - that will create a folder C:\Program Files\Waves\Waveshells\Waves that contains all the plugins as DLLs
5 - Copy that Waves folder into your shared Vstplugins folder
6 - Remove the WaveShells from your shared Vstplugins folder

paveloso · Post by **paveloso** » Thu Mar 25, 2010 7:12 pm

umd wrote:Hi.

@paveloso:

Thanks, glad it's being useful to you.

Shell plugins (i.e., Waves) aren't supported by the current 1.19 version, you'll need to use an utility called shell2vst to create regular VST's from the Waves shell, and then bridge the created files.

( I am working on an update which will support shell plugins properly )

Here's a copy/paste from a post I found describing shell2vst's usage:

1 - download and unzip this: http://www.xlutop.com/buzz/zip/shell2vst.zip
2 - copy the extracted shell2vst.exe into the C:\Program Files\Waves\Waveshells folder (this just makes it easier to use)
3 - drag and drop each "WaveShell-VST x.x.x.dll" onto the shell2vst.exe
4 - that will create a folder C:\Program Files\Waves\Waveshells\Waves that contains all the plugins as DLLs
5 - Copy that Waves folder into your shared Vstplugins folder
6 - Remove the WaveShells from your shared Vstplugins folder

Awesome - will try it later today. Thanks, mate!

chrisholm · Post by **chrisholm** » Mon Mar 29, 2010 3:34 pm

Haha. I just realized I DON'T have to re-bridge all my plugins every time there is a new version of the program. I had done that the two previous times, it took ages to go through everything and rebridge them, I thought the bridged files are all "standalone" didn't realize they are just connected to the installed jbridge program. Well, good to know

Now I just installed the new version and I noticed all the bridged plugins show the 1.2 version

XL · Post by XL » Wed Mar 31, 2010 9:39 pm

I have been working with jbridge now for quite a while. No issues, except when re-scanning plug-ins for whatever reason: I always get opcode 1/opcode 222222 while initializing some jbridged NI plug-ins (I think Kontakt 3 and Kontakt 4). I had some crashes with bridged 64bit Kontakt 4 in 32bit Reaper, but most times it works.

Recently, I have bought Abbey Roads 60s Drums from NI which is actually a Kontakt program with some GB of samples. The GUI is quite advanced for Kontakt 4, I think it is more elaborate than other NI Kontakt GUIs. Now, this specific (jbridged from x64 to x32) Kontakt program crashes very often, so I cannot work with it. It crashes most times when closing the plug-in GUI, but also sometimes when hitting some slider etc. in the plug-in GUI. And, which is the worst part, it crashes almost always when opening a song in which the plug-in GUI is (or should be) open after loading. Reaper x32 freezes while building up the track FX window content (displaying the plug-ins) after loading.

In Reaper x64, it works (using the x64 version of Kontakt 4), though it takes a little time when closing the track FX window until Reaper is ready again (which indicates that Kontakt "does" something when closing the GUI).

Does anybody know a solution?

umd · Post by **umd** » Wed Mar 31, 2010 9:53 pm

Hi, are you using the 8 or 16 out version of Kontakt bridged?

When it crashes, does it show any error message with the opcodes that failed?

XL · Post by XL » Wed Mar 31, 2010 10:17 pm

I am using 8 out version. When it crashes, Reaper freezes completely. There is no error message.

lightsfadelow · Post by **lightsfadelow** » Thu Apr 01, 2010 12:57 am

All of the NI Komplete 6 synths except Reaktor are available in x64 flavors... why do you need to jbridge them?

Need testers for my x86 to x64 vst adapter