Feature Request: allow both old and new way of playing back selected parts

• May 7, 2019 - 13:53
Reported version
3.x-dev
Type
Functional
Frequency
Once
Severity
S5 - Suggestion
Reproducibility
Always
Status
active
Regression
No
Workaround
No
Project

The beta version has altered the default looping behaviour. Before, to loop the playback of all the parts of a section, one just had to select any measure and hit playback button. In the beta version, only user-selected staff measures playback when looped, meaning that any hidden staffs are not included. Now, to play back the full section, one has to click on a staff with the ctrl button held to first select all the staffs of a measure, including hidden ones, before shift-clicking on the next measure to extend the selection. It's awkward. Being able to loop a particular staff is a welcomed new feature. However, in my opinion, the default behavior should remain as it is in Musescore 3, non-beta, since I would guess that looping all instruments would be more frequent than highlighting particular ones. In additon, the mixer already provides a means to playback particular instruments.

As mike320 mentioned in my original post, "There needs to be a different way to limit playback. Perhaps a new button could be added to the playback toolbar and/or the play panel."

Perhaps, the loop button could have two states, much like how some audio players change the loop icon to show the current type of looping (e.g., loop song, loop playlist, etc)--in this case, all or selected staffs.


Comments

Having two states of looping would allow quick switching back and forth between soloing a part and playing it in full context when looping without having to reselect any measure.

Title Feature Request: allow both old and new way of looping Feature Request: allow both old and new way of playing back selected parts

Adjustment of wording of the title. Looping playback is something else entirely.

In MuseScore 3.1 there won't be a new way of soloing instruments. We reverted the changes.

We will revise the feature (since a lot of users really loved the new approach) and reimplement it again in later versions.