in the latest 2.15 version
Thank you. Then, how to report this bug? My score is too big to find the real
culprit, but this problem is a regression since 2.15.xx (I can't remember).
Regards
Ha
Thank you. Then, how to report this bug? My score is too big to find the real
culprit, but this problem is a regression since 2.15.xx (I can't remember).
Regards
Haipeng
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailm
On 24 February 2012 11:44, Colin Hall wrote:
>
> On Fri, Feb 24, 2012 at 07:37:55PM +0800, hhpmusic wrote:
>> I tried again on my Win7 64 machine, which has Intel I5 processor and 16GB
>> RAM for midi sequencing. The problem persists. Strange!
>
> Send whatever output you have.
Haipeng's score s
I gather from your description that your file is causing lilypond to crash a
certain number of measures into the piece due to temporarily added staves? I
have had a similar problem.
On Thursday, February 23, 2012 03:40:54 PM 胡海鹏 - Hu Haipeng wrote:
> Hello,
> I'm extremely busy, but I have to
Hi Haipeng,
2012/2/24 hhpmusic :
> Thank you, just received. I reinstalled 2.14.2 and compiled the score
> successfully.
As a temporary fix, you can remove the Span_bar_stub_engraver by
adding the following to your \layout block:
\context {
\GrandStaff
\remove "Span_bar_stub_engraver"
}
C
胡海鹏 - Hu Haipeng writes:
> Hello,
> I'm extremely busy, but I have to report the bad news that LP still
> haven't solved this problem. It's not so easy for me to reduce the
> file, but you'll find lp unexpectly aborts at bar 240. I remember it
> ever aborts at bar 160-168, due to temporarily ad
Thank you, just received. I reinstalled 2.14.2 and compiled the score
successfully.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
I tried again on my Win7 64 machine, which has Intel I5 processor and 16GB RAM
for midi sequencing. The problem persists. Strange!
Haipeng
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
On Fri, Feb 24, 2012 at 07:37:55PM +0800, hhpmusic wrote:
> I tried again on my Win7 64 machine, which has Intel I5 processor and 16GB
> RAM for midi sequencing. The problem persists. Strange!
Send whatever output you have.
I'll send the score and midi generated on my machine to you by private
On Fri, Feb 24, 2012 at 10:48:07AM +0800, hhpmusic wrote:
> I remember someone replied me at this list, not bug list.
Yep, found a few threads going back to December 2011:
http://lists.gnu.org/archive/html/lilypond-user/2011-12/msg00675.html
http://lists.gnu.org/archive/html/lilypond-user/2011-
I remember someone replied me at this list, not bug list. I'm running Win xp
and 7 64 bit (two machines), Lilypond 2.15.30
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
On Fri, Feb 24, 2012 at 07:40:54AM +0800, 胡海鹏 - Hu Haipeng wrote:
> I have to report the bad news that LP still haven't solved this problem.
Please send a link to any previous discussions of this problem. Was this
reported to Lilypond bug-reports.
> It's not so easy for me to reduce the file, b
Hello,
I'm extremely busy, but I have to report the bad news that LP still haven't
solved this problem. It's not so easy for me to reduce the file, but you'll
find lp unexpectly aborts at bar 240. I remember it ever aborts at bar 160-168,
due to temporarily added staves. What's the current err
13 matches
Mail list logo
