Jamstix 3 RC1 - Now Available

Post by **Ralph @ Rayzoon** » Wed Dec 23, 2009 5:31 pm

The high-end JS I was talking about is not in the immediate future. We know that many users prefer to use 'best of breed' FX.

Main focus right now is finishing JS3 and then JS-OSX.

TomR · Post by **TomR** » Wed Dec 23, 2009 9:40 pm

then can we please please please(in my best James Brown voice) have x64 JS?

Post by **Ralph @ Rayzoon** » Thu Dec 24, 2009 8:29 am

Our OSX development effort is cross-platform 64-bit ready.

balistick · Post by **balistick** » Thu Dec 24, 2009 4:08 pm

Guitarfish wrote :I would vote for future development effort into more players and styles, and to a 64 bit version.
I second that.

BitFlipper · Post by **BitFlipper** » Fri Dec 25, 2009 2:05 pm

I have not searched through this whole thread but is anyone else having problems using Battery 3 with JS3? The problem is that when I try to load Battery 3, JS3 tells me that it requires at least 16 outputs. So I go to JS3 settings and select 16 outputs, save, close Sonar, and reopen everything. When I try to load Battery 3 again, it again tells me it requires 16 outputs, and when I go to the JS3 settings, it still shows only 8 outputs.

So basically JS3 does not save the user's output channel selection option.

This may very well be something that was already reported/discussed, but I only got around to installing the beta today so I have been out of the loop until now.

BitFlipper · Post by **BitFlipper** » Fri Dec 25, 2009 2:15 pm

BitFlipper wrote:I have not searched through this whole thread but is anyone else having problems using Battery 3 with JS3? The problem is that when I try to load Battery 3, JS3 tells me that it requires at least 16 outputs. So I go to JS3 settings and select 16 outputs, save, close Sonar, and reopen everything. When I try to load Battery 3 again, it again tells me it requires 16 outputs, and when I go to the JS3 settings, it still shows only 8 outputs.

So basically JS3 does not save the user's output channel selection option.

This may very well be something that was already reported/discussed, but I only got around to installing the beta today so I have been out of the loop until now.

OK, never mind, I found the problem. Even though JS3 told me "This change won't take effect until Jamstix has been restarted!", in fact JS3 hasn't actually committed the change itself. To do that, you first need to click on the Save button at the top.

Seems obvious now but at the time I didn't realize I needed to do that extra step, so it indicates that it is a bit unintuitive in this respect. Maybe a better idea is to show a dialog when the user switches away from the Settings page, indicating that changes will only take effect after JS3 is restarted, and does the user want to Save or Cancel? The current workflow might result in users unknowingly losing settings they made in the settings UI.

Or at the least put the Save button at the bottom-right to be more consistent with standard UI workflows where it would be much more likely to be noticed.

arapahoe_1135 · Post by **arapahoe_1135** » Sat Dec 26, 2009 6:41 pm

Using Live 8 on a PC (64 bit) everything is working OK except if you delete the plugin (JS3) and try to add it back in another track. an error message comes up and says that it can't find the plugin anymore? then you have to quit Live 8.1 to be able to open a new instance of JS3... also when you do this live 8.1 reports a serious error and quits immediately.

Also, I can't use JS3 with 256 selected as the buffer size. The smallest I can use is 512. Is this common for everyone else?

arapahoe

sonicviz · Post by **sonicviz** » Sun Dec 27, 2009 2:38 am

Feature Request.

Please make the Live Loop midi note triggering a global setup not on a per song basis.

I have a lot of live loop songs and would like to dump my bidule patch I use to convert Korg Nanocontrol notes to PG's. I would like to dump the bidule patch as it is one less cpu hit, but to replace it I have to modify each song, whereas if there was a global live loop control where you could specify either note or pg trigger for each part and number/type would be more flexible.

ty

Post by **Ralph @ Rayzoon** » Mon Dec 28, 2009 8:36 am

arapahoe_1135 wrote:Using Live 8 on a PC (64 bit) everything is working OK except if you delete the plugin (JS3) and try to add it back in another track. an error message comes up and says that it can't find the plugin anymore? then you have to quit Live 8.1 to be able to open a new instance of JS3... also when you do this live 8.1 reports a serious error and quits immediately.

Please repeat and then send me the file rzdlog.txt from My Documents\Jamstix3.

Also, I can't use JS3 with 256 selected as the buffer size. The smallest I can use is 512. Is this common for everyone else?

What happens at 256?

arapahoe_1135 · Post by **arapahoe_1135** » Mon Dec 28, 2009 10:07 am

Ralph,

gone for the week but will be able to do this next sunday. As far as the buffer thing goes... I just get massive crackles (at 256) and then after a 5 min or so Live 8 just goes poof and the whole application quits. I doesn't freeze, it just disappears.

My PC is a new quad core with 8 gig of ram

One other thing. when I installed JS2.5 on this computer and then added JS3 I was never presented with a way to load the samples to "separate disk"
your install only presents one option to install and did it about three times and if there is a way to select a different disk i can't find it. If there is a way perhaps you could make it more obvious?
hope this helps in some small way.

arapahoe