Playback should be able to select voices, not just instruments

• Nov 8, 2011 - 17:31
Type
Functional
Severity
S5 - Suggestion
Status
active
Regression
No
Workaround
No
Project

Enhancement Request: It'd be pretty helpful if for example for a 2 stave S/A+T/B score one could listen to e.g. Bass only.
Currently this requires a full 4 stave SATB score, which then of courses takes twice the space (on paper).

This request came up in the German forum, see http://musescore.org/de/node/13338
Also in the English forum http://musescore.org/en/node/13340 (but no discussion there)


Comments

I think this should include also the volume control for single voices, because one may want to hear the main voice very loud and the other voices more quiet as background. This is very useful for practising the own voice. Especially, when there are parts of silence for the main voice, it's good to have the other voices as an orientation at the next starting point.

I would love to see this feature.

Maybe it could be implemented as a function to split a multi-voice staff into two separate staves?

A quick solution for many standard use cases until a release of this requested feature comes would be, if it would be possible to set a negative stave distance value (under Style --> General... --> Page --> Stave Distance).

Many of my SATB sheets have the lyrics attached to the Alto voice. With negative stave distance, it would then be possible to completely overlap S+A and T+B visually and still having them in separate instruments with separate playback functionality.

If one of the devs reads this: Would this be a big issue to implement as an interim solution?

Severity S5 - Suggestion S2 - Critical
Reported version 2.1  
Regression No
Workaround No

I was about to switch to Musescore for our Choir, but not being able to play back single voices in a multi voice staff locks me into other software packages. Overall functionality and features of musescore are great, but this is a blocking issue for me/us.

Severity S2 - Critical S5 - Suggestion

This issue tracker here has been discontinued so better report it on GitHub
And it still is a feature request, not a critical big