re: LilyPond 2.13.9 released

2009-12-12 Thread 胡海鹏 - Hu Haipeng
Sorry, Since the bad frustrating Midi tie problem persists, I have to roll back to 2.13.7, and wait for a version with fixed tie playback. Haipeng ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: LilyPond 2.13.9 released

2009-12-12 Thread Graham Percival
As mentioned in the release message, users are strongly recommended to use 2.12.2, not 2.13. We will let you know when we think that 2.13.x is ready for users to test. Cheers, - Graham 2009/12/12 胡海鹏 - Hu Haipeng : > Sorry, Since the bad frustrating Midi tie problem persists, I have to roll > ba

Re: LilyPond 2.13.9 released

2009-12-12 Thread Werner LEMBERG
> Sorry, Since the bad frustrating Midi tie problem persists, I have > to roll back to 2.13.7, and wait for a version with fixed tie > playback. I second this: This belongs to the non-existent bug category `annoying' :-) Seriously: It should be fixed ASAP, or please revert to the old behaviour.

Re: LilyPond 2.13.9 released

2009-12-12 Thread Reinhold Kainhofer
Am Samstag, 12. Dezember 2009 17:34:36 schrieb Werner LEMBERG: > > Sorry, Since the bad frustrating Midi tie problem persists, I have > > to roll back to 2.13.7, and wait for a version with fixed tie > > playback. > > I second this: This belongs to the non-existent bug category > `annoying' :-) >

Re: LilyPond 2.13.9 released

2009-12-12 Thread Nick Payne
I downloaded the 2.13.9 documentation and extracted the PDFs. I notice that in web.pdf, most of the graphics are rendered too large and run off the edge of the page... Nick ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/ma

Need help with Memory Corruption [Was: Re: LilyPond 2.13.9 released]

2009-12-12 Thread Reinhold Kainhofer
Am Samstag, 12. Dezember 2009 15:43:37 schrieb 胡海鹏 - Hu Haipeng: > Sorry, Since the bad frustrating Midi tie problem persists, I have to roll > back to 2.13.7, and wait for a version with fixed tie playback. I've tried to fix the bug, but I'm always running into memory corruption issues, and I h