Jamstix 3.6.0 Final Release Candidate Available

jazzmandan · Post by **jazzmandan** » Wed Feb 05, 2014 7:52 am

Need more input from you Reaper guys....

craig_glenn · Post by **craig_glenn** » Wed Feb 05, 2014 8:59 am

On Reaper here...

Was previously working on an old project using 3.5.1 beta 12 and installed 3.6 beat 12 over this and Jamstix worked flawlessly... Earlier today i tried to start a new project, inserted VSTi > Jamstix and i got the same white screen where it says to contact Jamstix support...i then closed it and went back to my old project and to my dismay i got the same screen...i went and reinstalled 3.6 beta 12, and it started working again...weird!

Hope you got all that or if its helpful?

I am going to try beta 13 later and see what what happens

bakiki_ · Post by **bakiki_** » Wed Feb 05, 2014 9:20 am

Ralph [RZ] wrote:
bakiki_ wrote: Still having the same problem it worked once after reinstall but back to the same problem of the import feature freezing with no response....?
After what action exactly does it freeze?

It freezes/non responsive on the first click...?

I've installed beta 13 but GUI disappears when I click on it?

I'm starting to wonder if perhaps I have a the incorrect js3sl64.rtxc file. I have a collection of betas and rtxc files which which may have confused my setup. Could I also have a cluttered registry from residue of old installments. I have done a complete uninstalled but would this wipe old Jamstix 3 unused registry files..?

Sorry for all the questions..

Azimuth (Archive) · Post by **Azimuth (Archive)** » Wed Feb 05, 2014 10:00 am

@craig_glenn, if you get the "contact Rayzoon" screen after installing the new beta, make Reaper re-scan your vst folder and it should correct that. It worked for me.

genmce_1 · Post by **genmce_1** » Wed Feb 05, 2014 10:07 am

a_zimuth wrote:@craig_glenn, if you get the "contact Rayzoon" screen after installing the new beta, make Reaper re-scan your vst folder and it should correct that. It worked for me.

I had that white screen back on beta 10.
I never rescaned the vst folder...
Hmmm... maybe I can try again,
a_zimuth - are you using xp?
Also - do you hang out over at guitarnutz2?

I have not tried another beta yet with xp.
Maybe I need to try again later today.

minerman_1 · Post by **minerman_1** » Wed Feb 05, 2014 10:47 am

Using Reaper 4.56 &JS Beta 13

The gui/plug-in loads, project plays, & the loop/preview button works, but only if I click again either at the top of the plug-in, or Reaper itself, Jamstix won't make any sounds until I click somewhere to re-gain focus with my mouse (every time too, for example, if I highlight a hit in the editor, I have to click somewhere in the "border" of the plug to have any sound...any parameter adjustment is like this too)...other than that, no issues so far, my older projects load up & play (unlike the last couple betas)....It works (compared to beta 12, I got the white screen described by a few members here), but would be too many mouse clicks to get anything done to be honest...

Post by **Ralph @ Rayzoon** » Wed Feb 05, 2014 11:41 am

bakiki: RTXC files are no longer used in 3.6.0. Please send me apslog.txt and rzdlog.txt for review

minerman: please UN-check "Closed audio device when stopped..." in the REAPER-AUDIO settings.

Fuzz_face · Post by **Fuzz_face** » Wed Feb 05, 2014 11:49 am

Ralph, Beta 13 works great with cubase 7.5. Best version so far.
Excellent work!

jas_lan · Post by **jas_lan** » Wed Feb 05, 2014 11:55 am

Also works great in Cubase 6.5.5. Beta 13, that is...

operandx (Archive) · Post by **operandx (Archive)** » Wed Feb 05, 2014 12:19 pm

Having real issues with this latest beta (13) on Win Vista32 using Tracktion 5. Keep getting that white contact support screen. When the host is closed the Plugin server still shows that a plugin is in use. If I subsequently reopen the edit the number goes to 2 and on edit closure stays at 2. Also trying to close server with button causes a dialog to be displayed with no text and a button with no text. Have to close it using task manager. Then get a dialog with 'FastMM has detected a GetMem call after FastMM was uninstalled' error message.