Re: Junk string in ly -> midi -> ly conversion

2016-07-20 Thread Mojca Miklavec
On 20 July 2016 at 18:08, Federico Bruni wrote: > Il giorno mer 20 lug 2016 alle 17:51, Mojca Miklavec ha scritto: >> >> I tried to compile lilypond (2.19.44) from source. And the midi file >> generate with that binary seems OK. >> >> (I'm even more happy that the binary didn't actually crash becau

Re: Junk string in ly -> midi -> ly conversion

2016-07-20 Thread David Kastrup
Federico Bruni writes: > Il giorno mer 20 lug 2016 alle 17:51, Mojca Miklavec > ha scritto: >> I tried to compile lilypond (2.19.44) from source. And the midi file >> generate with that binary seems OK. >> >> (I'm even more happy that the binary didn't actually crash because >> it's compiled aga

Re: Junk string in ly -> midi -> ly conversion

2016-07-20 Thread Federico Bruni
Il giorno mer 20 lug 2016 alle 17:51, Mojca Miklavec ha scritto: I tried to compile lilypond (2.19.44) from source. And the midi file generate with that binary seems OK. (I'm even more happy that the binary didn't actually crash because it's compiled against a different stdlib than its dependen

Re: Junk string in ly -> midi -> ly conversion

2016-07-20 Thread Mojca Miklavec
Just one more data point. I tried to compile lilypond (2.19.44) from source. And the midi file generate with that binary seems OK. (I'm even more happy that the binary didn't actually crash because it's compiled against a different stdlib than its dependencies.) Is it possible that the problem w

Re: Junk string in ly -> midi -> ly conversion

2016-07-20 Thread Mojca Miklavec
On 20 July 2016 at 17:01, Federico Bruni wrote: > Il giorno mer 20 lug 2016 alle 16:50, Mojca Miklavec ha scritto: >> >> If this is a platform-specific problem, can you please: >> - send your midi file for comparison (mine is attached) >> - test whether UTF-8 characters are handled properly during

Re: Junk string in ly -> midi -> ly conversion

2016-07-20 Thread Federico Bruni
Il giorno mer 20 lug 2016 alle 16:50, Mojca Miklavec ha scritto: If this is a platform-specific problem, can you please: - send your midi file for comparison (mine is attached) - test whether UTF-8 characters are handled properly during conversion (I initially thought the problem was in non-asci

Re: Junk string in ly -> midi -> ly conversion

2016-07-20 Thread Mojca Miklavec
On 20 July 2016 at 16:35, Federico Bruni wrote: > Il giorno mer 20 lug 2016 alle 16:14, Mojca Miklavec ha scritto: >> >> I wanted to test the conversion from midi to Lilypond. I took a midi >> file generated with LilyPond, converted it to LilyPond with >> >> >> arch -32 >> /System/Library/Framework

Re: Junk string in ly -> midi -> ly conversion

2016-07-20 Thread Federico Bruni
Il giorno mer 20 lug 2016 alle 16:14, Mojca Miklavec ha scritto: I wanted to test the conversion from midi to Lilypond. I took a midi file generated with LilyPond, converted it to LilyPond with arch -32 /System/Library/Frameworks/Python.framework/Versions/2.7/bin/python /Applications/LilyPon

Junk string in ly -> midi -> ly conversion

2016-07-20 Thread Mojca Miklavec
Hi, I wanted to test the conversion from midi to Lilypond. I took a midi file generated with LilyPond, converted it to LilyPond with arch -32 /System/Library/Frameworks/Python.framework/Versions/2.7/bin/python /Applications/LilyPond.app/Contents/Resources/bin/midi2ly test.midi (I didn't find an