Crash when paper size too large? #13
Comments
|
More info: I have the resolution set to 600, and am generating PNGs. From your code, I pulled the arguments and manually ran which generated a PNG with a file size of 1,017,890 bytes. If I use the default resolution (leaving the However, running it through Sphinx using the Lilypond extension, it generates a 115-byte stub of a PNG: |
|
I am quite busy recently, will dig it this week :D |
|
Take your time. I am not in any rush. I've switched to SVGs (and filed a bug about cropping). If you need me to switch back to PNGs (or send you the file that killed the extension) let me know. |
|
Hi @kjcole, I use the following rst source, and set .. lily::
:noedge:
:noedge:
\version "2.20.0"
\language "english"
% A4 = 210 mm * 297 mm
#(set! paper-alist
(cons '("long scroll" . (cons (* 210 ) (* 440 mm))) paper-alist))
\paper {
#(set-paper-size "long scroll")
}
\header {
title = "翼をください, Excerpts"
}
\score {
<<
\new Staff \relative c' {
\time 4/4
\tempo 4 = 70
r4 r r c8 d e8 e f16 e8 d16 (d4) e8 d
c8 c d16 c8 b16 (b4) b8 g a4 c8 a g4 c4
d4 r r r
}
>>
} |
|
I've recently upgraded to Pop!_OS 22.04 LTS. This moved me from Python 3.8 to Python 3.10 and from LilyPond 2.20.0 to LilyPond 2.22.1. (It also changed a lot of other applications and libraries.) I also found a better way to eliminate page-breaks. See the small patch in changes.txt After downloading, remove the And from I just ran it again after the major distribution release upgrade. The console log is:
|
|
Any progress? |
|
Sorry, not yet, I will take a look this week. |
|
No rush. Just checking back. |
|
This song is beautiful :D but I still can not reproduce it :( What is your version of imagemagick? I am using 7.1.0.41. |
@kjcole I don't know what is "stub of PNG"? |
|
Hi @kjcole, can you tell me your ImageMagick version? |
|
What I meant by a stub of a PNG: It generated a file, and the first few bytes identify it as a PNG but after the header that identifies the image format, there is no data. Like a template with no content. It looks like I'm using an older version of ImageMagick. Version: ImageMagick 6.9.11-60 Q16 x86_64 2021-01-25 (dpkg says, specifically "8:6.9.11.60+dfsg-1.3build2") |
|
I will try your ImageMagick version. |
|
It has taken me some time to get back to testing. This morning, I compiled the whole book again, and it successfully generated all the PNGs. So, either you fixed the problem, or some upgrade of something else fixed the problem. Probably a bit of both. Thanks. (Before trying the PNGs, my conf.py was still set to SVGs, which now don't crop but were seriously degraded in quality. However, I'm happy with the PNGs. As long as I tell Lilypond that the paper is of "infinite length" I don't run into the badly scaled page problem.) |
|
I spoke too soon: I had left the |
#18 improved the quality of cropped SVG, have you tried it? |
|
Yes. I tried the SVG patch. See the console log below and the attached screenshot showing the seriously degraded SVG. (All of the SVGs are bad.)
|
|
I've attached the actual SVG generated from the above here: |
|
This is so weird, this issue should be fixed exactly :'( |
|
Well, thanks for trying. I'm not in a hurry, and I'm thinking about work-arounds. For example, with The Hundred Pipers, I commented out the additional verses from the LilyPond file and put them in the reStructuredText file. That made the generated PNG much smaller, an so the plugin didn't complain. (I'd still prefer to have the lyrics stay with the LilyPond file, but the solution works okay for now.) |
|
I will drop ImageMagick (#32) in the 2.0, then this problem should be fixed (again Q_Q). |
|
Hi @kjcole, can you please try again with 2.0.0 when you are free? so I can close this issue :D |
|
What's the best way to install locally? I tried |
|
Just use |
|
|
Ohh, so sorry, I forgot to push it PyPI. Please wait a minute and I will do that. |
|
You can try |
|
And there are some breaking changes, you no longer need write a lot of options. for example: 1.x: .. lilyinclude:: ./hundred_pipers.ly
:nofooter:
:noedge:
:audio:
:controls: top2.x: .. lilyinclude:: ./hundred_pipers.ly
:controls: top |
|
It appears to be working now. Thanks. |
In order to make scores stay in a single file, I have been adding the following to the top of my Lilypond files:
I increase the value of
???above until the entire score fits in a single page. This has worked fine with values up to 371, but today I had one that needed 440 and the build blew up with:sphinx-err-hj4x9frp.log
The text was updated successfully, but these errors were encountered: