Superfluous Clefs and Key Signatures
Hi! I'm running OS: macOS 10.16, Arch.: x86_64, MuseScore version (64-bit): 3.5.2.312126096
I'm updating some scores, from sometimes ancient Sibelius files converted to Music XML, and I'm often encountering a whole bunch of unnecessary clefs and key signatures. I can hide things and delete things, but I'm more interested in how to prevent it from happening (I have over 150 scores to edit, and I'd rather prevent than tediously edit). Often it seems like it happens after I've made the individual parts. Thanks for any input in preventing this.
BTW I'm a recently converted Finale user, and I'm really impressed with Musescore. Keep up the great work!
| Attachment | Size |
|---|---|
| to_find_a_song_-_SSAA_piano.mscz | 81.54 KB |
Comments
For your attachment, please cite measure number (and part name) showing the issues you mention.
In reply to For your attachment, please… by Jm6stringer
Sorry for that omission. Soprano I: mm 15, 31, 37, 53, 63, 83, 99, 107. Soprano II: mm 15, 31, 37, 53, 63, 83, 99, 107. Same measures for Alto I and Alto II. Interestingly, does not happen in piano part. In other scores, it does happen in the full score, but not this one.
When I load this into 3.6.2, I don't see anything amiss in those measures, but I do in the very first measure. So it does seem extra clefs have crept into this, but in order to understand how, we'd need you to attach the MusicXML file itself and tell us what to do from there. Probably it will turn out to be something similar to #46036: Clef on first note of system becomes header clef after save and reload. But that doesn't explain whatever you are seeing with key signatures (I don't see this myself). One other thing I do see - some very odd use of multiple voices involving invisible rests.
In reply to When I load this into 3.6.2,… by Marc Sabatella
Thank you for looking at this. You're right, the original engraver did some odd things, for unknown reasons. I also have the original Sibelius file, should that be helpful. (I tried to upload it, but it's a file type not allowed to be uploaded). A lot of these scores are pretty old, and since they were meant for print, the engravers did a lot of "hiding" of things because it didn't effect their final product. Anyway, let me know if you want the original Sibelius file. THANK YOU SO MUCH. :-)
In reply to Thank you for looking at… by CSchaneLydon
Also, the work I'm doing is just cleaning them up. Converting the XML to MSCZ, then putting things in order so that there are no collisions, plenty of space, 8vas are above the staff, lyrics are not colliding with notes, correct MIDI sounds for the various voices, etc.
In reply to Also, the work I'm doing is… by CSchaneLydon
Here's a screenshot illustrating what I'm seeing.
In reply to Here's a screenshot… by CSchaneLydon
I take it that is after generating parts? The MusicXML file is of the whole score. But yeah, full of things it probably shouldn't be. Some of that is just to be expected with MusicXML, it's a good format for representing musical structure but when it comes to formatting, it's generally not reasonably to expect too much to be preserved, and even those things we try to preserve often turn out to be counterproductive because everyone's defaults are different.
First thing I generally do after any MusicXML import is Ctrl+A to select all then Ctrl+R to reset manual adjustments. Actually probably best to run all three of the Reset commands in the Format menu. Then you're starting with MuseScore's own defaults and not some half-baked combination of MuseScore's defaults, the other program's defaults, manual adjustments made there, and quirks in the MusicXML conversions.