as you are changing the loop-start point the loop-end relative position changes accordingly, meaning that the relative loop-end point position has gone out of sync to the external MIDI controller value and it has now to play catch-up to make it hooked back again :)
offset/loop points that are set on the main GUI are absolute / concrete positions (in sample time or frame units); however, the controllable/automatable LV2 plugin input control ports there having the same name (ie. offset/loop-start/end) are always expressed in relative / abstract normalized units (eg. a percentage)--i believe this has been discussed on github issue#20 where you participated.
hope it gets now clearer--t's a dang feature, not quite a bug ;)
no, it is not a bug.
as you are changing the loop-start point the loop-end relative position changes accordingly, meaning that the relative loop-end point position has gone out of sync to the external MIDI controller value and it has now to play catch-up to make it hooked back again :)
offset/loop points that are set on the main GUI are absolute / concrete positions (in sample time or frame units); however, the controllable/automatable LV2 plugin input control ports there having the same name (ie. offset/loop-start/end) are always expressed in relative / abstract normalized units (eg. a percentage)--i believe this has been discussed on github issue#20 where you participated.
hope it gets now clearer--t's a dang feature, not quite a bug ;)
cheers