Export Chordnames in all parts
XP r4611.
At the moment,When I am writing an arrangement for Jazz players, I have to put the chordnames in every part or they will not appear in the parts.
I would like to be able to do the chordnames only once, probably in the top part and have them exported in all parts.
Regards,
Comments
so chords should behave like system text rather than staff text, right?
If so: it should be optional (e.g. ctrl-k vs. shift-ctrl-K ?)
Edit: and shouldn't this go into the issue tracker?
In reply to so chords should behave like by Jojo-Schmitz
I wonder what would happen if you clicked the "system" box in the chordname text style, then? Could be worth playing with.
Normally, though, I don't want chordnames in all parts - just comping instruments and soloist(s). So I prefer to have control over which staves they appear in. Copy/paste works well enough, especially if I first copy to a dummy staff, then delete the notes leaving only the chords, then copy and paste from there. But there are several other elements I'd like to be able to place once for several user-defined staves at once, like dynamics. Finale has the concept of a "staff list" that things can be attached to, rather than just the all-or-nothing "staff" or "system". Might be nice to have something like that in MuseScore, too.
In reply to I wonder what would happen if by Marc Sabatella
I could see nothing when I checked the "system" box - certainly the chordnames were not exported. Thanks for the idea, though.
"But there are several other elements I'd like to be able to place once for several user-defined staves at once, like dynamics." and "so chords should behave like system text rather than staff text, right?
If so: it should be optional (e.g. ctrl-k vs. shift-ctrl-K ?)": I agree. For example fermatas do not export in parts. A user defined selection for each part would be very helpful.
Title should probably be: "Export Chordnames in selected parts".
I did not put this in the issue tracker as I do not think this is an unintended result of core.
Regards,
In reply to "system" box by xavierjazz
Well, as with most text style parameters, I wouldn't expect it to affect chords you had already entered. But it *should* be the case that checking that box causes subsequently entered chordnames to display on the top staff of the system and then be exported to all parts. If that doesn't happen, I'd call that much a bug.
In reply to Well, as with most text style by Marc Sabatella
That worked. While trying this I discovered another bug which I will add to the issue tracker: Parts can be closed without a warning that they are not saved.
Thanks again,
Regards,
In reply to Well, as with most text style by Marc Sabatella
And I take back the part about not expecting the system chckbox in the text style to affct already entered chords. I keep forgetting that changes to text style *do* affect existing chords - but only after a reload. I can't remember if that was true in 1.0 or not. That is, I have a feeling that even a reload didn't cause text style changes to be applied to existing chords before 1.1.
In reply to "system" box by xavierjazz
But feature requests can be pit into the issue tracker too, can't they?
In reply to But feature requests can be by Jojo-Schmitz
Sure. A feature request can go to the issue tracker after being well defined. It's better discussing the issue here, to figure out if it's a bug or a feature request. When it's done, it's better if it's more than one sentence in the issue tracker and it adds details of what MuseScore should do, why, external references etc...