Jamstix 3.6 OSX - Final RC Available

muzic_maken · Post by **muzic_maken** » Wed Apr 23, 2014 9:52 am

I finally have sound on the kit...(I haven't tried routing my EZ and SPDrummer yet)...But can not get JAmstix to learn my song or start playing along with it or even preview the drummers or Kit....I do keep getting CPU overload all the time.. This is with only 2 tracks on the session..Acoustic Guitar and vocal...I never have any problems with CPU overload since upgrading to PT11. But it's not crashing my system as often.

Mac Mini Quad Core
16gig Ram
Focusrite LS56
UAD 2 Satellite
OSX Mavericks

Post by **Ralph @ Rayzoon** » Wed Apr 23, 2014 9:59 am

Please email me your latest rzdlog.txt so I can see what the system config is at this time.

muzic_maken · Post by **muzic_maken** » Fri Apr 25, 2014 8:15 pm

Still No Luck here...

Post by **Ralph @ Rayzoon** » Sat Apr 26, 2014 6:33 am

We will have a new Beta soon.

Post by **Ralph @ Rayzoon** » Sat Apr 26, 2014 8:23 am

OSX Beta 28 is now out. Simply run JamstixManager to install it. We are especially interested in these issues:

a) Audio crackling/overloads
b) White screen errors on load (i.e. Core Access Error)

If you still have any of these with Beta 28, please email me /Documents/Jamstix3/rzdlog.txt and a brief description of the error/behavior.

Tom_H · Post by **Tom_H** » Sun Apr 27, 2014 9:48 am

- Love the Jamstix Manager

Slick stuff.
- No white screens so far.
- Still the GUI lags a lot behind the VST Window Frame on the old laptop.
- AudioM8 input doesn't make the Audio LED in Jamstix flash, although Audio Jam works as expected and the dynamics knob moves.

Just a short test though, Bitwig Studio 1.0.8.RC2

Cheers,

Tom

P.S. By accident I once more closed Jamstix from the OSX menu when I intended to close Bitwig. This results in a total hang with a white Jamstix Window and an empty Bitwig Window. Force-Quitting Bitwig leaves the Jamstix Window Frame behind and there seems to be no way to kill it with the normal tools. No OSX-Console-Wizard here.

Is there any reason for Jamstix to show in the OS Menu when run as a VST?
I guess I understand how you split between VST Window and Jamstix Server (no clue why though) but somehow I find it irritating and prone to user errors.
And no love for the jamstix server window on OSX either

muzic_maken · Post by **muzic_maken** » Sun Apr 27, 2014 12:20 pm

Here's a video of the problems I'm having..
I am getting CPU overload as soon as 3 audio tracks start
This shouldn't be the case since I'm using UAD 2 Satellite
for all my effects processing.

Also this video didn't capture it but sometimes when I hit play
there is nothing but distortion, when I close the session and bring it
back up the audio is fine.

Here's a link to the vdeo of a few problems I'm having

[url]http://youtu.be/W1ciQaRvFY0[/url]

this is all with the latest beta

Ken

muzic_maken · Post by **muzic_maken** » Sun Apr 27, 2014 12:25 pm

Tom_H wrote:-
Tom

P.S. By accident I once more closed Jamstix from the OSX menu when I intended to close Bitwig. This results in a total hang with a white Jamstix Window and an empty Bitwig Window. Force-Quitting Bitwig leaves the Jamstix Window Frame behind and there seems to be no way to kill it with the normal tools. No OSX-Console-Wizard here.

Is there any reason for Jamstix to show in the OS Menu when run as a VST?
I guess I understand how you split between VST Window and Jamstix Server (no clue why though) but somehow I find it irritating and prone to user errors.
And no love for the jamstix server window on OSX either

Tom I too have this problem in PT it's not as frequent but still happens.

It's not recognizing the tempo of my songs (that could be user error that I haven't figured out) I assumed it would follow the tempo command in the DAW.

Ken

Post by **Ralph @ Rayzoon** » Sun Apr 27, 2014 12:39 pm

Tom_H wrote:Is there any reason for Jamstix to show in the OS Menu when run as a VST?
I guess I understand how you split between VST Window and Jamstix Server (no clue why though) but somehow I find it irritating and prone to user errors.

Next Beta will remove the system menu for the server window and also hide it from the dock.

Post by **Ralph @ Rayzoon** » Sun Apr 27, 2014 12:55 pm

muzic_maken wrote:Tom I too have this problem in PT it's not as frequent but still happens.
It's not recognizing the tempo of my songs (that could be user error that I haven't figured out) I assumed it would follow the tempo command in the DAW.
Ken

I've checked out the video. Please send me a rzdlog.txt with Beta 28 and PT11 so I can research the BPM and overload issue further.

Also, please note that Jamstix has no way of knowing where your song starts and what groove would be adequate for it. You need to select the desired style/drummer in Jamstix and set the song structure in JS to match your actual structure (intro, verse etc.).