visible in parts/visible in score

• May 19, 2019 - 00:52

Is it possible to tell individual elements (I'm most interested in text) to be visible in the parts but not in the score? And vice versa?


Yes. Change their visibility after you create parts and they will be independent. If you find exceptions it should be considered a bug.

In reply to by mike320

Thank you.

I could not manage to find this info by searching the Handbook. (Possibly because I didn't know the best search terms to use?) Is it there?

I do think a feature for this somewhere in Text Styles and/or the Inspector would be nice, i.e. so as not to have to go back through the score later just for this.

In reply to by kacattac

This lets you do things like make a certain system text visible in some parts and invisible in others and visible (or invisible) in the score. It gives a lot of flexibility.

I didn't find anything in the manual after a quick search that tells you about this capability. Perhaps it should be included in the Customize Parts section of the handbook.

In reply to by Jojo-Schmitz

If you make them invisible in the score they are invisible when you create parts from that score, in this sense they are dependent. However, you do still have the option to toggle visibility after you make a part. In this sense they remain independent. It seemed kacattac understood what I was talking about.

Thanks guys. So if I create parts before writing a single note, I can create "visible in parts" text as I go simply by making it invisible in the score? But if I create parts only after completing the score then I have to go back through the score to find the text I want to show only in parts?

For some reason I am in the habit of creating parts only at the end of the process. I think it's residual anxiety from early versions of both Sibelius and MuseScore where all kinds of things went wrong with parts if you got too fancy too soon. It seems we are over most all of those problems; so does that mean that File>Parts...>New All should be my first order of business after creating a new file?

In reply to by kacattac

I generally create parts after all of the score is entered and have few problems. The visible vs invisible text is rather small compared to the overall score in my experience, so this works well for me.

One thing I use a lot is the tempochanges plugin. It makes most of the tempo changes invisible automatically, but I don't think this would be passed to existing parts.

In reply to by kacattac

The order is not relevant except that it sets the starting point. Try it yourself - whether you set the marking invisible in the score before generating parts or not, you are free to toggle visibiltiy in the part all yu want without affecting the score. The only effect of setting it invisible in the score before generating the aprt is whether it starts out visible in the part or not.

Creating parts at the end of the process is still the usual recommendation. If you make things invisible in the score before generating the parts, it's no big deal to then go to the parts and make everything visible (select all, press "Set Visible" in Inspector).

In reply to by Marc Sabatella

I understand that I can always toggle it. But I really want to do this immediately after the text is entered in score, i.e. at a stage in the creative process when massive formatting changes are perhaps yet to come and parts are thus not yet created. The reason is: to go back and do this later, you have to remember where all of these little pests are hiding (or go looking especially for them, which is a thankless and error-prone method).

Specifically: I write a lot of cue-text in my parts, e.g. "w/guitar" in the sax part and "w/sax" in the guitar part, if these two play together for an extended passage. This speeds rehearsal and helps the players. But ideally it would not show up in score, just like cue notes would not. (It's a "cue" of sorts, but given during playing rather than resting.) The current feature is certainly adequate, but a global "visible in score"/"visible in parts"/"visible in all" feature in the Inspector would be super awesome.

In reply to by kacattac

Hmm, as a conductor I would really prefer to have markings in parts that I can't see on my score, it's bad practice. But that said, you should fine either way. Make them invisible in the score right away, sure, then after generating parts, just do the Ctrl+A / Set Visible as I suggested - no remembering of individual texts required.

The idea of having more controls over which properties get linked and which do not is a rather bigger question that does come up and we need a good solution for, it will need to go beyond just the "visible" property.

In reply to by Marc Sabatella

re: "markings in parts that I can't see in my score," I think it just depends. Cues are generally not shown in full score; but in educational music you don't just cue the bassoon part in the trombones to help the trombones come in at the right spot, you also do it in case you don't have a bassoonist that year (or ever), in which case the conductor/teacher needs to know who else they can assign to play the passage.

There's no reason I can think of that a pro conductor would need extra text telling them that the bassoons and trombones are in unison when they can (or ought to) already see this in the notation. But the players (even pros) sometimes can't tell right away in dense textures, so an indication in the parts can be helpful.

I've studied with two composition teachers, one never thought to mention anything about this, the other was rather bothered by all the cue text and thought it was cluttering the score for no good reason.

In reply to by kacattac

The reason I like to see what the players see is to waste less time in rehearsal when I'm wondering why I'm not hearing what I see, or they ask me what some marking means, etc. I like to know who has cues so I can tell them "go ahead and play your cues", etc. Although indeed, cues just to help with entrances aren't useful.

Do you still have an unanswered question? Please log in first to post your question.