RAYZOON

I just sent you an email with the needed file.

Hi Ralph, I have uninstalled 3.5 for now, I will have another go at it tomorrow. The issue is that I have all my plugins on an SSD drive and all my data on another HD. The Jamstix data is in a folder called JamstixData. Whatever I put in the installer box I can never get it to use my JamstixData folder. If I put that folder in it puts the data in a subdirectory called data. Wehn I get it wrong I either get the problem shown in the screenshot or no sounds found at all.

In the past with updates I have deleted the data directory the update installed and then ran it where by it would complain about no data directory and so I would point it at the right one. With this update when I try that it crashes Cubase with "a serious error has occurred...."

Thanks for the update.

In Reaper 64 on win7 64 bit machine Jamstix is loading as 32 not 64 in an existing project.

I had Reaper rescan plugins, no change.

Jamstix shows 3.5.0 (x32) in the Jamstix window bottom.

How do I make Jamstix load in the project as 64 bit?

Thx

Now having another issue, same hardware as above.

When "inserting new part before this part" JS freezes and I cannot close it. Must restart PC. Am able to shut down Reaper but JS Gui stays open and is unresponsive.

May have fixed it all by deleting and reinstalling.

Thanks much for the 3.5 final update, but it's a little confusing on the version naming.

In Ableton Live:

JamStix 3.0 showed up as JamStix3
JamStix 3.5 Beta shows up as JamStix35 ("About" screen says 3.5.0)
JamStix 3.5 Final shows up as JamStix3 ("About" screen says 3.5.0)

So for folks that have kept the Beta version around for your old songs that used it, if it says JamStix35 it's the old version and if it says JamStix3 it's the new version (or the very old version, if you still have that installed somewhere).

Otherwise we're cookin' with gas.

Thanks for great job, Ralph.

1. I use double monitor configuration and prefere to move Jamstix window to the secondary one. If I click any menu icon then menu itself still appears on the primary monitor (stuck to its border). It was OK with the 3.3.0 release.

2. "- sub-hosting removed, use MIDI routing with new key map support instead"
What is "new key map support"? How can I learn more about it?

Hey there...

Use 2 monitors too...so far so good, no problems here

Ralph,

I'm getting 100% cpu spikes again, but only when the UI is open (even in midi only mode). I had reported this problem before, but it went away with b10 as I recall. I removed JS entirely from my system and reloaded clean from the release installer and kit files, but it's still happening. Could this be fixed with the 'cacheable ui' option?

Thanks again,
G

@felken: let me known if you have any further trouble

@ancient: the Beta was named jamstix35.dll so folks could test it alongside the 3.3 version.

@alved: we're using a completely different toolkit for the GUI in 3.5 so we'll have to see what we can do about dual monitor support. As far as key mapping goes, the kit menu has now options to load/save key maps. A key map has the MIDI keys for the given 3rd party plugin and also information on hihat controller etc. V3.5 comes with several pre-made key map files. What plugin are you going to use with JS?

@Photo_G: please send me rzdlog.txt from Documents\Jamstix3.