Jamstix 4.4.3 Beta 3 (macOS) is now available

[jdockerty_1]

Cool, thanks for the reply.

[apesma_1]

Hello All,

Testing the new Beta 30 release using the latest version of reaper.

1) I can confirm that I'm getting the kit freeze issue that others are reporting.

2) I’m noticing a strange thing that Jamstix does when it encounters a time signature change from reaper.
I have a song with a time signature of 18/8. During a pre-chorus part (bar 23), Reaper issues a 9/8 time sig change for 1 bar. After that bar (24), another time sig is issued that sets it back to 18/8. While bar 23 is being played, Jamstix seems to repoint or offset it’s bar pointer to bar 45, which is way after the song ends, so no drums get played here even though I have a groove that exists at bar 23.

At the end of bar 23 and the start of bar 24, Jamstix redirects the song pointer back to bar 23.10.1 or thereabouts. At this point the song is completely out of sync.

Should I be handling this differently?

Thanks for any and all help.

[img:4951f2cd59]https://dl.dropboxusercontent.com/s/tuj ... dw1/02.png[/img:4951f2cd59]

[img:4951f2cd59]https://dl.dropboxusercontent.com/s/ni9 ... hzk/01.png[/img:4951f2cd59]

[Azimuth (Archive)]

Use the Manager app to send the log files to Ralph. I was able to replicate this issue in 4.2.3 beta 3 also.

[apesma_1]

Done! Thank you.

[apesma_1]

a_zimuth,

I was also able to replicate this problem with Cubase LE Elements 9.5 as well.

I am curious as to what DAW you were using?

[Ralph @ Rayzoon]

Please set the time sig for the 'Pre-Chorus' part to 9/8.

Also, you do have 'Allow Time Sig Changes' checked in the JS4 Options, right?

[apesma_1]

Please set the time sig for the 'Pre-Chorus' part to 9/8.

Also, you do have 'Allow Time Sig Changes' checked in the JS4 Options, right?

Hi Ralph,

The Pre-Chorus part was already set to 9/8 in Reaper.

I toggled 'Allow Time Sig Changes' a few times yesterday when I was testing and it didn't make a difference. Turned it back on now and the "Time" field was already at 9/8. Ran it again and the bug is still happening.

[Azimuth (Archive)]

a_zimuth,

I was also able to replicate this problem with Cubase LE Elements 9.5 as well.

I am curious as to what DAW you were using?

I'm using Reaper, latest pre version.

[b:f25f056303]EDIT: I sent the Reaper project and logs to your email Ralph[/b:f25f056303]

[color=red:f25f056303][b:f25f056303]EDIT 2: This was my mistake. The time sig markers in my DAW were in the wrong locations.[/b:f25f056303][/color:f25f056303]

[apesma_1]

My mistake as well. Ralph helped me to get this sorted. Then I got humbled reading the the support FAQ and then later finding the same support tip in the PDF. Apologies to everyone.

a_zimuth,

I was also able to replicate this problem with Cubase LE Elements 9.5 as well.

I am curious as to what DAW you were using?

I'm using Reaper, latest pre version.

[b:44b70248dd]EDIT: I sent the Reaper project and logs to your email Ralph[/b:44b70248dd]

[color=red:44b70248dd][b:44b70248dd]EDIT 2: This was my mistake. The time sig markers in my DAW were in the wrong locations.[/b:44b70248dd][/color:44b70248dd]

[Azimuth (Archive)]

Apologies to everyone.

No apologies needed. This is exactly why this forum exists, to help each other out when problems occur.