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
-
Ralph @ Rayzoon
- Site Admin
- Posts: 5858
- Joined: Wed Jan 02, 2008 6:24 pm
Looping a bar doesn\'t work when "AlwaysSync"=1
We need to work on that function.
Ralph
Rayzoon Technologies LLC
Rayzoon Technologies LLC
Looping a bar doesn\'t work when "AlwaysSync"=1
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?
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?
-
Ralph @ Rayzoon
- Site Admin
- Posts: 5858
- Joined: Wed Jan 02, 2008 6:24 pm
Looping a bar doesn\'t work when "AlwaysSync"=1
We definitely have to work on this more for 3.5
Ralph
Rayzoon Technologies LLC
Rayzoon Technologies LLC
-
Ralph @ Rayzoon
- Site Admin
- Posts: 5858
- Joined: Wed Jan 02, 2008 6:24 pm
Looping a bar doesn\'t work when "AlwaysSync"=1
3.5.1 Beta 2 is now out, which fixes AlwaysSync and also let's you select parts or bars.
Ralph
Rayzoon Technologies LLC
Rayzoon Technologies LLC
Looping a bar doesn\'t work when "AlwaysSync"=1
Excellent! Thank you Ralph! Will try asap.
Looping a bar doesn\'t work when "AlwaysSync"=1
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.
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.
-
Ralph @ Rayzoon
- Site Admin
- Posts: 5858
- Joined: Wed Jan 02, 2008 6:24 pm
Looping a bar doesn\'t work when "AlwaysSync"=1
It's not updated correctly. Please send me rzdlog.txt from Documents\Jamstix3.
Ralph
Rayzoon Technologies LLC
Rayzoon Technologies LLC
Looping a bar doesn\'t work when "AlwaysSync"=1
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.
Looking forward to testing this. I'll report back.
Thanks again.