Bug 46880 - Bitmap aliasing and coordinates precision
Summary: Bitmap aliasing and coordinates precision
Status: RESOLVED MOVED
Alias: None
Product: poppler
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
Hardware: Other Mac OS X (All)
: medium normal
Assignee: poppler-bugs
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-03-02 01:51 UTC by Jorge Hernández Valiñani
Modified: 2018-08-21 10:37 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
PDF with bitmap aliasing and object placement inaccuracies. (1.05 MB, application/pdf)
2012-03-02 01:51 UTC, Jorge Hernández Valiñani
Details
Rendered sample with notes pointing out rendering inaccuracies. (893.60 KB, image/jpeg)
2012-03-02 01:56 UTC, Jorge Hernández Valiñani
Details
Rendered sample (with Photoshop; void of artifacts) (698.67 KB, image/jpeg)
2012-04-26 15:03 UTC, Jorge Hernández Valiñani
Details

Description Jorge Hernández Valiñani 2012-03-02 01:51:45 UTC
Created attachment 57904 [details]
PDF with bitmap aliasing and object placement inaccuracies.

(Note: I only know how to install Macports version, today 0.18.2; I do not know if this happens in a later version)

The following PDF has two problems when rendered with `pdftoppm`:

    pdftoppm -r 159 -f 27 -l 27 -tiff sample.pdf > output.tiff

1. Either the rendered bitmaps have aliasing problems or the output has some horizontal lines missing.

2. The placement of one bitmap layer (top black ink) with respect to the other one (bottom color) is inaccurate. As a result color seems displaced.

See embedded "output(pdftoppm).jpg" pointing out areas where this happens.

Rendering with `pdftocairo` provides no bitmap antialias whatsoever (which I would consider a bug too), so it makes it difficult to see whether the two bugs above happen or not too.

None of these issues happen when rendering with Acrobat X (i.e. Acrobat renders this PDF flawlessly).
Comment 1 Jorge Hernández Valiñani 2012-03-02 01:56:39 UTC
Created attachment 57905 [details]
Rendered sample with notes pointing out rendering inaccuracies.
Comment 2 Jorge Hernández Valiñani 2012-03-02 02:30:57 UTC
Oops, the correct `pdftoppm` command-line is:

    pdftoppm -r 159 -tiff sample.pdf > output.tiff
Comment 3 Jorge Hernández Valiñani 2012-04-03 08:34:47 UTC
pdftocairo equally has problems with this PDF, albeit showing up differently: no antialias whatsoever is applied to the bitmaps.
Comment 4 Thomas Freitag 2012-04-26 05:56:52 UTC
Rendering it with actual master, rendered with 150 dpi, is better than the attached rendered sample. But it will never be comparable with output of Acrobat: one of the biggest difference between poppler and acrobat is, that with poppler You render it with a given resolution and then see a bitmap, and when You zoom that bitmap You begin to see pixel. When You zoom with acrobat, it renders it always again considering the zoom factor and viewable section.
So pdftoppm will never be a "viewer" in the meaning of interactive zooming. That can only done by a "windows" program using the poppler library!
Comment 5 Jorge Hernández Valiñani 2012-04-26 15:03:21 UTC
Created attachment 60639 [details]
Rendered sample (with Photoshop; void of artifacts)

I think you missed my points. I never talked about zooming:

1) I was pointing in the rendered sample to specific artifacts: there seem to be specific lines causing a staircase effect, and it is **not** a problem of poor antialiasing, as well as poor alignment of layers.

2) Those artifacts do not appear on Acrobat **when rendering at exactly the same resolution**. They appear in pdftoppm's version but not Acrobat's **at exactly the same ppi resolution**. I am aware that zooming in Acrobat would re-render the page at higher ppi, but that is not what I was talking about.

Please open the rendered sample and observe the artifacts. Here I attach another rendered sample, at exactly the same resolution (159) rendered with Photoshop 12.1 (CS5.5), which renders similar to Acrobat and do not present those artifacts.
Comment 6 GitLab Migration User 2018-08-21 10:37:43 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/poppler/poppler/issues/295.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.