Rayzoon Technologies LLC

[Mark Blair]

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]

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.
_________________
Tom

[Mark Blair]

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]

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.
_________________
Tom

[Mark Blair]

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.

[Ralph [RZ]]

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.
_________________
Ralph Zeuner
Rayzoon Technologies LLC
http://www.rayzoon.com

[Mark Blair]

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]

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)...

[Ralph [RZ]]

What error are you getting? Any messages on the screen?
_________________
Ralph Zeuner
Rayzoon Technologies LLC
http://www.rayzoon.com

[TomR]

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.
_________________
Tom

[Keebo]

Thanks for the update, Ralph. Nice job. This is such a great tool.

I ended up uninstalling all of the previous installations and only installing the 64 bit version and I am all set with Sonar X1.

As mentioned earlier, changing the windows font dpi settings to get the interface to my likings creates some issues with graphics not lining up properly. I am able to work with this but I wish it was possible for Jamstix to adapt to different dpi settings.

Good luck with future updates. I am so looking forward to an iOS version and Jambassist.

Rock on.

[Mark Blair]

Hey Ralph -

Sorry -- it was late for me and I forget to list the error. And TomR, I thought I was the only person who thought of trying potential fixes like what you suggested (I tried it previously, no difference).

Anyway, the error screen that pops up says:

Runtime error 216 at 00000001325E045 (this number changes a bit each time). Then the Sonar Fault Reporter screen pops up, which then leads to a SONARPDR.EXE has stopped working screen, then it sometimes volunteers to try to save my Sonar sessions, and the screen mentions that there was an Unhandled Exception in the jamstix3.dll, and then, after a crash dump file is created, it says Exception Code c0000005, and then it says SONARPDR.EXE has stopped working. I hope this helps!

Oh -- and, like others, whenever the JS interface is open, I get random distortion, but it seems to be fine when the JS interface is closed.

-- Mark

[TomR]

Ok Mark. Have you tried a chkdsk and defrag? that may help.

Here is another trick since you can load JS in a new project, enable sonar to have more than one project open.

Open the new one first to get JS image into memory and then open one of your existing projects that is having trouble.

If the project loads Use the JS save song to export the song and kit settings. Then remove JS from the existing project.

Then close all projects and sonar.

restart sonar and load your existing project, add JS to the project.

If that works then load the saved song and save your project.

Close and reopen to verify that it is still working.

I hope this gets you going.
_________________
Tom

[Ralph [RZ]]

Mark: please send me rzdlog.txt from Documents\Jamstix3. Also, try running SONAR as ADMIN, if you aren't already.
_________________
Ralph Zeuner
Rayzoon Technologies LLC
http://www.rayzoon.com

[Mark Blair]

Ralph - I sent the file! But, per my response below to TomR, don't lose too much sleep over this! The audio glitches with the JS interface open are actually a more pressing issue from my perspective -- bit that's not a major show-stopper either. But it is very annoying!

TomR - JS 3.5 works in another project file, so at this time I don't want to try any other work arounds -- but thanks! I just want to give Ralph an opportunity to see what's causing the Unhandled Exception error, so I'm going to leave the "bad" project file as it is for now. It was just my initial JS 3.5 test project file, so no real problem for me at this stage.