Page 1 of 1

Looping a bar doesn\'t work when "AlwaysSync"=1

Posted: Sun Apr 15, 2012 1:38 pm
by drybij_2
and "Lock host" is enabled. It simply refuses to loop even though the loop indicator lights up.

If I enable lock host, the selected bar may change, depending on if I was positioned to the same bar as my host. But now I can loop the bar. Unfortunately it's not the bar that I wanted to loop.

If the looping can be fixed if AlwaysSync=1 and lock host is enabled, that would be ideal.

Thanks!

Looping a bar doesn\'t work when "AlwaysSync"=1

Posted: Mon Apr 16, 2012 8:33 am
by Ralph @ Rayzoon
We need to work on that function.

Looping a bar doesn\'t work when "AlwaysSync"=1

Posted: Sat May 19, 2012 12:32 pm
by drybij_2
As I use that function more and more i find myself creating markers in my DAW software that coincide with important points in the JS timeline. Then I use my midi transport controls to move between them. It's really handy and functional.

The only point where it slows down is when I need to edit a bar that's not at one of the marked points. I then have to unlock the JS controls from the host, select the bar with the mouse, edit the bar and then turn the lock back on.

Since my left hand is already on the midi transport controls, it would be easy to turn off / on the lock without distracting the mouse by using those controls. Perhaps the lock button (by the power knob) could be made accessible to Reaper's midi-learn?

Looping a bar doesn\'t work when "AlwaysSync"=1

Posted: Sat May 19, 2012 1:43 pm
by Ralph @ Rayzoon
We definitely have to work on this more for 3.5

Looping a bar doesn\'t work when "AlwaysSync"=1

Posted: Tue Jan 08, 2013 12:08 pm
by Ralph @ Rayzoon
3.5.1 Beta 2 is now out, which fixes AlwaysSync and also let's you select parts or bars.

Looping a bar doesn\'t work when "AlwaysSync"=1

Posted: Tue Jan 08, 2013 7:05 pm
by drybij_2
Excellent! Thank you Ralph! Will try asap.

Looping a bar doesn\'t work when "AlwaysSync"=1

Posted: Sun Jan 20, 2013 8:54 pm
by drybij_2
I'm having some difficulty with this. At first I thought it was me, but I'm pretty sure I've done the update correctly.

JS doesn't follow Reapers' play cursor when Reapers' transport is idle and I move to a marker position. You had this working before, with other other obvious difficulties. And it worked well for certain parts of my workflow.

The lock in JS's transport is pressed - indented.

I have AlwaysSync=1 still in the Jamstix3.ini file, installed the updated js3sl32.rtxc file (there is no .dll update in the archive, correct? because I didn't see one.) and restarted Reaper / Jamstix. The version in JS still says 3.5.0 32-bit. JS will follow Reapers' play cursor when playing or recording but not when simply moving the play cursor when Reaper is idle.

Looping a bar doesn\'t work when "AlwaysSync"=1

Posted: Mon Jan 21, 2013 9:04 am
by Ralph @ Rayzoon
It's not updated correctly. Please send me rzdlog.txt from Documents\Jamstix3.

Looping a bar doesn\'t work when "AlwaysSync"=1

Posted: Mon Jan 21, 2013 9:28 am
by drybij_2
Thanks for the reply. With that info I figured it out. JS was looking in a different directory than the one I updated. It now says 3.5.1 beta

Looking forward to testing this. I'll report back.

Thanks again.