Jamstix 3.1.0 RC1 Available

Susan G · Post by **Susan G** » Sat Oct 16, 2010 2:51 pm

Ralph [RZ] wrote:We are unable to produce any crashing with 3.1 B3 with various OS's and hosts. Please tell us specific steps to produce crashing. Also, if you do not have any crashes, let us know as well. Need your help to track this down.

So far all my crashes have happened when I'm previewing a bar. Just now I was previewing a fill bar with Jamcussion. When I hit the Compose button the display of hits wasn't being refreshed, so I tried to stop the loop playing and got a white screen AppHang again with REAPER.

It doesn't happen every single time, which is why it's hard to give an exact recipe.

Win7 x86, REAPER 3.72rc2

-Susan

P.S. Shouldn't the hit display in the bar editor update automatically when I hit "Compose"? It doesn't with the drumset either. I have to stop the loop and then click underneath it to see the new hits displayed. They play as newly-composed, but what I see and what I hear are different.

Edit: Tried again, and this time I recomposed a fill bar and locked it. When I hit the space bar, white window again and poof! REAPER disappeared.

I'll try in SONAR and FLS in a bit.

Susan G · Post by **Susan G** » Sat Oct 16, 2010 3:54 pm

max.noise wrote:Hi Ralph,
tried the new Beta and found that it crashes Cubase 5.5 and Live 8.2.1 at the end of a song. It's fine as long as Jamstix has something to play (I did not try the new features or did any other tricky things, I simply started the host and let it run), but when the last bar is played the host crashes on the next 1. Transport stops and the last sound is repeated over and over and the hosts don't react anymore and have to be closed via task manager.
OS is Windows7 64bit.

Greetings from Germany

Max

Similar here with SONAR 8.5.3. Played through to end, then I clicked a UI tab in SONAR and got a white screen/AppHang:

Problem signature:
Problem Event Name: AppHangB1
Application Name: SONARPDR.exe
Application Version: 17.5.3.282
Application Timestamp: 4b7b3272
Hang Signature: 120b
Hang Type: 1
OS Version: 6.1.7600.2.0.0.768.3
Locale ID: 1033
Additional Hang Signature 1: 120b5a872bd0df59660511f953c773ae
Additional Hang Signature 2: 7463
Additional Hang Signature 3: 74634b048f6d7c355eabb42f0646d33f
Additional Hang Signature 4: 226b
Additional Hang Signature 5: 226bd3b6ba93c1eeb4838562c379a918
Additional Hang Signature 6: 0a21
Additional Hang Signature 7: 0a21931ac2cc8e8a78f8d1af92d2c47e

I think I'll stop testing for now.

-Susan
Win7 x86

auto_da_fe · Post by **auto_da_fe** » Sun Oct 17, 2010 11:38 am

I too am getting the white screen crashes in sonar with Beta three.

It seems to be related to whether the JS3 GUI is active or not.

I have an empty Sonar project with only JS3 B3 loaded in. I open the JS3 GUI and load 12-bar blues.J2D. As long as the JS3 GUI window is not open I can play and restart the song all day long. If the JS3 GUI is open, as soon as you try to restart the song it crashes. The audio portion of the song continues playing however the screen goes white and you have to restart the computer.

This is very repeatable. So far 3 for 3.

Of course there is no S. JS3 crash log related to this event.

Win 7, Sonar 8.5.3, JS3 beta 3

dke_music · Post by **dke_music** » Sun Oct 17, 2010 2:29 pm

Same here, if the JS3 beta 3 UI is open Sonar crashes at the end of the song, once JS has run out of notes to play.

I just tried it in Beta 1 and it doesn't crash when it run out of notes to play at the end of a song.

Win7 32bit, Sonar 8.5.3.

Dan

Post by **Ralph @ Rayzoon** » Mon Oct 18, 2010 11:59 am

Everyone, please see what issues remain with beta 4, which I just uploaded.

Susan G · Post by **Susan G** » Mon Oct 18, 2010 3:42 pm

Hi Ralph-

I'm still seeing hits crossed out for no apparent reason. I'm using REAPER right now, will check in FLS in a bit (did you get my .flp file?).

When I say "no apparent reason": for example, I have a bar with a Kick on the upbeat to 3 and the downbeat of 4. The status says the reason they can't be played is "TRANSITION FROM KICK". The RF is only playing the Kick, so why isn't it possible to play 2 kicks in one bar?

In another bar, I have a snare side hit on beats 1 and 2, and the hit on 2 is X-ed out: "TRANSITION TIME FROM SNARE SIDE". How can this be?

If I compose the bar in loop preview the Xes often disappear, then on the next play they'll reappear, or other hits will be x-ed out. Much of the time the x-ed out hits play normally anyway.

I've only been working with beta 4 for a few minutes and it hasn't crashed yet, but the problem with all these hits being x-ed out makes it nearly impossible to work with IMO.

-Susan

Post by **Ralph @ Rayzoon** » Mon Oct 18, 2010 3:53 pm

I did see the FL red cross problem once. I then did something and it disappeared. Am working on getting to the bottom of this. I do not see this problem in any other host. Please also see if this problem disappears when FL is recording.

The no crosses in preview is normal behavior for JS.

Susan G · Post by **Susan G** » Mon Oct 18, 2010 3:58 pm

Ok, but as I said this is with beta 4 in REAPER , I haven't tried it in FLS yet.

Thanks-

-Susan

dke_music · Post by **dke_music** » Mon Oct 18, 2010 4:33 pm

The crashing at the end with GUI open seems to be fixed. I haven't yet run into any other problems, though I'm working on a pretty much finished piece with just minor edits here and there.

Dan

auto_da_fe · Post by **auto_da_fe** » Mon Oct 18, 2010 8:31 pm

Same here Ralph no more crashing end of song.

Will not be able to work with it a lot till this weekend, if I notice anything I will PM you

thanks

Jeff