Jamstix & REAPER

Jae.Thomas · Post by **Jae.Thomas** » Wed Jan 09, 2013 2:11 pm

It loads fine in fresh projects - with or without baxter. It juust does not load in this older project.

Post by **Ralph @ Rayzoon** » Wed Jan 09, 2013 2:17 pm

Please make sure REAPER is set to 'automatic bridging'.

Jae.Thomas · Post by **Jae.Thomas** » Wed Jan 09, 2013 2:22 pm

indeed it is, and I want to use jamstix 64 bit only...

Jae.Thomas · Post by **Jae.Thomas** » Wed Jan 09, 2013 2:33 pm

I went through and set EVERY x86 plugin to "default" when it comes to bridging, and now it seems things are loading fine. I am not exactly sure what happened here. I will keep loading and see if it freezes up again.

keys_reaper · Post by **keys_reaper** » Wed Jan 09, 2013 9:16 pm

Jason Brian Merrill wrote:is anyone else having problems loading projects in reaper with jamstix? I seem to have an open GUI window with jamstix and yet it isnt responding...

Hi JBM
Yes I have seen this a few times with the current 4.32pre and rc1. (didn't have JS before then). It seems to happen if JS is not docked on a track but is docked on others.
Closing and opening reaper cleared it iirc.
Actually I think I might have also removed the undocked track and re-added it at some time too on some projects.
Keys

keys_reaper · Post by **keys_reaper** » Fri Feb 01, 2013 7:51 pm

I have a reaper v4.32 project with a few time sig changes. I have a JS part for each ts change. All starts ok but some way through the song position pointer in JS no longer follows reaper.there is no ts change in reaper when it goes wrong. Reaper continues counting up normally but JS jumps back some bars and beats. I do have plenty of odd ts in here - 13-8, 11-8 etc. If I stop reaper at say bar 70 then press play, JS plays at the wrong position e.g bar 65.

Is there any way to see if it's a reaper issue or a JS issue?
I can't seem to find a vst that displays song position. Anyone know of one?

I get the same bug with reaper v4.33pre3 too.

Can anyone help please? Thanks.
JS v3.5.1b2
Keys.

edit:
It seems that the problem is JS. When I add a 'silent' part in order to either have no drums or my own hand edited bars, then JS loses the song pointer either during or after this part. If i tell js to compose with say freestyle for that part, the song pointer stays in sync.

This does look like a bug in JS for silent parts....

Post by **Ralph @ Rayzoon** » Wed Feb 06, 2013 2:11 pm

Can you send me the REAPER project?

keys_reaper · Post by **keys_reaper** » Wed Feb 06, 2013 6:39 pm

Ralph [RZ] wrote:Can you send me the REAPER project?

Hi Ralph, I had a test project all lined up - then I found the work around - and now I cant reproduce the problem!

edit... I think its me.... The JS song pointer goes wrong once the last part has been played. I've been watching the JS transport instead of the REAPER transport and as REAPER continues to play normally, JS skips bars/beats when the last JS part has finished.

When testing this, I must have added a bar or so in the song at the time when i changed the style from SILENT to something else. I was thinking the change of part type had made the JS transport come back to the right position!

To be clear, the JS song position stops following the DAW song position once all the JS parts have finished playing.

Sorry for the confusion. Keys.

Post by **Ralph @ Rayzoon** » Thu Feb 07, 2013 9:17 am

Is 'Enable Song Looping' checked in your JS3 Options?

keys_reaper · Post by **keys_reaper** » Fri Feb 08, 2013 5:07 pm

Ralph [RZ] wrote:Is 'Enable Song Looping' checked in your JS3 Options?

No, when I enable it, very wierd song positions happen in JS.
Then reverting to disabled doesnt clear it back - seems to be worse still.
I'll email you a sample reaper project and the JS log.

Thanks.
Paul.