add a staff to grand staff
I need to add a bass clef staff to a grand staff, below the existing bass clef staff. In other words, a 3 stave grand staff for 24 measures. (of secondary concern would be to include bracket for all 3.)
I need to add a bass clef staff to a grand staff, below the existing bass clef staff. In other words, a 3 stave grand staff for 24 measures. (of secondary concern would be to include bracket for all 3.)
Do you still have an unanswered question? Please log in first to post your question.
Comments
So just add it? Press I, select the bottom piano staff and press "Add staff", then change the clef to bass, then extend the bracket, double click it, drag the handle down
In reply to So just add it? Press I,… by Jojo-Schmitz
So just add it? Wise guy!🤔
Thank you ...and Happy New Year!
And then, after entering notes, use Format / Style / Hide empty staves (or, right-click the staff itself, set "Hide when empty" to "Always") if you only want the extra staff for those bars.
In reply to And then, after entering… by Marc Sabatella
Oh yes! - that would have been the next question for sure. Happy New Year to you, too.
In reply to Oh yes! - that would have… by penne vodka
I cannot get rid of the extra staff in the first system. If I try to do so, I lose the bass staff as well (and the pedal markings).
I see no "always" when I right click-the staff, nor under staff properties. I use 2.3.2
In reply to I cannot get rid of the… by penne vodka
Press 'I';
Select (on right) Stave1;
Press: 'Add stave';
Use the central arrow (up/down) to move it.
In reply to I cannot get rid of the… by penne vodka
That is a 3.0 feature
In reply to I cannot get rid of the… by penne vodka
I definitely recommend using to 3.0, many really major improvements to be had. Meanwhile, in 2.3.2 you can set the bass clef staff to "Never hide".
In reply to I definitely recommend using… by Marc Sabatella
Thanks to all. No offense, Marc - you've been like the cavalry - but as you know I struggle with 2.3.2 and version 3 has more bugs than the entire state of Florida...I'll wait just a bit longer...just a bit...
BTW - your fix worked.
In reply to Thanks to all. No offense,… by penne vodka
No offense taken. But it just seems to me many of the things you struggle with in 2.3.2 are already solved in 3.0 and life would be easier if you updated.
In reply to Thanks to all. No offense,… by penne vodka
I think the bugs in version 3 would be more annoying than love bugs in the spring. I haven't yet sold out to version 3 because there are basically too many things that are impossible to do in a symphonic score. Anatoly asked me to let him know when I change my mind, and will do so publicly when the time comes.
In reply to I think the bugs in version… by mike320
Yeah...if I may evoke Star Trek's Dr. McCoy. "I'm a composer, not a software engineer!"
I'm learning, but not fast enough for my liking. I think I'll be cowardly and let you run point on this, though I am looking forward to v3.
In reply to Yeah...if I may evoke Star… by penne vodka
If you decided to test it, it would only benefit everyone. It will peacefully coexists with version 2. Try to enter a score, and when you find a bug report it here in the forums. If there is a work around, someone can let you know what it is. If it's not a know bug, which is what we're looking for, a formal bug report can be entered.
If it gets to the point you can't continue, you can save the score as musicxml and open it in version 2 to finish it. The goal in version 3 is that you will have to do very few manual adjustments, so you're not likely to lose a lot of adjustments in version 2. You'll just have to do the ones you didn't need to do in version 3. I honestly got so used to some of my workarounds I don't even think about them being bugs until I see them reported. Version 3 is stable enough that I'm not too concerned about losing work now, just not being able to enter a complete score.
In reply to If you decided to test it,… by mike320
Take one for the team, huh? (sigh). Okay. Actually, I'm having a hell of a time with an old piano work which requires an extra staff alternately and I thought the 2.3.2 workarounds worked, until I went back to the beginning.
Will I be able to load this file from my current version to V3?
Could I still use V2.3.2 to "save online" the music I have there for upload? I think I've read the two versions will work side by side.
In reply to Take one for the team, huh? … by penne vodka
You can open version 2 scores in version 3. Tell version 3 to reset items when you open it, you'll understand when you open the first score. There is no need to use version 2 to upload the score, it works fine from version 3.
Since you use custom sound fonts, I suggest that you do what I did. Open preferences in version 2 and select the path to sound fonts there and copy it. Next, open preferences in version 3 and paste the path there so you don't have to worry about copying all of your sound fonts to the new location. Finally make sure the sound fonts are listed the same in both synthesizers and save as default to avoid future sound problems.
In reply to You can open version 2… by mike320
That's a ten-four.
why couldn't I take up painting?
In reply to That's a ten-four. why… by penne vodka
Painting is boring.
In reply to Take one for the team, huh? … by penne vodka
Both versions can save online, only scores saved with 2.x can get opened by the Android / iOS app currently
In reply to I think the bugs in version… by mike320
FWIW, my sense is that both versions have bugs and limitations. Those who are power users with 2.3.2 and accustomed to its quirks and limitations and the various workaround required to get basic things to work out well will be more sensitive to the quirks of 3.0 and the ways in which the old workarounds don't work any more. I think relatively inexperienced users will be happier using 3.0 and having most things just work by default, and won't see each quirks as being more problematic than those of 2.3.2
In reply to FWIW, my sense is that both… by Marc Sabatella
Sold!