Part name in header
MuseScore 3.6
When I use the $I or $i tag in a header the result is blank, even though the part name is known in Part properties and is also in the part name box. Why? What am I missing? (This is in a single-part score, not a part generated from a larger score.)
Comments
Not sure what '$I' and '$i' are supposed to be, as far as I can tell no such macro exists, but the macro for partname would be '$:partName:'. It is set only in parts, not in the main score though
In reply to Not sure what $I and $I are… by Jojo-Schmitz
MuseScore 3.6.2:
"$I" and "$i" (as shown in popup - while opening header/footer texts)
work both - as well as "$:partName:" - in all existing single parts.
In reply to MuseScore 3.6.2: "$I" and "… by Rudi cj7tb
. . . but missing in online handbook . . .
In reply to . . . but missing in online… by Rudi cj7tb
Oops, we'd need to update that tooltip screenshot in the handbook!
In reply to MuseScore 3.6.2: "$I" and "… by Rudi cj7tb
Yes, "$I" and "$i" in the popup; "$:partName:" is not listed among the metadata tags there. So that is new information to me. But I just tested "$:partName:" (no quotes) and it's blank too, so that doesn't work either.
In reply to Yes, "$I" and "$i" in the… by Gerald Reynolds
$:partname:exists only in (linked) parts (created for File > Parts), not in the main score (unless manually added there, via File Score properties > New). And if there is no$:partname:, these$Iand$ican't work either. I guess they should better not get shown too in the tool tip for the main score.In reply to $:partname: exists only in … by Jojo-Schmitz
Ah, OK, so I added partName to Score Properties (and populated it) in the main score, and it shows up in the header using any of "$I", $i", or $:partName:". That at least explains what's going on. What I would suggest, then, is that it be included as a property in the main score with the default value "All Parts" or something similar (language dependent). Then one would not need to mess with the tooltip, making it different for the main score and the parts.
In reply to Ah, OK, so I added partName… by Gerald Reynolds
Another possible default value that comes to mind is "Full Score". But if the full score consists of a single part, it could be possible to override it with that part name, if that extra coding is thought justifiable.
In reply to Another possible default… by Gerald Reynolds
"Full Score" makes sense only in English. Any special casing IMHO isn't needed, a score with no linked parts simply doesn't have a pathName tag and doesn't need it either. If you personally absolutely need and want one it is simple enough to add, no extra codind for this is justifiable IMHO
In reply to Ah, OK, so I added partName… by Gerald Reynolds
Having
$:partName:populated in the main score makes no sense at all.In reply to Having $:partName: populated… by Jojo-Schmitz
I respect your opinion but don't share it. Having some value there that can be used in the header even of the main score can in fact be quite useful (and yes, I've tested the workaround; it works, but at the very least the online handbook should document it). When one is printing the main score and all the parts for a full orchestration, one would like to set the header in the main score to include the part name macro so one does not have to go back and add it to the header of each part after part extraction; it will be populated into the parts automatically. Consider, for example, a header such as "Symphony of the Winds, $:partName:, Page $p". Besides appearing in each part with its part name, it will appear on the main score with "Full Score" (or something similar) for the part name, rather than just a comma. That makes very good sense.
In reply to I respect your opinion but… by Gerald Reynolds
If a score has linked parts , those do have
$:partName:available. You can add it so the main score's header/footer, but it won't print, and I don't see where that is an issue (you can tell a maon score from it's parts at one single glance: the main score has more than one instrument). If it is a problem for you, either drop that macro from the main score's header footer or just add it to its score properties, either is easy enough to do.The handbook needs fixing for sure. It is like a Wiki, you can do it ;-)
In reply to If a score has linked parts … by Jojo-Schmitz
Yes, you can tell a main score from its parts at a glance. It is not my point to use the part name to make that distinction. Rather, it is to be able to have a consistent header that applies equally to the main score and all the parts, without having to edit either the header or the score properties to make it happen.
You said if I add it to the main score's header/footer it won't print (it doesn't unless you also edit the score properties) but you don't see where that is an issue. I just gave you an example where it is an issue. In that example, in the main score header you'd get "Symphony of the Winds, , Page 2" on the second page. The extraneous comma after the null part name is undesired, and that is an issue. To avoid it one or the other workaround must be used; either define it in the score properties or remove it from the header in the main score after extracting the parts. But if you remove it and then later edit something and re-extract the parts, you'd have to add it back while doing that, then remove it again before printing. That is an issue that my suggestion seeks to avoid. That's why I felt it was worth submitting in the issue tracker.
In reply to Yes, you can tell a main… by Gerald Reynolds
With the other workaround, adding it to the main score, you'd not have to add it back later to any new part
In reply to If a score has linked parts … by Jojo-Schmitz
About editing the handbook myself, if the issue as I submitted it in the issue tracker is actioned, that will affect what needs to be said in the handbook, and it will depend on how that is done. So I'd rather see what decision is made about that, and preferably let those who make that decision edit the handbook accordingly.
In reply to About editing the handbook… by Gerald Reynolds
As there is no further MuseScore 3.x planned and MuseScore 4 will get/need a new handbook, there's no need to hesitate and not documenting the current state.
In reply to As there is no further… by Jojo-Schmitz
Fair point. Do you have a link to where the edit should be made? If so, I'll think about it.
In reply to Fair point. Do you have a… by Gerald Reynolds
https://musescore.org/en/handbook/3/score-properties
Esp. an updated image for the Tooltip is needed. And maybe a note that it doesn't contain the partName macro.
In reply to https://musescore.org/en… by Jojo-Schmitz
Not sure if I can capture an image for the tooltip. It comes and goes unpredictably and too quickly. But I'll try.
In reply to Not sure if I can capture an… by Gerald Reynolds
I can try, but not today anymore
In reply to I can try, but not today… by Jojo-Schmitz
Just got it.
In reply to Just got it. by Gerald Reynolds
I've made the changes and replaced the tooltip screenshot. Does it look OK to you?
In reply to I've made the changes and… by Gerald Reynolds
Looks good, thanks!
In reply to I've made the changes and… by Gerald Reynolds
Looks good, but the changed name results in some of the translations of that page to now lack that image.
I've fixed those now.
However: better leave the names of images the same when updating them
In reply to Looks good, but the changed… by Jojo-Schmitz
Sorry, didn't think of that. Will keep it in mind for the future. Did you check both the images I replaced? (Tooltip and Style dialog)
In reply to Sorry, didn't think of that… by Gerald Reynolds
I think I did. At least all translations show images rather than a read bold warning about a missing file
In reply to Not sure what $I and $I are… by Jojo-Schmitz
So if the main score is just a single part (and you don't generate a part score from it), but you want to use this macro, it won't work?
My suggestion: If the score (main or otherwise) contains a single part, that's the part name the macro should return. Else it may be appropriate to return "All Parts" or something similar (language dependent). For a single part the source of the name would be the part name for the instrument, as seen in Staff and Part Properties.
If the "$I" and "$i" macros do not exist, either create them to match the popup or remove them from the popup and add "$:partName:" to it.
In reply to So if the main score is just… by Gerald Reynolds
I just checked on a generated part from the same single-part score, and "$I", "$i", and "$:partName:" all work there, just not in the main score. So my suggestion above to make it also work in the main score seems to be needed. Also, "$:partName:" should be added to the popup.
In reply to I just checked on a… by Gerald Reynolds
$:partName:is in File Score properties, on a part. But not on the main score See above.Might be better to update the tooltip for parts to include all 3 meta tags (and remove 2 from the tooltip for the main score).
Feel free to submit this into the issue tracker
In reply to $:partName: is in File Score… by Jojo-Schmitz
OK, I submitted it in the issue tracker, both with my suggestion and allowance for your objection to it.
In reply to OK, I submitted it in the… by Gerald Reynolds
Thanks for #326052: Part name in page header
In reply to Not sure what $I and $I are… by Jojo-Schmitz
[Deleted]