have you submitted this as a request?
this is not the same as rotate, which is destructive, nor the same as start offset (which is only used on initial play).
this means it needs to have a UI to control (e.g. how to set the loop start point) and also to show the user where the current start is… ideally you would need some way of visually seeing where the loop is in the full track. (e.g. see you are looping bars 3-6, of 1-6)… also it wouldn’t be long before a user said they they want to have loop start and end, as they don’t want to change the length.
also it does have other complications…
you are implying that length actually is now not the full length of the track, length now becomes LENGTH - loop start (this could have widespread implications in the code ), also something like the DISP screen for track, would now have to change, either due to the current loop length OR better still to show the full length still, but highlight the looped section.
I think often now though the question is… is this within the scope/vision of the pyramid?
it can never have all daw functions, so where do you stop?
and does the pyramid have resources left to do it?
as users, we dont have access to the code base, so we cannot say what is easy/hard to implement… we have to trust Squarp to do what they think is feasible - which I think they have done a really good job.