Joshua Koo wrote:
1 last point is that i figure out how to play with midi2ly.
1 guess a very import thing is to specify the quantise note durations, if not the generated ly looks really horrible.
depending on the songs, 16 or 32 seems quite good.
then of course, rests will appear as spaces, so any "s" u might change to "r".
another trick i found is like there are certain patterns to solve the conversion mistakes. as i could see, any slight breaks in between notes would be counted as spaces, so u normally have to change ur length and delete the spaces ... for example, 1 crotchet note might appear like this
ais8. s16
actual note is ais4
so just do a search and replace, finding all "8. s16" and replace with 4.
of course there's a possibly that "ais8. s16" might mean "ais8. r16" but it seems chances are ais4 for me.
and there are more troublesomes types like many rests or super long notes,
fis16*37 s16 --> do the maths= fis16*38 = fis4*9.5
divide by the bars = fis4*4 + fis4*4 + fis4* 1.5 =
fis1~| fis ~| fis4~fis8
There seems to be little documentation on midi2ly but i hope in future, this tool can be improve perphaps at least reducing the steps i mention above.
It seems that almost nobody uses midi2ly for any serious job.
To input the music from scratch, writing the .ly file directly
seems to be as quick as using a MIDI keyboard and a sequencer,
especially since you typically spend much more time on the additional
annotations like slurs, dynamics, articulations, ...
The same goes if you want to transfer a score from some other format
via MIDI, since too much of the information is lost.
Therefore, there has never been any incitament to improve midi2ly.
/Mats
_______________________________________________
lilypond-user mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-user
