|
| From: | lilypond |
| Subject: | Re: [Lilypond-auto] Issue 2658 in lilypond: wrong stem rendering (inconsistent thickness) |
| Date: | Tue, 16 Apr 2013 15:31:45 +0000 |
Comment #27 on issue 2658 by address@hidden: wrong stem rendering (inconsistent thickness)
http://code.google.com/p/lilypond/issues/detail?id=2658Huh. The "nice look" version is actually cheaper to get back than I thought. I just need to replace "stroke" with "strokepath fill newpath" everywhere relevant.
The disconcerting thing is that both are supposed to be quite the same. Presumably Ghostscript's antialiasing algorithm works "better" with stroke.
Holy moley: just by replacing in scm/ps-to-png.scm the argument -dGraphicsAlphaBits=4 with the (quite faster) -dGraphicsAlphaBits=1, the PNGs make a large jump upwards in quality. Of course not entirely without drawbacks: things like circles (like in string numbers) get rendered without antialiasing as well and get quite scrawny.
So this should give me a hook for getting PNG in nice quality. I just need to decide which of the drawing primitives should come with a "no antialiasing, please" implementation.
--You received this message because this project is configured to send all issue notifications to this address.
You may adjust your notification preferences at: https://code.google.com/hosting/settings
| [Prev in Thread] | Current Thread | [Next in Thread] |