Make use of Lilypond

[ramondelafuente]

We should really go from our formatter to Lilypond, that removes any responsability to draw any notes ourselves.

[mvriel]

That looks sweet! Then the only thing you need to do is write a converter from interpreted MIDI to that text-based format of Lilypond

[ramondelafuente]

Found some perl scripts that do that (actually in apt, and also referred to in Lilypond documentation), but maybe our domain expert @genesislive2007 could chip in with his opinion ;-)

[cgoosey1]

Ha my research at the beginning of the week revealed this software, I think i mostly glossed over it as we wanted to build it in an application

[ramondelafuente]

I knew someone mentioned lilypond to me last week - now I remember! Dammit, a missed opportunity there :-)

[ramondelafuente]

He was ON MY OWN FRICKIN' TEAM! *grin*

[cgoosey1]

lol we all gave it the same look at the time!

Wow! Lilypond seems to be the final solution! Isn't it?
The manual is soo extensive, and I think it can handle all the features implemented into the MIDI format, and probably more.
If kotta will use this awesome tool, it cannot be deployed in shared hosting, or other system without extensive permissions right?
I'm just wandering about the deployment process. Can a compiled software such as Lilypond be part of the provisioning process of the ours stack? I'm trying to compile it from source and seems that it needs a lots of deps...
Anyway for me +1 for the usage of this tool!

[ramondelafuente]

it's in apt... apt-get install lilypond
I'll add it to the provisioning.

(it does seem to install every single other package in APT as a dependency ;-) )

Awesome @ramondelafuente!

The flow could be:

1. MIDI file handeling
2. Parsing with midiparser
3. Convert the MIDI data into human format to have a nice in-memory representation
4. Lilypond file generation
5. Fire up Lilypond
6. Grab a beer (if the Steves beer keeps overflowing...that's what she said #11 will be resolved!)

The tricky part now is limited to the step 3