.48 Setting a loop point stops sample

[Saga Musix]

Full Version:
OpenMPT v1.17.02.48

Has the bug occured in previous versions? If yes, please specify version(s): (This option is optional, and doesn't need research. But in case you know...)
All versions.


Description of the bug:
If you play a sample, have its loop set to disabled and type some numbers into the loop point textboxes, this makes the sample stop. There's no reason why...


How to reproduce (step by step description):
Play a long sample, disable loop and enter some loop point settings in the input boxes.

Fixed in OpenMPT 1.17.02.53

[Sam_Zen]

You're right. Quite peculiar behaviour here.
It stops, but not all the time. And sometimes the playing even jumps back to the start and runs until the new End value.

More testing has to be done here, with all the variables and combinations.
Like the existing values of Start and End, before the test. The position of the playback cursor on the moment of typing a new value. Even the value of the cursorposition saved in the statusbar on the moment of leaving the area.

I tried to change the End position not by typing, but with the r-click contextmenu, while the playback was on.
There was no pre-stop, but to my surprise the playing stopped at this new End point. While Loop was disabled ....
Again this raises questions about a correct functioning of the Loop dialog.

[Saga Musix]

another strange behaviour: if you have loop enabled and mark a part of the sample behind the second loop point (it may be partially behind it, it doesn't have to be the whole loop), the sample plays like there was no marked part at all...

[Sam_Zen]

So it's more the discrepancies between the functioning of the fixed Loop dialog and the realtime changing functioning of the playback. There doesn't seem te be any consistent hierarchy of what overrules what, when performing a command.

[Saga Musix]

both cases will be fixed in .53