KVR Audio

Home Studio 87 · Post by **Home Studio 87** » Tue Nov 16, 2010 1:49 pm

any news ?

the new update is working with Kontakt 4 (32 Out) ?
thanks

umd · Post by **umd** » Tue Nov 16, 2010 2:22 pm

Hi.

Yes, it's coming along fine, I am still making some tests though.

And yes, it will load the 32 output version of Kontakt fine.

XL · Post by XL » Sun Nov 28, 2010 1:00 am

I am using latest version of jbridge under Cubase 5.5 x32 with 2 instances of jbridged Kontakt 4 x64 (16 outs) in a project. When loading the project, the first instance (approx. 1.7 GB sample data) loads fine, while the second instance (approx. 4 GB sample data), after loading, reports an "opcode 24" error, but loads fine also. Is there some way to get rid of this error message since I have to click "ok" during loading each time?

Also, the first time when I open the GUI of that second instance, it is completely empty. Closing and re-opening brings back the GUI. I am using integrated GUI mode which has always worked fine under Cubase.

umd · Post by **umd** » Sun Nov 28, 2010 1:02 am

Hi.

I've seen this happening too, I fixed it for the next update, could you pm me with your email address for an updated build?

Thanks.

XL · Post by XL » Sun Nov 28, 2010 8:50 am

No Opcode 24 error and no empty GUI at first opening with the updated version. Great! Keep up this brilliant work!

umd · Post by **umd** » Sun Nov 28, 2010 9:10 am

Glad that worked.

Thanks

XL · Post by XL » Wed Dec 01, 2010 9:41 pm

Hm, I am having another problem which I do not know whether it is cubase-related or jbridge-related. I have these two jbridged Kontakt 4 instances, and when I freeze the first it's ok, but when I freeze the second, everything is shifted by one bar exactly, meaning that the frozen tracks are one bar too late in time. When printing the mixdown of the whole song offline, it is working. Do you think this could have something to do with jbridge? This never happened before, I am always using two Kontakt instances in my project and I am always freezing them during mixing...

TS-12 · Post by **TS-12** » Wed Dec 01, 2010 10:50 pm

I often get problems with jbridge in cubase 4, when reopening a project the plug-in's patch settings are gone, this mostly happens with Omnisphere and StylusRMX plug-ins. I had many projects messed up like this..

umd · Post by **umd** » Thu Dec 02, 2010 2:26 pm

Hi.

@XL:
Could you try them unbridged and check if the same happens? That's the best way to be sure. But it's something that has never been reported before and that I have never experienced here either.

@TS-12:
Any difference with the latest update ( if you haven't received it please pm me )? That is something that has been reported with some plugins but which unfortunately I haven't been able to re-create here, making it harder to solve.

eddu · Post by **eddu** » Thu Dec 02, 2010 4:22 pm

hi,

i am jbridging stylus and omnisphere in Cubase 32b under win7 64 bits and they just dont show up in the VST list (unlike many other non Spectrasonics vstis). I read somewhere it could be the file name so i change both, the dll and the txt for each instance but they dont seem to be recognized by cubase.

Tried to jbridge both 32 and 64b versions but they both are missed by cubase.

Thanks

umd · Post by **umd** » Fri Dec 03, 2010 11:45 pm

Hello.

Could you try a full plugin re-scan in Cubase?

eddu · Post by **eddu** » Sat Dec 04, 2010 12:08 am

I already tried. Also tried to add the jbridged plugins on diferent paths on the hd. No way, Spectrasonics instruments keep being missed by cubase.

umd · Post by **umd** » Sat Dec 04, 2010 12:21 am

Hello.

Hum, I know from the reports that some users are working with Omnisphere "jbridged" in Cubase5, so there must be a solution ( unfortunately I don't have that plugin here to try it ).

A few more things to try:
- Try renaming the bridging files so that they match exactly Omnisphere's plugin name ( if they don't already ).
- Make sure that Cubase isn't scanning the plugins that you want to bridge, to avoid conflicts, only their bridging files.
- Make sure you created the correct bridging files, according to your main host's architecture ( 32bit or 64bit ).

Are those the only plugins you're trying to bridge? If not, all the other ones are recognized?

Let me know what happens.

chrisholm · Post by **chrisholm** » Sat Dec 04, 2010 12:48 am

I'm geting opcode 14 on Waves Q10, cant remember getting that before. using dll made with shell2vst

umd · Post by **umd** » Sat Dec 04, 2010 2:21 am

Hi, try enabling the "prevent main host control when the GUI window is closed" option.

If the problem remains, please email me with you user details, I've been testing something here related to the opcode 14 error, which you may want to try.

Need testers for my x86 to x64 vst adapter