Closed saintmatthieu closed 2 years ago
Thanks for the report.
Your file parses fine before that be36eb206613ba51bcb91c88525e772e88ec7efb, in which it looks like I introduced the possibility of deleting while iterating. But in testing a trivial fix I found we weren't safely getting the correct offsets for meter changes anyway, so this has probably been a problem since somewhere in the version 6 series. Will PR in a minute.
Glad it was addressed and merged so fast. Now when will it be released? Current v7.1.0
is almost half a year old 🕸️
Glad it was addressed and merged so fast. Now when will it be released? Current
v7.1.0
is almost half a year old 🕸️
when we have time. It's a volunteer project.
Sorry, I didn't realise it was more than pressing a button. ☮️
music21 version
7.1.0
Problem summary
Time signature changes are not exported to MIDI, at least not when the data is imported from MusicXML. (The MusicXML import might actually be at fault here, but I guess not.)
Steps to reproduce
Using the xml snippet in the More information section as
input.musicxml
(here as PDF), runExpected vs. actual behavior
Time signature changes should be present in the MIDI output file (as time signature events) ; they are not, the only time signature event is at tick 0 and has the value of the first time signature of the score.
More information