Graham,
Thanks for your reply. I wrote a small example based on the midi2ly output.
This small example can be converted to lilypond file with respect to the
"key" command line option. Now the "\transpose cis c" works as expected and
I get plain C major notation.
But this fails with the MIDI file. This is very strange.
The example is huge, I must admit. So I want to contribute...
midi2ly is a python script. Since python is a script language, I should be
able to debug it. I have a little experience with python, so I tried it with
this command line:
python -d C:\Programme\LilyPond\usr\bin\midi2ly.py --key=0:1 LastUnicorn.mid
But python doesn’t respect the -d and just runs the script:
LY output to `.\LastUnicorn-midi.ly'...
Can you advise me how to investigate/debug midi2ly by myself?
Best Regards,
Helge
-----Ursprüngliche Nachricht-----
Von: Graham Percival [mailto:address@hidden
Gesendet: Donnerstag, 28. Dezember 2006 10:37
An: Helge Kruse; 'Lilypond bug'
Betreff: Re: AW: midi2ly key and rests
Helge Kruse wrote:
There is no attachment on THIS mail, since the web interface did not
offer
to include files. I am not member of the bug mailing list. Therefore I
hope
it's ok to send it to you.
There was no attachment to the previous email, either.
http://lists.gnu.org/archive/html/lilypond-user/2006-12/msg00784.html
Unfortunately it's a complete song with much more than five notes. But
the
problems remain.
Unfortunately we do not have the resources to investigate bug reports
which have huge examples. Could you create a small example (perhaps
using lilypond's midi capability) that demonstrates the problem with
midi2ly? A lilypond -> midi -> failured midi2ly example would be very
useful.
- Graham