David Kastrup: > Michael Ellis <michael.f.el...@gmail.com> writes: ... > > The MuseScore output is correct and matches the tempo and meter items > > embedded in the original midi file (attached). I've also verified with 2 > > different > > DAW's (Reaper and Logic X) that the midi file is imported correctly.
The midi file matches your msc2-meter-example.png, I can show you (Michael) a dump if you like. > > The application that produced the midi file is called tbon. It's a > > shorthand notation > > language I wrote for projects where fast notation entry is more important > > than > > having the full capabilities of LilyPond. If you're curious about tbon, go > > to > > https://github.com/Michael-F-Ellis/tbon . The README has a link to a live > > online > > demo. Nice idea to have c--c mean c8. c16 which is much more error prone to type. You could probably change your python program to output lilypond code directly. > > I'd really rather use LP than MuseScore for the times when I want to > > engrave the > > output from tbon since LP still produces better looking scores, imo, but > > not being > > able to handle meter changes is a showstopper. > > I get correct PDF output on 2.21.0 but a nonsensical wash of bar checks > that appear to cater to 2/4 throughout. And here with 2.19.16. The bar checks fails because midi2ly puts in barchecks in the wrong places, don't know why. /// Regarding your subject line question, I don't know. I make my own midi -> ly converter though, currently in an experimental leap... Regards, /Karl Hammar ----------------------------------------------------------------------- Aspö Data Lilla Aspö 148 S-742 94 Östhammar Sweden +46 173 140 57 _______________________________________________ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
