KVR Audio

Rockscientist · Post by **Rockscientist** » Wed Feb 03, 2010 5:44 pm

Dang. OK, thanks

chrisholm · Post by **chrisholm** » Thu Feb 04, 2010 8:49 pm

Did you manage to check that preset bug thing on Rob Papen Blue?

umd · Post by **umd** » Fri Feb 05, 2010 3:07 am

I did, but I still don't know why it happens, sorry.

I'll keep trying.

chrisholm · Post by **chrisholm** » Fri Feb 05, 2010 9:51 am

Sure thing. Thanks for all the hard work. It's a great app.

Anheuser · Post by **Anheuser** » Sat Feb 06, 2010 5:09 am

Regarding East West PLAY (specifically Symphonic Orchestra), Cubase 5 and Win7 (64 bit):

I'm just getting going with PLAY and jBridge, but here are my observations so far:
- One way to reliably crash Cubase is to run PLAY in 'integrated GUI mode', open up the 'instrument list' (F11) and toggle the 'e' button for an instance of PLAY (OFF and then ON). By 'e' button, I'm referring to the button that minimizes/maximizes the instrument. When you try to maximize the plugin, you get the crash (the instrument GUI never gets displayed). Therefore, switching to 'separated GUI mode' prevents this crash, but it also makes it a little bit harder to figure out which instance of PLAY belongs to which midi tracks (assuming you're running more than 1 instance). If making PLAY work in 'integrated GUI mode' is not going to be possible in the near future, then perhaps adding some plugin identification info in the title bar of the separated GUI window would help? E.g. if the midi track is connected to '2 - play_VST_x64.32', then perhaps the same info can be printed at the top of the corresponding GUI window (so that it's easier to locate the correct instance)?

- I was previously running a few instances of PLAY in integrated GUI mode, and my CPU usage per instance of PLAY was abnormally high (25% per instance, I had about 3 to 4 instances going). I was also getting clicks/pops when I clicked on various areas of the PLAY GUI (probably because my CPU was getting maxed out). During that session I had multiple of instances of Symphonic Orchestra Kompakt edition active and 1 instance of Colossus (Kompakt also) active. I'll see if this happen now that I'm going to run in separated GUI mode.

As a side note, someone in the Cubase forums mentioned that putting all the PLAY midi tracks at the top of the sequencer is supposed to help keep things stable (a Cubase issue I assume?).

umd · Post by **umd** » Sat Feb 06, 2010 1:30 pm

Hello.

From my experience, Play doesn't like the integrated GUI mode very much, and it will need the "dirty close" option enabled, otherwise you'll be left with a hanged auxhost process running ( still investigating if this is a bug in my code ).

And unfortunately, I have no way of obtaining the track name from the main host, as there's no opcode in the SDK for that. It would require some sort of plugin/host code integration.

The separate GUI mode is not as pretty ( nor pratical ), but it's usually more compatible.

I still have a couple of things to try for the next update though, if you want to give a test build a try to see if it makes it any better for Play, please email me with your user data.

Thanks

Tone Control · Post by **Tone Control** » Tue Feb 09, 2010 9:55 pm

To use this with Protools, is it better to use Bidule then jBridge,
or the fXpansion RTAS/VST wrapper around the jBridge wrappers individually?

Has anyone tested jBridge with Protools?

Is it possible to have a jBridge for RTAS directly??

Cheers
Tone

bobbybland · Post by **bobbybland** » Sat Feb 20, 2010 10:03 pm

I have a question,I've purchased jbridge,but whats not clear to me is if I have a 32bit OS and want to run a 64 bit plugin in my 32bit OS,is this possible?

I already know a 64bit OS is recommended,but I wanted to check and see if it's possible to run in a 32bit OS using 64bit plugins.. ??

umd · Post by **umd** » Sun Feb 21, 2010 5:00 am

Hi.

No, that is not possible.

64bit OS's can run 32bit plugins, but not the other way around.

lightsfadelow · Post by **lightsfadelow** » Sun Feb 21, 2010 2:45 pm

At this point unless your audio HW is 64bit incompat, i think everybody should at least be running a 64bit OS with jbridge. there's debate as to whether to use a 64bit host... personally i'm running cubase 5.1.1 x64 and it works PERFECTLY with jbridge on Win7 x64.

LfmC · Post by **LfmC** » Mon Feb 22, 2010 7:32 pm

I'm thinking of buying jBridge as I'm tired of waiting for the damned Steinberg to fix their mess..

However, If I'm gonna go this route , I'd really like to "set and forget" the entire bridge. And that's a bit hard when every plugin is stamped with the jbridge box. A (sorry but) quite ugly win 3.1 box at the bottom of each plugin. Is there a way to disable it and have the plugins load without it?

lightsfadelow · Post by **lightsfadelow** » Mon Feb 22, 2010 11:51 pm

LfmC wrote:I'm thinking of buying jBridge as I'm tired of waiting for the damned Steinberg to fix their mess..

However, If I'm gonna go this route , I'd really like to "set and forget" the entire bridge. And that's a bit hard when every plugin is stamped with the jbridge box. A (sorry but) quite ugly win 3.1 box at the bottom of each plugin. Is there a way to disable it and have the plugins load without it?

well, you can't really "set and forget" since jbridge works by creating a fake DLL in the x64 VST folder so every time you install a new 32bit plug, you have to run the jbridge utility. it's pretty easy, though.

also, i'm not sure you can turn off the jbridge UX in the plug, as it's needed to set the plugin settings in case the defaults don't work. i guess if it really bothers you that could be a deal breaker, but jbridge is really solid, coupled with the fact that vstbridge doesn't really work at all and is not getting updated. so jbridge is the only game in town until everything is native x64.

i have yet to see a 32bit plug NOT work with jbridge, so my reco is just put up with the extra UX. and, remember, cubase 5 still uses the win3.1 windowing system anyway

LfmC · Post by **LfmC** » Tue Feb 23, 2010 9:59 am

ok let's say I get over the visual violation of my sexy looking plugins..

2. question:
what happens when a bridged plugin I used a lot get's a 64bit version. Does that mean I have to re-open each project, re-save each preset and reload the VST? Or is there a way to name the wrapped plugins the same as the original, so when I replace the bridged version with an unbridged one, cubase loads it with the same preset?

umd · Post by **umd** » Tue Feb 23, 2010 11:25 am

Hi.

If it's the same plugin, its future 64bit version will open data saved by its bridged 32bit equivalent.

However, users have reported that they needed to rename the <name>.64.dll/<name>.64.txt files to <name>.dll/<name>.txt so that Cubase would open older projects with the same plugin, but now bridged.

thedude01 · Post by **thedude01** » Tue Mar 09, 2010 5:15 am

Having some trouble with Kontakt 4.05 and Cubase 4. 64bit Windows 7, 32bit Cubase 4, 32bit Kontakt. EVERY time i save a project with a jbridged instance of Kontakt 4.05 upon repoen of the project Cubase crashes. This never happens when just using Kontakt without jbridge. I also have many VSTi's that operate flawlessly through jbridge. Am I doing something wrong or is this a known issue?

Need testers for my x86 to x64 vst adapter