Rayzoon Technologies LLC

[Sherz]

Oddly... it worked OK for me a couple of times, but now when I open the very same project JS is no longer recognised. Very strange.

Anyway, it's no big deal for me to switch to Cubase 32-bit as I have both installed in anticipation of such eventialities.

[RhythmicallyChallenged]

Wonderful news! As of the 5.5.2 update to Cubase, Jamstix 3 now appears to work in Cubase 5 x64!

Unfortunately I needed to "thrash prefs" in Cubase 5 x64 and start anew ... look this up on the Cubase.net forum if you don't already know about this.

Even having done that, on the first run Cubase 5 x64 froze, but I could kill it in Task Manager and on the second and subsequent runs, it appears to be fine!

I haven't done any major testing but at least it's now loading. As I haven't changed anything about JS3, just updated Cubase to 5.5.2, it proves that the problem was with Steinberg, not with Rayzoon.

[Ralph [RZ]]

Thanks, RC, keep us updated on how things are going for you.
_________________
Ralph Zeuner
Rayzoon Technologies LLC
http://www.rayzoon.com

[Sherz]

Unfortunately this didn't fix thigs for me. JS3 is still not found, and in fact after deleting the Cubase preferences I now have VST bridge errors occuring with other plugins that were previously working fine

[RhythmicallyChallenged]

On further testing, it appears we're not out of the woods yet. If I load JS3 in Cubase 5.5.2 x64 it loads fine, but if I close the GUI and try to re-open it, it doesn't redraw -- there's just a white window.

As a workaround I find if I uncheck "Cache GUI" in Options, it does redraw on re-opening, but then some other strange things happen, e.g. main GUI window disappears when the style or player or other dialogs are open (but reappears when the dialogs are closed). This is different behavious compared to Cubase 5.5.2 32-bit.

Definitely a huge improvement overall but there's still a way to go. In the release notes of Cubase 5.5.2 one of the fixes is "#26383: Improved compatibility for the VST Bridge when using delphi-compiled plugins" ... I wonder would this have anything to do with it? Perhaps you can communicate with Steinberg devs that they are at least on the right track!

@Sherz: sorry to hear about your prefs problem!

[Sherz]

[Steve_E]

[Steve_E]

JamStix appeared in Cubase after I placed the .dll in its own folder [rather than loose in Steinberg's VST folder] after updating to the latest 64 bit Cubase update.

jBridge still won't package JamStix though, however JamStix appears to be working although Cubase won't pick up any midi output from JamStix and JamStix appears to be causing ASIO spikes, posp and crackles.

[Ralph [RZ]]

Steve, are you using JS 3.1 RC1?
_________________
Ralph Zeuner
Rayzoon Technologies LLC
http://www.rayzoon.com

[Steve_E]

[Ralph [RZ]]

3.1 RC1 won't fix the MIDI issue as this is a problem in the Cubase wrapper. However, it should fix the ASIO spikes. If not, please send me rzdlog.txt from My Documents\Jamstix3.
_________________
Ralph Zeuner
Rayzoon Technologies LLC
http://www.rayzoon.com

[Steve_E]

OK, thanks, Ralph - if the ASIO spikes are removed then I should be able to render out files - hopefully! Cheers - will let you know.

[Steve_E]

Brilliant! JS 3.1 RC1 worked a treat! No ASIO spikes and I was able to render out an 11.5 minute track with no issues out of Cubase 5.5.2 64 bit with 9 VSTi's playing. Thanks, Ralph! Cheers!

[Achmed_Lachned]

After many hours of research with jamstix 2 and Cubase Studio 64bit 5.5.2 on Windows 7 64bit, in my case the following procedure led to a running jamstix:
- installed JS 2.0 as administrator in a subfolder vstplugins under my User-Folder: c:\users\blabla\vstplugins
- installed stock pack with JS running under vsthost (http://www.hermannseib.com/english/vsthost.htm)
- installed JS 2.5.3RC1 as administrator in the same folder
- installed my beloved other packs
- installed jbridge demo 1.2 (http://jstuff.wordpress.com/jbridge/) as administrator
- changed jbridge.exe, auxhost.exe, auxhost64.exe : "properties - compatibility - run as administrator"
- run jbridge against above installed jamstix user folder. If it finds only m8audio.dll, convert this, then run jbridge a second time and select the jamstix.dll directly. Maybe deactivate "Thorough file analysis" (I had to do it, else led to a crash).
- select 64bit host
- let output to a new subfolder c:\users\blabla\vstpljb64 (four datasets are created: m8audio.64.dll, m8audio.64.txt, jamstix.64.dll, jamstix.64.txt, the dlls seem to be stubs to jbridge)
- run cubase 5.5.2 as administrator
- add plugin-path of the new stubs: c:\users\blabla\vstpljb64 to VST2-Paths
- open "jamstix 64" in VST-instruments, you will notice a smal frame "jbridge..." with a setup button on the lower border of the jamstix window.
- click this setup button
- activate the following points:
* audioMasterGetTime hack
* sluggish GUI hack
* Force child window clipping
* switch to separate GUI mode (maybe this option replaces the upper ones ?)
* I am getting a dispatchable opcode 19 error message
- close cubse
- after restarting cubase (as admin !) and reselecting jamstix, maybe you see only a new jbridge window - look at the task bar, jamstix now runs in its own window and disappears behind the big cubase
- you can click on this separate window to work with jamstix
- after that, jamstix 2.5.3RC1 runs relativ stable...one of the tests was: audio track with "whole lotta rosie" to m8audio and jamstix with the nu-metal kit - really exciting

After that, I ordered the full version of jbridge which seems to be some versions ahead than the demo. Hope it will not getting worse...