Add new comment

maybe it sticks because:

a. it goes beyond its limit eg. loop-start over loop-end;
b. the corresponding parameter absolute value is changed on the GUI;

on both cases you'll have to backtrack until the controller value catches-up the stuck value again.
and yes, since v0.9.2.32git..., all offset and loop points are relative to whole sample length, so that 0% means the beginning (first frame) and 100% the end (last frame); obviously 50% means the middle position; also, loop points do not go either before the offset-start nor after the offset-end points; offset- and loop-start cannot go greater than either offset and loop-end, respectively.

one last hint re. MIDI controllers, is that the term CC means continuous-controllers, so that abrupt or sudden jumps in value might still cause an out-of-the-hook situation and the sync moment gets lost--probably in need to go smoothly in to catch-up and hook on previously (stuck) value back again.

seeya

[UPDATE] ps. v0.9.2.33git head might improve on the "sticky" issue but remember that the general considerations above do still apply, nevertheless.