ell1e

I'm really sorry if I'm sending this to the wrong location. ETR is awesome! But my keyboard is a reduced size one with awkward arrow keys. Maybe there would be a possibility at some point to add WSAD controls? Since WSAD don't seem to be used for something else important, they could probably be offered at the same time so no UI changes would be needed since it could be done without a toggle. I realize this is a volunteer project so I understand if nobody ever gets around to this, I just thought maybe...

Should playback go to the end, loop back to first measure, play until the loop is reached, and then loop? Yes, this is also what REAPER does for me. (Not sure if it was the default or I changed it, tbh.) And REAPER has an option for jump to loop immediately or not, I think. REAPER is a reasonably popular professional audio workstation. (I bring it up because I don't know the other big ones that well, they might have an option here too.) Not one of the biggest super known ones but sort of an insider...

Sorry I didn't have time to test it yet, got dragged into some things. However, I agree that at least when I proposed it I also thought there should be no unnecessary jumping, because it allows doing a sort of uninterrupted going-with-the-flow live'ish vibe&compose style where you want the beat to not do weird skips. And if you wanted to fast forward, you could still click to jump after all. Whether this is how the majority would find it useful, I don't know. But I'd rather not have the program do...

For what it's worth, I can see the surprised users problem but I also think it sounds useful to have the range stay (since why would stopping change what is looped? Thinking from a conceptual & new user angle). If it is decided to be useful, from there I can see three possible ways to go about it: Rename the option to "Advanced Looping" and toggle this with the option as well. This would intuitively make more sense to me if the whole looping approach including looping the entire song with no range...

Hm I see. For what it's worth, the only reason I'm even suggesting it is that Rosegarden's midi import otherwise is really intuitive and excellent, so it seemingly sometimes failing to "detect" the instrument just seemed a bit out of character to me when I ran into it. I have never had anything unexpected happen outside of this, it's working really well.

What if the instrument parameters showed the first program change info anyway, but stored/remembered internally with marker that the event still exists and the event wasn't removed, and as long as the event instrument isn't changed there is no duplicate program change saved/sent to devices from the instrument parameters due to that stored/remembered marker? Or is that too complicated? Basically, I feel like the states "instrument parameters show instrument", and "program change was at 0 seconds and...

I can only repeat myself, but as I already stated yes I find it desirable, and no I don't want to loop immediately, pretty much never. (Or in the few cases I do, I just left-click for play jump.) I already explained why too. And while I get having it jump there immediately might be nice for you and others with that preference, you could still just left-click to get the play cursor there while there isn't really a reverse approach like that to stop it from jumping: so that seems to me like the worst...

I can only repeat myself, but as I already stated yes I find it desirable, and no I don't want to loop immediately, pretty much never. (Or in the few cases I do, I just left-click for play jump.) I already explained why too. And while I get having it jump there immediately might be nice for you and others with that preference, you could still just left-click to get the play cursor there while there isn't really a reverse approach like that to stop it from jumping: so that seems to me like the worst...