RAYZOON

In addition to the post above, the problem reappeared failure mode window Always on Top in Cubase 7. When you try to work with the tools window disappears.

Two small installer niggles:

- may be irrational but the 64 Bit VST Path requester appears before the 32 Bit one. All other plugin installers have it the other way around and I get confused each time. Also, the "Select Components" Screen shows them in the "natural order" - 32 Bit first, then 64 Bit, which may add to me expecting to enter the 32 Bit Path first...

- While the Installer remembers the Data/Install Path correctly, the VST paths are empty each time. Again, nothing to kill me, but I like it if the Plugin installer either saves my entries for both paths from the last time I installed the plugin (I use custom VST folder paths) or at least uses the standard VST Paths defined in the registry (which I've set to my custom paths).

Didn't try the plugin yet but wanted to give feedback on the installer while it's fresh

Cheers,

Tom

dimapet_3 wrote:In addition to the post above, the problem reappeared failure mode window Always on Top in Cubase 7. When you try to work with the tools window disappears.

Please email me Documents\Jamstix3\rzdlog.txt

Tom_H wrote:Two small installer niggles:

Current plan is to port the OSX JamstixManager tool over to Windows for V4 (incl. offline install option) so we won't invest too much time for changes in the current installer.

Playing with Beta 27 on Live 9.1.1 Win 8.1 x64

Switching tabs there is a slight delay between each tab contents popping up.

Is it possible to get the dynamics level to be a global setting?
It seems to be saved on a song basis at the moment, but it seems to me dynamics level setting should be global, as well as logically be grouped with the other audio jamming settings.

dimapet_3 wrote:In addition to the post above, the problem reappeared failure mode window Always on Top in Cubase 7. When you try to work with the tools window disappears.

After a day of absence, turned on the computer and found that the problem is gone, I'll let you know if it will appear again.
Many thanks to Ralph for the excellent support! This is the best support among many software products.

Some more testing, but unfortunately getting loads of pop up exceptions.
Was just trying to preview some styles and it went spastic on me.

Tried reopening it and then get a white screen
ERROR: Cannot communicate with core GUI ID=2

JS beta seems very twitchy, and i don't think it's anywhere near release stable to be honest.

I'm considering going back to 3.5

PS: The bug with Wizard double click on song opening the wrong song is still there.

sonicviz, please send me rzdlog.txt from Documents\Jamstix3.
The next time you get an exception, write down and let me know what function (i.e load style) and element (i.e. style name) it occurred on. We haven't had any such issues on any of our test rigs so any detail info will help us in trying to duplicate the problem.

Ralph [RZ] wrote:sonicviz, please send me rzdlog.txt from Documents\Jamstix3.
The next time you get an exception, write down and let me know what function (i.e load style) and element (i.e. style name) it occurred on. We haven't had any such issues on any of our test rigs so any detail info will help us in trying to duplicate the problem.

aok. ty

Now I have another strange problem...

My current project using JS Beta 27 works aok with Audiom8 in Live 9.1.2

I have a new project I just added Jamstix Beta 27 to, and added audiom8 on a guitar track.
Audiom8 shows v1.6 and a VU meter and is detecting audio aok.

However no matter what combination of input monitoring I use I can't get Jamstix to register any audio input from AudioM8

I can't believe I have an existing project that works and a new one that doesn't. Settings look the same for the guitar and Jamstix tracks, with input monitoring on etc.

I even ran through the manual setup list again but no joy.

Anyone have a step by step Ableton Live checklist for setting up Audiom8?
This is driving me batty! (or battery actually, as I'm also sending JS midi output to Battery4)