Jupiter-8v Not Compatible w/ Cubase 5 64-bit?

[Undercoverman]

Does anybody have Jupiter-8v working under Cubase 5 64-bit? Every other synth in the Arturia V Collection I just purchased will load perfectly (when updated to the latest versions!) but Jupiter-8v just will not load at all. It crashes the 'VSTBridge', which I think is what allows 32-bit VSTs to work in 64-bit programs.

It loads without any trouble whatsoever in standalone mode, and I can load the vst in this program here: http://www.hermannseib.com/english/vsthost.htm When loaded, the sound is fine and thankfully somewhat reminiscent of the real thing. I noticed that the interface is far more visually appealing and 'complicated' compared to the others in the V collection - is it (the software) so different that it causes issues?

Downgrading to 32-bit is not an option for me - I use lots of sample heavy, RAM intensive plugins (like Eastwest's Pianos software) that benefit massively from the extra RAM. Does anybody have any workarounds or tweaks to get it running?

[Undercoverman]

Ah, I found one myself:

http://jstuff.wordpress.com/

JBridge, a substitute for VSTBridge. It runs as a wrapper, so you can get Jupiter-8V running in Cubase 64. Bad news is that it costs 10 EUR to buy a version that doesn't run out after 30 minutes - but that's negligible. There's no added latency and no drop in functionality. It seems like the answer to my woes - should it turn out not to be, I'll let you know.

[thared33]

I have the exact same problem. The VSTBridge keeps crashing. I bought the V Collection mainly for the Jupiter-8V... so that's just my luck I guess.

[thared33]

I just contacted Customer Support so I'll let you know what they say. I hope an update will be released that fixes this. That was the softsynth that I was most looking forward to using.

[Undercoverman]

You and me must be of like minds, thared. Similar setups and we were both looking forward to the JP8V the most out of the V collection! I've consoled myself by being amazed at how much the ProV sounds like its real life equivalent - that said, I would very much like the JP8 running without needing extra software. The disappointment upon first trying to run it was huge.

[thared33]

I also have a lot of EW products, but only the old Bosendorfer Piano and not the newer Pianos =).

I opened up a case support, but I'm not sure that I'll get a reply about it. I'll keep checking back every now and then to see if an update has been released though. I sure could use the Jupiter 8V in my work right about now...

[thared33]

I've still heard no response from Arturia and the case is still open. If it could open up in Cubase 5 64bit I'd be perfectly happy.

[thared33]

Hmm... I'm really anxious to get this working. I'd like to put some Jupiter 8 stuff in my tracks. Works in standalone but not in in Cubase 5 64bit. 

[uaneme]

I have the same problem with MiniMg V 2.0

Is there anyone who has these plugs running in working order on any 64bit windows?
(XP64 Vista64 or 764) or is it a bug that affects all? 

When can i start working with my brand new miniMg?






 

[platp116]

Any updates here? I just installed Cubase 5 64 bit and can't get J8v in the VST's list.

[Antoine]

Cubase 64-bit nicely runs native 64-bit VST instruments and effects, but is much buggy on 32-bit ones. We have not released 64-bit versions of our instruments yet.
Full 64-bit systems still are a bit fresh, be certain that unwanted behaviors will raise, please consider using them in production with much precaution.

[dickiefunk]

There has been 2 updates of Cubase 5 - 5.5 and now 5.5.1.

Has anyone tried the Arturia synths in the latest version of Cubase?

[Denis]

Just to let you know...

Cubase allows you install two cubases on you computer, one 32bits and one 64bits...

When you plan to use a 32bits synth in one of your projects, then use your 32bits Cubase.

Kind regards,

Denis

[gswan]

Same problem here. Have Cubase 5.5.2-64 under Win7-64 with an Intel Core2 Quad and 8GB RAM. Other 32-bit VST's work OK (Arturia, NI, UAD etc) however Jupiter-8 kills the VST bridge.

One other thing I noticed was when running Jupiter-8 standalone, it would always default to the Windows sound driver, instead of the ASIO device driver (MOTU ASIO driver). Even after I had set it and restarted J8, it did not retain the settings. Anyone else seen this? The other synths (CS80 and MgV) retained their audio device settings when closed and restarted.

Maybe Cubase 6 will have a more stable VST bridge?

[gswan]

Nope
Still just as broken with Cubase 6 64-bit as it was with Cubase 5 64-bit.
Arturia's response was unhelpful.