Music play not starting on selected note.
I did a pull from git this morning and compiled. My rev is now: f5524ab
I managed to make progress on yesterday's piece, albeit a little problem with paste leaving an incorrect rest after copying a full measure into an empty measure, but my latest problem is:-
In the attached score, I have a central section which is repeated. If I ask mscore to play from the first note of the section after the repeat, (measure 19), it actually starts playing from the beginning of the repeat section (measure 5).
If I select a start point further in to the final section, say measure 20, playback starts at the same count of measures in on the repeat section, that I have selected to start in the final section.
It gets a bit annoying to have to listen to the repeat section every time I want to change and listen to the final section.
Playback starts from the correct selected note anywhere before the 'repeat' bar line in measure 18.
Score attached.
| Attachment | Size |
|---|---|
| alligator3.mscz | 2.39 KB |
Comments
Have you tried not to select "Repeat"?
In reply to Hi, by Shoichi
OK. Thank you. I tried it after clicking off 'repeat' and it did play from the correct place, immediately after the repeat bar.
However........
I see this as a circumvention of the problem. The program documentation says:
"MuseScore starts playback from the place it last left off. If you select a note, MuseScore plays from there instead."
and it seems more logical to me to start on the selected note rather than to jump backwards into a repeat section.
Meantime, thanks shoichi, at least I will not get so annoyed now!
In reply to OK. Thank you. I tried it by turtlevt
Yes, it's just that it is a known issue that in some cases having repeats turned on can cause problems. But I though it was only immediately after an edit, and also, fixed for 2.0 already. Maybe I'm wrong. But if not, sounds like this is a new bug.
In reply to Yes, it's just that it is a by Marc Sabatella
Marc, you say this problem is fixed for 2.0. I am using the newer versions as they progress towards 2.0, so either it is not fixed or may be a new bug, as you say.