Can I set up a selected-staves view? [SOLVED]
(MS3) I've scanned the Handbook and can't find how the following might be done. I often work in larger scores (> 5-7 staves). In the Mixer, I can Solo particular instruments, say, Flute-Oboe-Clarinet-Viola-Cello.
When doing playback, only those 5 instruments are heard.
What would be great, is a way to select only F-O-C-V-VC staves to be visible. For as long as I need. As I write this, the idea of Edit->Instruments, then Visible (on/off) comes to me. Is that the only way to do what I'm looking for? Thanks.
Comments
If it's a grouping you use often, the simplest solution is to just generate a part for that group,ing, then you can switch to it in a single click whenever you want.
Otherwise, for MuseScore 3, Edit / Instruments is indeed the way. In MuseScore 4, the visibility checkboxes are easier to access, on the instruments panel in the left sidebar. Also, it will allow you to control visibility of the whole instrument (as in MU3) or individual staves within the instrument.
I reviewed the Handbook for setting up parts... This gets almost where I want, but using a "cover page" in the score jazzes things up, I guess.
In reply to I reviewed the Handbook for… by Are Jayem
Looks like you just need to add a page break to your title frame.
In reply to Looks like you just need to… by Marc Sabatella
Marc -- not sure where to add a PB... I didn't think I am using a title frame?
In reply to Marc -- not sure where to… by Are Jayem
The title frame is the thing you added the cover page info to. It's clearly visible in your image above - shown with a dotted outline. And it looks like you have now added the page break to it, so, problem solved, right?
In reply to The title frame is the thing… by Marc Sabatella
Removing the "cover page" is worth it, to get the parts groupings... I can always add a CP when the score is completed. Appreciated.
In reply to Removing the "cover page" is… by Are Jayem
? Why removing it now that you have fixed it? Youlll just need to re-add it and re-fix again later. It's fixed already in your screen shot, why create extra work now?