Jamstix 3.1.0 RC1 Available

Perun_ZG · Post by **Perun_ZG** » Sat Jan 01, 2011 4:59 am

BitFlipper wrote:I am not sure whether these issues are from Sonar X1a or from JS3.

Look over at the Cakewalk forums. There are still many issues with X1 itself.

Max_RB · Post by **Max_RB** » Sun Jan 02, 2011 12:11 pm

Hello,
started Cubase 5(64 bit Win 7) with Jamstix beta 14(default setting), same problem as before. After load Jamstix GUI opens just fine, after closing the interface (not the program), on reopening the GUI Jamstix freezes showing a white GUI. Now for the first time I unchecked "cache GUI", and that makes all the difference at least for me and my computer.

cheers Rolf

dke_music · Post by **dke_music** » Sun Jan 02, 2011 9:37 pm

So far beta 14 and Sonar X1a are working well. I was getting hang's on starting X1 and occasional crashes while working with JS3 beta 9, didn't get a chance to test beta 12.

Dan

Milt · Post by **Milt** » Mon Jan 03, 2011 9:09 am

Beta 14 didn't help here.

Post by **Ralph @ Rayzoon** » Mon Jan 03, 2011 9:16 am

Milt, does it work fine with "Cache GUI" unchecked?

Milt · Post by **Milt** » Mon Jan 03, 2011 9:19 am

Ralph [RZ] wrote:Milt, does it work fine with "Cache GUI" unchecked?

I don't know about that Ralph, I haven't tried it. I will be back in the studio in a couple of hours and will give it a go and let you know what happens. Thanks!!

Milt · Post by **Milt** » Mon Jan 03, 2011 3:30 pm

Ralph, unchecking 'cache gui' seemed to help quite a bit, but I still got a couple of error messages randomly loading different songs 10 or 15 times. One said: "Access violation at address 7710E663 in module "ntdll.dll". Read of address FFFF300c". The other message said: "The instruction at 0x7710f5a6 referenced memory at0xb601cbc3. The memory could not be read. Click ok to terminate the program." I also got the Reaper host 32 shut down message after I had closed Reaper, and it named Jamstix as the fault module. Thanks for your work. EDIT: Forgot to mention that unchecking cache gui made matters worse in Sonar 8.53 x86 and x64.

Andre Giroux · Post by **Andre Giroux** » Sat Jan 08, 2011 12:58 pm

Hi Ralph,
Couple of things going on here with MTS and JS.

1. Setting up a new song. I bring a click track and set time signature (2/4) and tempo 114 then bring in a midi track for JS, set up song in wizard: structure, style, drummer and kit press create song. Now at this point the kit won't load and i have to load the kit manually under kit menu.

2.In the song parts time signature don't sink with host which stays set default 4/4. Each parts need to be changed manually to 2/4

this has come up in beta 14. was working fine before
Thanks
AndrÃ©

Post by **Ralph @ Rayzoon** » Sat Jan 08, 2011 7:15 pm

After changing the time signature in the host, please play the host for just a second and then hit 'Reset Song' in JS. This allows MTS to send the updated info to JS and let's JS adjust the time structures.

Sherz · Post by **Sherz** » Thu Jan 13, 2011 4:23 pm

Well, while recent betas have certainly improved the situation with Cubase 5.5 64-bit, i.e. I can now actually load and use JS3, and with cache GUI disable it seems to behave itself reasonably well (though pops & crackles seems to be an issue).

BUT... somewhere along the line something broke so that I can now no longer use JS3 with Cubase 32-bit. It used to be the other way round!
I now get the same error that I used to get with Cubase 64 - i.e. it can't find the VSTi.

I have yet to evaluate the current beta in my 64bit environment to see if that has fixed the pops/crackles issue.