Stave text entered into parts appears on the main score

• Aug 22, 2013 - 11:50
Type
Functional
Severity
S5 - Suggestion
Status
active
Project

Stave text entered into parts appears on the main score

This is undesirable as it makes it more difficult to add specific notes for the performer of a part

Stave text entered into parts appears on the main score

MuseScore2 commit-9560130
Windows 8 Pro


Comments

Hmm. Not sure why you wouldn't expect this. My expectation would be that adding staff text to a part *would* show up as staff text on the score. Not on everyone else's parts of course, but on the score, as staff text. So the current behavior seems correct to me.

As a conductor, I expect to see text instructions given to players. I suppose it should be possible to create "secret" instructions the conductor doesn't know about, but I don't think it should be encouraged. This does open up the more general question of how this sort of thing should be managed. I think that manual edits to elements - including position adjustments - made while viewing a part shold probably affect the part only. But elements added to a part should reflect in the score as well unless one takes explicit steps to make these elements "secret".

An example would be keyboard change directions for organ or harpsichord players.

Other things can be valve positions for brass players

Position numbers for string players.

Barre numbers for guitarists

These are all irrelevant to the conductor, who is concerned about the overall sound, not the minutiae of performance, but essential for the players concerned.

I suppose, but still, surely, that's the exception and not the rule? I'd expect the vast majority of text to be something that should be in the score. Surely all scores I see have tons of this sort of text.

Maybe a 3rd category, in addition to the existing "system text" and "staff text" a "part (only) text"?
Or staff text added to the score propagates to the part, but staff text added to a part doesn't propagate back to the score?
So if there is staff text that is releavat to the entire score it needs to be entered in the score rather than the part?
Or some flag, where staff text in score defaults to being staff text while in a part it defaults to being part only text?

I think "most" items added while viewing a part should propagate back to the score. Notes and rests obviously (?), also articulations, lyrics, chord symbols, time or key signature changes, etc - really virtually everything except perhaps a very few markings. So I don't like making a special exclusion for staff text, especially since as I mentioned, *most* staff text really does belong in the score as well.

A possibility that occurs to me is to have a modifier on the Visible flag saying whether an item is to be invisible to both score and parts or just score or just part.

But there does need to be a way of marking some elements as score-only or part-only. Assuming there is something in place internally to handle differences in *position* between score and parts (and here, I definitely would agree that what happens in a part, stays in a part), I'd think we should piggyback off that.

Indeed there may will be occasions when you wish to add comments and instructions specifically for the conductor.

In fact this maybe the most common use.

A checkbox in Text Properties would seem to me to be the way to go.

The solution for now seems to be add the text to either score or part, mark it invisible wherever you don't want it. I guess that option existed when I posted #5, I just didn't realize it would work. That is, if you mark something invisible, it only affects that instance.

Ultimately, I could see adding a "break link" command that you could invoke on a selected item or items. The you could delete it from wherever you like without affecting the other versions. Or some way of specifying while adding the item that you don't want it duplicated.

Anyhow, since it's possible to get the effect described here already, and now we're just talking about how *else* it could be made possible, I'm reclassifying this.