Cannot find how to turn a joined double staff with one name into two separate staves.

• Sep 18, 2022 - 00:11

I am stumped again- I downloaded a score with two tenor voice parts joined (a la Grand Staff) in the middle of a score. I can easily remove the bracket; however I cannot figure out how to name each staff separately. The two tenor parts have the word "Tenor" over to the left where the voices/ instruments go. I just want to have the top line for trombone 1 and the bottom line for trombone 2 without just having one designation "trombones." I already used "I" to see the components of the score, but the only options I see are to add or delete a part, and I don't want to do either. I attached a small pic of what I'm talking about. I'm sure it's another easy fix, but I can't seem to find it any where.
Thanks in advance.

Attachment Size
Tenor- how to split.jpg 28.28 KB


In reply to by Marc Sabatella

Yeah, I did it. Wish there was a way to salvage such a staff besides copy/paste and delete remains from score. On the surface it just looked like there should be some way to just be able to remove the name "tenor" between the two staves and rename each one separately.

Anyway, it was good practice figure it and other problems out with imported scores. I had downloaded that one from Choralwiki and found a much better version here, although it needed considerable cleanup. So I did the arrangement a second time with beautiful results. Thanks for your help and suggestions.

In reply to by

There would be a way to manipulate the names if this score had been set up correctly to begin with. It wasn’t though, so the first step was to take those extra few seconds to convert it to the correct format.

Unfortunately there can’t realistically be dedicated commands to automatically fix every possible error that might be found in a score of unknown origin, so the focus tends to be on the problems that come up the most often or that aren’t already so simple to solve through other means. This doesn’t tend to be that common of a problem, and the solution takes only seconds as it is, so thus far it hasn’t been as high a priority as other features.

If enough people find themselves encountering this particular error, it’s certainly possible someday a feature could be added to deal with it. Meanwhile, it’s conceivable that someone could create a plugin to deal with the times this error does occur.

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