[ANN] midilib 0.8.2

Jim Menard [mailto:jimm@io.com] announced:

midilib is a pure Ruby MIDI library useful for reading and
writing standard MIDI files and manipulating MIDI event data.

The latest version of midilib (0.8.2) can be found on the
midilib Web site (http://midilib.rubyforge.org/\). The midilib
RubyForge project page is http://rubyforge.org/projects/midilib/\.

Wow.
Is it possible for your midi program to convert to lilypond text format
(like midi2ly)?

sorry if stupid request...

kind regards -botp

I didn't write the code, but here is what I think the answer would be.

One could create a rudimentary conversion to lilypond, but there is a
lot that goes into an engraving that is determined by the person doing
it. I suppose you could create rules that determine which tracks get
turned into which staves, but you would still have a lot of manual
editing to do for beams, fermatas; in short, any human interpretation
in the music would require complex AI and still not be foolproof.
Think of things such as changes in tempo and quantization of
imperfectly timed notes..

···

On Thu, 1 Jul 2004 11:13:19 +0900, "Peña, Botp" <botp@delmonte-phil.com> wrote:

Jim Menard [mailto:jimm@io.com] announced:

> midilib is a pure Ruby MIDI library useful for reading and
> writing standard MIDI files and manipulating MIDI event data.
>
> The latest version of midilib (0.8.2) can be found on the
> midilib Web site (http://midilib.rubyforge.org/\). The midilib
> RubyForge project page is http://rubyforge.org/projects/midilib/\.
>

Wow.
Is it possible for your midi program to convert to lilypond text format
(like midi2ly)?

sorry if stupid request...

kind regards -botp

[I've rearranged the conversation so it's top-to-bottom. -- Jim]

Carl Youngblood writes:

···

On Thu, 1 Jul 2004 11:13:19 +0900, "Peña, Botp" <botp@delmonte-phil.com> wrote:
>
> Wow.
> Is it possible for your midi program to convert to lilypond text format
> (like midi2ly)?

I didn't write the code, but here is what I think the answer would be.

One could create a rudimentary conversion to lilypond, but there is a
lot that goes into an engraving that is determined by the person doing
it. I suppose you could create rules that determine which tracks get
turned into which staves, but you would still have a lot of manual
editing to do for beams, fermatas; in short, any human interpretation
in the music would require complex AI and still not be foolproof.
Think of things such as changes in tempo and quantization of
imperfectly timed notes..

Yeah, what Carl said :slight_smile:

MIDI::Track.quantize can perform straight, non-swing quantizing. Ooh, there's
a new feature idea: swing quantizing. Thanks.

Jim
--
Jim Menard, jimm@io.com, http://www.io.com/~jimm/
"Lisp is the red pill."
    -- John Fraser, comp.lang.lisp