You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The TimeSignature object does start at 0, but when I open the MusicXML file in MuseScore, I get it in the middle of the measure, resulting in the two hands not being in sync and the measure containing apparently 8 beats.
Interestingly, it does not fail for every measure, for example, the measure 11 of this piece fails, but the 10 works as expected.
Hi @leleogere Thanks for the issue and code to reproduce it! I can get it to work using a small change in your code and a patch to the export function:
in your code, be sure to instantiate the new part with the same number of quarter divisions as the old one, like so extracted_measure = pt.score.Part(id="measure", quarter_duration = score._quarter_durations[0])
in the export, I disable cost-based merging of attributes, so the time signature and other info are now in the beginning of the exported musicxml measure. This seems to work with musescore, but I don't know whether it'll have any negative consequences in the future. It's just a patch, we might roll it back at some point when we spend some time on export_musicxml.
I'm not sure if it is related to Partitura or MuseScore, but I'm facing weird behavior when I try to extract a part of a score:
Here is the MusicXML rendered by MuseScore:
Here is the list of elements in the partitura
Part
object:The
TimeSignature
object does start at 0, but when I open the MusicXML file in MuseScore, I get it in the middle of the measure, resulting in the two hands not being in sync and the measure containing apparently 8 beats.Interestingly, it does not fail for every measure, for example, the measure 11 of this piece fails, but the 10 works as expected.
You can find the problematic MusicXML here.
Here is the code to reproduce the issue (the measure in question is the measure 11 from Chopin's Etude op10 no12):
The text was updated successfully, but these errors were encountered: