problem with xml export yesterday
For those of you using musescore, i m having trouble this afternoon fixing errors using the arrow up/down shortcut. The musescore file reflects the change correctly (and plays it correctly), but the xml export goes haywire (such as without acknowledging the change or making the rest of the measures played in white keys without accidentals). Not sure if anyone experienced this recently on musescore.
Comments
Can you attach the problematic file here?
In reply to Can you attach the… by Shoichi
Here it is.
In reply to Here it is. by drlucas
Two tests: before and after up arrow
In reply to Two tests: before and after… by Shoichi
2°
In reply to 2° by Shoichi
3°
In reply to 2° by Shoichi
Let me show you:
0.xml is a file I received from another machine
I open it on musescore
m. 77 I highlight the 3rd and 4th beat of RH with a box and press arrow down to change the octave from A natural to A flat
I save the file to 1.mscz
I export the file to 1.musicxml
I quit musescore
I open the file 1.musicxml
m. 77...it's still A natural (whereas 1.musz is A flat)
In reply to Let me show you: 0.xml is a… by drlucas
Converted from PDF with Audiveris.
File 0: Measure 401, staff 2 incomplete. Expected: 2/2; Found: 66/64
In reply to Converted from PDF with… by Shoichi
also confirmed with 3.5RC #270643: [EPIC] MusicXML import/export issues?
In reply to Let me show you: 0.xml is a… by drlucas
File 0.musicxml contains a percussion clef (!) in measure 77, which is invisible after import into MuseScore. I suspect this messes up the accidental calculation on MusicXML export. Corrected file (without the percussion clef) is attached, please check if this fixes the problem.
In reply to File 0.musicxml contains a… by Leon Vinken
Thanks for noticing this. It makes sense now.