David Kastrup wrote:
- I get correct PDF output on 2.21.0 but a nonsensical wash of bar
checks that appear to cater to 2/4 throughout.
Thanks for testing it, David. What options did you use for midi2ly and
lilypond? My command lines were:
./midi2ly.py -o meter.ly -n -V 1 meter.midi
lilypond meter.ly
I only got one bar check complaint when LP processed meter.ly which
contains:
TrackA = {
\numericTimeSignature\time 4/4 c'4 d'4 e'4 f'4 | % orig
\numericTimeSignature\time 2/4 g'8 a'8 g'8 g'8 a'8 g'8 c''4 | % orig
\numericTimeSignature\time 6/8 c''4 g'8 a'8 g'8 g'8 a'8 g'8 | % orig
\numericTimeSignature\time 2/4 c''4 c''4 r2 | % orig
}
It was on the 6/8 line in the above which contains 8 eighth-notes.
I'll try upgrading to 2.21 and see if that makes any difference.
On Sat, Dec 30, 2017 at 5:15 PM David Kastrup <[email protected]> wrote:
> Michael Ellis <[email protected]> writes:
>
> > Hi, It's been a few years since my last post here. I'm wondering about
> the status of
> > midi2ly. I just tried the version that came with 2.18.2 and it seems to
> handle meter
> > changes incorrectly. Here's a short example produced from a midi file
> imported into
> > MuseScore 2.1
> >
> > msc2-meter-example.png
> >
> > and here's the result of processing what midi2ly produced from the same
> file
> >
> > ly-meter-example.png
> >
> > 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 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.
> >
> > 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.
>
> --
> David Kastrup
>
--
Write music faster with Tbon.
<https://github.com/Michael-F-Ellis/tbon/#tbon>
_______________________________________________
lilypond-user mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/lilypond-user
