MusicXML exported without clef defined
I have been sent a MusicXML file exported from MuseScore v1.2 without a clef defined. I think that this is an error since the file cannot be rendered without a defined clef.
Thanks
Your work is very much appreciated!
James Sutton
Dolphin Computing
| Attachment | Size |
|---|---|
| OdetoSimplicity.mxl | 3.03 KB |
Comments
Thanks for the report. Could you also get the original MuseScore file?
The message with this file says:
"This is a MuseScore file that I created. I think I had first entered it in Finale Songwriter, realized I had the wrong clef, couldn't figure out out to change it in Songwriter and did some copy/paste from Songwriter to MuseScore (I think that's what I did). I've been playing around with both to see if there's any reason to purchase Songwriter. "
The MuseScore file contains an empty cleflist, but both 1.2 and the current trunk display a G clef. On export to MusicXML, the file generated by 1.2 does not contain a clef (which is not correct), the file generated by the trunk does contain a G clef.
As 1.x is frozen (no maintenance is done anymore) and the issue does not occur with the trunk, no action required. Thanks for reporting the issue.
Automatically closed -- issue fixed for 2 weeks with no activity.
This is still a problem
REOPEN
this is still a problem. If you load the attached xml (without clef) and save as xml it still has the clef undefined.
In 1.3 as well as a current nightly build your file Shows a G crel after Import. Export as XML and opening it again too Shows a G clef.
So what problam are you seeing and whgich Version of MuseScore are you using?
using version 1.3 r:5702
If you open the xml file in a text editor and search for "" there is none defined, either in the imported or exported files. I would expect MuseScore to add this element since, as you say it displays a treble clef.
OK, but Leon said about this back in December:
As 1.x is frozen (no maintenance is done anymore) and the issue does not occur with the trunk, no action required. Thanks for reporting the issue.
I don't understand. The latest released version has a valid bug report about a real bug. On what basis can you close this report? Until you release the fix the report should remain open otherwise you will get duplicate reports like this and waste everybody's time.
The lastest Version is a current nighly build, you get it from the bottom of the download page.
As 1.x won't receive any bug fixes, issues against it get closed, unless they are also an issue with the latest nighly build, i.e. not fixed already. Even if that is not yet officially released...
James - you definitely have a point that not having an open issue report for bugs that have been fixed but not in a released version invites the possibility of duplicate reports. But you should also understand that main point of an issue tracker is so the developers can keep track of which bugs still need fixing. So leaving a bug report open after it has been fixed ends up being counterproductive.
Realistically, few users probably don't bother checking to see if a bug report already exists before filing a new one - or they search using different terms and don't find it. So duplicates are inevitable; they simply get closed as they are discovered.
So just know for future reference that as things stand now, you should try to verify if a bug exists in the latest *development* builds (ie, the nightly builds for 2.0) before submitting to the issue tracker. If that is not convenient, but you still wish to report a bug you have found in an existing release, you can always post about it to the bug reports *forum*, and someone else will probably step up to the plate and test it in a developmenet build.