KVR Audio

Kode · Post by **Kode** » Mon Dec 14, 2009 3:16 am

Thanks Umd, i test the Zebra2 demo with separate Gui and work fine, no more waiting but i like the JBridge integrated GUI because with separated GUI i can not view the Cubase mixer when work with Zebra2 and vice versa, only the Cubase Tracks are visible, but is a minor problem and the Zebra2 work fine now.

I hope you can fix this problem with the Separate GUI-Cubase main window and Zebra in future. Thanks for this great plugin, i'm very happy with JBridge¡¡.

Best Regards.

umd · Post by **umd** » Mon Dec 14, 2009 11:18 am

I agree the integrated mode is prettier.

But the separate GUI mode is usually more compatible.

When you have the time, could you try the following?

The first time I start Cubase and add Zebra, I get that GUI open freeze, but after killing it ( or waiting a few seconds and close it ) and re-starting it, doesn't seem to happen any more. Could you confirm if that happens there as well?

Thanks.

Kode · Post by **Kode** » Mon Dec 14, 2009 3:38 pm

Yes, the Integrated GUI mode is much pretier

Hmmmm, my problem is diferent, if i add zebra and open it the first time, it open without problem and without freeze, but when closed for first time and open it again then Zebra freeze for about 20-30 secods and next times open-closed is the same 20-30 seconds freeze again...if i kill it or restarting again then freeze for 20-30 seconds...I need to quit Cubase 5.1.1 64bits and restart it to have a single Zebra start without freezing, after that (closed-open) freeze again.

umd · Post by **umd** » Tue Dec 15, 2009 6:13 pm

Ok, thanks for the info.

I'll need to keep investigating this, so far I haven't found why it happens.

Kode · Post by **Kode** » Tue Dec 15, 2009 8:09 pm

OK, thank you very much.

shifter7 · Post by **shifter7** » Mon Jan 04, 2010 8:24 pm

I recently switched to Cubase4 X32 (from Cubase4 X64) and using Windows 7 X64 6 GB ram. I had been using jbridge to bridge my 32bit plugins. What would be best now? Use jbridge to bridge my 64 bit plugins to Cubase x32 and also to bridge my 32 bit plugins? What is the benifit of bridging these? Any advise would be appreciated.
shifter7

umd · Post by **umd** » Mon Jan 04, 2010 8:35 pm

Hi.

No way is "better" than another, really.

Some people prefer to keep using the 32bit version and just bridge "larger" 64bit samplers.

When it comes to sound, it will sound the same both ways, so it's all a matter of how many and which plugins you need to bridge.

shifter7 · Post by **shifter7** » Wed Jan 06, 2010 7:53 pm

Ok, let me ask this, what are advantages of bridging Kontakt 3 X64 to Cubase X32? I'm on Windows 7X64 with 6gb ram. Thanks,

shifter7

umd · Post by **umd** » Wed Jan 06, 2010 8:36 pm

Hi.

The advantage is that if you're reaching the memory limit for your 32bit Cubase you can make use of the extra RAM you wouldn't be able to use otherwise.

In your case, you should also be fine with the 32bit version of the plugin bridged, since you only have 6Gb of RAM.

mrmine · Post by **mrmine** » Fri Jan 22, 2010 9:19 am

i've bought jbridge 1.18.

i've installed cubase 5 32bit under windows 7 x64.
i've applied jbridge to c\program files(x86)\steinberg\vstplugins
obtaining a c\program files(x86)\steinberg\vst-jbridge-plugins folder.

i've one stupid question:

in cubase5 i've to load the original VSTi.dll(i mean,does it recall automatically jbridge)or the VSTi.32.dll ?

thnkas in advance

standalone · Post by **standalone** » Fri Jan 22, 2010 10:33 am

You got to "hide" the original DLL from Cubase and let it scan the Jbridge version instead.

BTW, I purchased Jbridge this week and I'm really happy with it. I use it in XP32 to overcome Cubase's memory restrictions inside a 32bit enviroment, and it works!. Now I can access all the ram without a problem.

I made bridges for Kontakt, Omnisphere, Wusikstation and Eastwest's Play. All work fine except the last one (no surprise

). Every time I click on the GUI it disappears, when I try to switch "always on front" as suggested, Cubase crashes.

It's no big deal for me, as I can use it without a bridge and let it share Cubase's assigned memory, while the other bridged plugins have their own. But now that there is a free version of Play avaliable I guess it's easy to test.

umd · Post by **umd** » Fri Jan 22, 2010 12:16 pm

standalone said it.

Regarding Play, I have been experiencing some problems here too. With the current implementation, it will need the "Dirty close" option enabled otherwise its auxhost won't terminate ( at least in my machine ).

But no crashes, though I must say I haven't run any complex setup. Does it make any difference if you switch to the separate GUI mode?

standalone · Post by **standalone** » Fri Jan 22, 2010 4:34 pm

umd wrote:standalone said it.

Regarding Play, I have been experiencing some problems here too. With the current implementation, it will need the "Dirty close" option enabled otherwise its auxhost won't terminate ( at least in my machine ).

But no crashes, though I must say I haven't run any complex setup. Does it make any difference if you switch to the separate GUI mode?

Hey, that works, you have a lot of tricks under your sleeve!.

I got to be careful to not close the GUI's window, as auxhost crashes if I do. Otherwise it seems to work fine. I enabled the dirty close option, just in case. I have to check what happens when not using this.

The rest of the plugins keep working without a problem inside their bridges.

thereynolds · Post by **thereynolds** » Mon Jan 25, 2010 5:46 am

Hi UMD,

What's an Opcode 53 error? I received it when changing scenes in forte.

Can you provide a list of the different Opcode errors so that if encountered, one knows where to begin looking? Or is that not such a good idea?

Thanks,

Mike

umd · Post by **umd** » Mon Jan 25, 2010 11:21 am

Hi.

Opcode 53 is effIdle, according to the SDK.

For the user, it doesn't matter much to know what they mean, it's just to help me identify the problem.

I can reproduce this opcode 53 error with some plugins here too, and I am working on a fix/workaround for the next update.

Please email me with your user details so I can send you a test version with that fix.

Thanks.

Need testers for my x86 to x64 vst adapter