I'm looking at 4579, it's fixed there (unless more work was done in 4580). Think I saw treble clefs in one of the last revisions though, so it must have indeed been recently fixed.
Tested on revision 5484: create a piano score using the "create new score" button in the startup dialog and export as MusicXML. This results in a MusicXML file without any clef definition, which apparently on import defaults to using the G clef.
Comments
Fixed in revision 4580.
I'm looking at 4579, it's fixed there (unless more work was done in 4580). Think I saw treble clefs in one of the last revisions though, so it must have indeed been recently fixed.
Automatically closed -- issue fixed for 2 weeks with no activity.
Only seems to happen if it's a new score created in the trunk.
Using MuseScore 2.0 Nightly Build (5133) - Mac 10.6.8.
Does indeed still occur with a new score. Will investigate.
Set to critical as incorrect information is exported.
Tested on revision 5484: create a piano score using the "create new score" button in the startup dialog and export as MusicXML. This results in a MusicXML file without any clef definition, which apparently on import defaults to using the G clef.
Fixed in revision 5486.
Automatically closed -- issue fixed for 2 weeks with no activity.