JS3.5 64-bit vst with Sonar X2 -- a couple of issues

Mark Blair · Post by **Mark Blair** » Wed Nov 21, 2012 5:57 pm

1) Seems to ignore the .ini file location for the data folder. Also, can no longer just move data folder and expect Jamstix to prompt for new location -- it crashes Sonar X2 when I try that!

2) On the Song screen, the whole top section seems to be offset to the bottom right about an inch or so -- and therefore starts to overlap controls on the lower portion of that screen.

3) Also, the circular button to activate playing through a measure won't turn off when I try to click it again, so the measure keeps playing until I delete the instance of Jamstix.

So -- I guess I'll just wait for the next update in hopes that it will address this stuff, and I guess I'll try to re-install JS3.3 32-bit for now...

TomR · Post by **TomR** » Thu Nov 22, 2012 10:52 am

I had some trouble getting the install to update the existing js3.3.

I ended up removing JS35 update and js3. Then I installed only js35 accepting the default location for the install files. Copied the Keyfile and installed all the kits. Everything seems to be working ok in x2 after a vst scan.

I have noticed that if JS35 gui is open on the second monitor some of the JS dialogues open in the wrong place. I moved the JS gui to my main monitor and the graphics are behaving better.

I have been working this evening using the bar repeat button you are referring to and have not had any problems.

Perhaps if you remove everything JS 3, 3.5 and reinstall as I did things may work better for you.

Good luck.

Mark Blair · Post by **Mark Blair** » Thu Nov 22, 2012 11:43 am

Thanks for the suggestions, Tom. But I already wiped out everything (except for my data folder which is located on a separate drive that I use for samples only). And then, after I re-installed just JS 3.5 64-bit from scratch, I temporarily copied my data folder to the default location, so at least the sounds now work. But the other issues still remain. Again, I'm using 64-bit Sonar X2, so perhaps this is a host-specific issue (unless that's what you're using, too).

TomR · Post by **TomR** » Thu Nov 22, 2012 7:45 pm

Do you have the Cache Gui option enabled? If so try turning it off. Have you changed the default windows font dpi settings? perhaps that is a place to check.

As for the ini file I wonder if Ralph is not using it for some of the variables. Send him an email at support@rayzoon.com see if he has a suggestion.

Mark Blair · Post by **Mark Blair** » Thu Nov 22, 2012 9:59 pm

Already reverted back to 3.3 -- and I'll just wait for Ralph to check into it in his own good time. I'm sure he's got a lot to deal with right now.

Post by **Ralph @ Rayzoon** » Fri Nov 23, 2012 10:44 am

Hi Mark,
Concerning the INI file, things are a bit different from V3.3 as I outlined in this thread:
http://rayzoon2.com/forum/viewtopic.php?t=6375

Your JS skin problems are caused by old skin files from V3.3 being present in DATA\SKIN. This will lead to offset panels and also the PREVIEW button not working right. I'd recommend this:

- keep a good backup copy of your old DATA folder on the sample-only drive.
- install 3.5 and choose a NEW folder name for the first location the installer asks for, on the sample-only drive! The second location asked for is your plugin DLL folder (host search path) as usual.
- copy ONLY the contents of the data\sounds, data\players,\data\styles folders from your old DATA folder to the DATA folder inside the new JS3.5 location on the sample-only drive.

Mark Blair · Post by **Mark Blair** » Fri Nov 23, 2012 12:08 pm

Thanks, Ralph! I won't get a chance to try your suggestions until Monday (26 Nov) -- but I'll be sure to reply back here with the results in case other folks are monitoring this thread. Thanks again!

- Mark

Mark Blair · Post by **Mark Blair** » Mon Nov 26, 2012 8:49 pm

Thanks again, Ralph. It MOSTLY worked!! Again, I'm using Sonar X2 64-bit, and now the test project file that had the problems expressed above generates a show-stopping error whenever I try to re-install the newly-installed JS 3.5 64-bit vst plugin. However, when I insert it into a new Sonar project file, it seems to work mostly okay (just a few relatively minor peculiarities that I won't worry about at this time). ANYWAY, does anybody have any idea why the newly-installed JS 3.5 64-bit would work in a new project file -- yet not work in an old project file where the improperly installed JS 3.5 was previously at least able to start up without any error? And yes, I've re-booted the system (several times)...

Post by **Ralph @ Rayzoon** » Tue Nov 27, 2012 5:52 am

What error are you getting? Any messages on the screen?

TomR · Post by **TomR** » Tue Nov 27, 2012 9:17 am

Mark. You probably already did this but just in case you did not, be sure to run the sonar vst scanner again.

If you already did here is a trick that I have used to correct other vsts that misbehave:

Move the vst dll out of the sonar scan path.
run the vst scanner,
close sonar,
copy the vst back into the scan path.
start sonar and run the vst scan.
close sonar again and load sonar again and try your project.

good luck.