Sorry if I stepped in a sensitive area, but I mean no disrespect nor even competition. I am just pointing to how things can be done better.
In any case, I forgot to mention that the app's MusicXML export also messes up Take Five, by creating measures that are 6 beats long.
> Very clever work.
Thanks!
> How does your MusicXML output differ from the one generated by the app?
Comparing them manually, they are pretty similar in terms of music output, but here are some differences, from the side of my module:
- It is XSD-compliant with MusicXML 3.1
- It generates...
Thanks Massimo for taking the time to reply and congratulations on creating an amazingly useful application!
I have written an iReal Pro to MusicXML converter, and I had to "reverse-engineer" the chord scheduler to account for the cases I'm looking at. I ended up writing a simple algorithm...
For what it's worth, I'm writing a iReal-to-MusicXML converter (that has different features than the app-provided one) and I am attempting to guess the beat scheduling algorithm.
Thanks! I was able able to "reverse" Take Five by adding 2 empty cells after Bbm7, as per this sheet.
But some experiments with 7/4 went wrong, whereby the player would get confused and end up playing out of time. I understand these are pathological cases, but it does point to some inherent...
I'm not able to fully understand the logic of how empty cells end up specifying chord durations, especially in odd time signatures. For example, in Take Five (5/4) section A, both Ebm and Bbm7 are followed by a single blank cell, but somehow the player translates this to Ebm playing for 3 beats...