RAYZOON

Hi Ralph

JS 3.5.1 Beta2 (64)

If I select a folder in the left pane, to import JS1 rhythms,
I imagine it should show the folder in orange in the top RH corner of that window(which it did when I first tried it)
Now when I try to import JS1 rhythms, selecting the correct folder does not work.
The orange text does not change to the correct folder.

[color=red:40d60972f0]MY MISTAKE , I HAD Groove import selected in JS3.5 instead of Rhythm [/color:40d60972f0]
regards

John Heath[color=red:40d60972f0][/color:40d60972f0]

Hi Ralph. I am having trouble with the song wizard. If I select a JS1 kit it does not load and I get an empty kit window after pressing create song. If I do it a few times I can end up with the words Kit and JC Kit crossed out in the song wizard.

Confirmed, we'll get that fixed.

I have lot of troubles loading kits. Maybe those addressed are in the update?

Kits are not loading, no error message. Just a black kit-window or if there's a kit already loaded, nothing happens.

Sometimes I get this: " Cannot assign a TGUIForm to TImage".

The worst problem is that I can't load certain sounds at all (for example right clicking kit pieces), such as "brush".

I use Presonus Studio One 2 Pro on windows 7.

Jamstix keeps crashing Live. Seems to be GUI related, as it always crashes either trying to open JS plugin or attempting to open a menu in it.
Sometimes it works, but then *BAM*

Showstopper. No problem with any other plugins.

Edit: This appears to be a possible conflict between my multi-monitor utility and Jamstix not wanting to play nice. Switched to Ultramon for now.

Bojo: please run your host via right-click->Run As Admin and see if it fixes it. If not, please send me rzdlog.txt from Documents\Jamstix3.

Question: I'm currrently working on a piece in Ableton Live 8.3.4 32 Bit, Windows 8 64 Bit. I use a Jamstix 3.5 track with Euclid and Midi-Out only to drive some metallic hits in a sampler.
Now when I open the file, I get no output from Jamstix on playback. Only if I open the GUI it works. If I then close the GUI again, it continues to work for a while but then stops again. It works only reliably if I leave the GUI open, even if switching to another track hides the GUI in Live (I guess only virtually).

This has been the case with the 3.5 release as well as it is now with the beta 2.

Any ideas what to look for? Is that a known problem?

Cheers,

Tom

We'll look into that for Beta 3.

any news on the release?

We're working on it, definitely this week.