Instrument name duplicates when creating a part
1. Open score.
2. Create part.
Result: Instrument name doubles, appearing leftward above the stave. There is also a large version of the instrument name that appears next to the score title.
Using MuseScore 2.0 nightly build (4141) - Mac 10.4.11.
Attachment | Size |
---|---|
Duplicated Instrument Name.jpg | 33.73 KB |
Comments
I don't know about the duplicated small name, but the large name is presumably on purpose. It was in 1.0 too - it's not a staff name, but a *part* name (created when you create the part). In 1.0, by default, staff names in generated parts are blank.
I did wonder about the large name, but one might not want it - especially if you create a part that has multiple instruments, in which it'll only list one.
In 1.0 at least, you have control over the part name; you can set it blank if you want. Looks like with 2.0 and the new linked parts facility, things are different, and it's not clear to me if there is a way to control the title that gets added to the part as text. But after creating the part, you can that text title normally, so you certainly aren't forced to use one.
I'd imagine that 99% of the time, you'd want it, so I'm glad something is generated by default. But I think it should be the part title, not the name of one of the staves, so that much does seem like a bug to me. BTW, I couldn't figure out how to reproduce the duplicate staff name - maybe more specific instructions would help?
In any event, it seems to me linked parts are still only partially implemented. There's enough there to get an idea of how things will work, but lots of things don't work right, so I haven't been bothering to submit issues on this feature on the assumption that it's still a work in progress. If people would like to see issues submitted on this, I'm happy to start doing so.
Appears to be fixed in 2.0 nightly build (4145). The large version still appears though - still not sure whether it should, or not.
I know what you mean about the continuing development and you want to see how it pans out before jumping in - I'd probably just file the reports :).
Automatically closed -- issue fixed for 2 weeks with no activity.