Clef does not stay hidden after re-opening file
The clef on stave 2 of this score remains visible even though I cleared the visible tickbox in the inspector. If I export it to PDF then the clef is hidden but it re-appears when I next open the score. I have deleted this bar and re-entered it but the result is the same.
Comments
Generally speaking, hiding elements that are generated on the fly, like clefs, won't be very effective anyhow. If you don't want clefs on this staff for some reason (not clear why, without them people won't know how to read the notes), just turn clefs off in the Staff Properties.
In reply to Generally speaking, hiding… by Marc Sabatella
I want the bass clef but the not the treble clef. I don't know why 2 clefs are showing at the place.
In reply to I want the bass clef but the… by yonah_ag
I think this is probably connected to the hidden time signature - somehow, one of the clefs is before the time signature and the other is after it. Clefs are normally supposed to be before the time signature, so it's the one after it that's incorrect here. That's the bass clef. So select and delete it, then change the existing clef to bass by selecting it and clicking the bass clef in the palette. That should work, but unfortunately it also creates a problem on save/reload, I think because the measure has become a little corrupt. So try inserting a new measure at the beginning of the measure, and copying and pasting the existing content into it.
BTW, I see you've disabled autoplace for some of the text, which caused problems you needed to work around by adding a spacer. It would have been better to just leave autiplace enabled.
In reply to I think this is probably… by Marc Sabatella
Tried your suggestion but it kept doing the same corruption. In the end I added a new stave, gave it the bass clef, copied stave 2, deleted stave 2 then moved the new stave up. It seems to be OK now.
Also tried deleting the spacers and using automatic placement but the texts then didn't line up but went into different vertical positions to each other, according to the height of the note stem in the stave.
In reply to Tried your suggestion but it… by yonah_ag
Well, yes, that is the initial job of automatic placement - to a avoid collisions with the notes. but you don't have to disable it to align the chord symbols. Not only is it unnecessary extra work, it isn't helpful, it causes other problems that take additional work to fix, and it makes it more likely your score will look incorrect if the layout of your score changes in any way (eg, new fonts, new version of MuseScore, viewing on mobile devices, etc). So simply leave it enabled, but then do whatever else you were doing to align them. For instance, manually adjust oneusing the Inspector to be as high as it needs to be, then hit the Set as Style button.
You might subjectively decide you want addition room between the staves still, even though there will be no collisions, but again, don't cause problems for yourself down the road by disabling autoplace unnecessarily. It's almost never necessary or helpful, and will almost always cause problems.
In reply to Well, yes, that is the… by Marc Sabatella
Thanks for the advice. I'm using MS a lot now and trying to take these things on board. I will try again with autoplace. Does it make any difference that they are stave texts rather than chord symbols? If I set this as style am I affecting other scores or just the current one? Is there a document which outlines best practises for scoring in MS?
In reply to Thanks for the advice. I'm… by yonah_ag
Well, they aren't chords, so I wouldn't misuse chord symbols for this. But FWIW, 3.5 does have the ability to automatically align chord symbols. Still, it's trivially simple to align staff text manually just as you already did. You do exactly what you were already doing, except you simply skip the unnecessary extra steps of disabling autoplace and compensating by adding spacers.
As for best practices, every situation is different, so no, there isn't one single document for this. Just keep asking questions here!