Bug 688516 - Grayscale image lost at 300 dpi
Summary: Grayscale image lost at 300 dpi
Status: RESOLVED DUPLICATE of bug 493348
Alias: None
Product: Ghostscript
Classification: Unclassified
Component: Graphics Library (show other bugs)
Version: 8.53
Hardware: PC Windows XP
: P4 major
Assignee: Stefan Kemper
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-01-27 11:35 UTC by Franjo
Modified: 2007-12-13 12:55 UTC (History)
0 users

See Also:
Customer:
Word Size: ---

Attachments
input file (22.87 KB, application/pdf)
2006-01-27 11:35 UTC, Franjo 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Franjo 2006-01-27 11:35:06 UTC 
using the following command line:

gswin32c -sDEVICE=jpeg -sOutputFile=c:\temp\print\res1.jpg -q -dBATCH -r300
-dNOPAUSE  c:\temp\nem.pdf

the result is BLANK jpg file. It is the same with tiffgray and tiffg4 driver
too. 72, 200 or 600 dpi results look ok. With 301 resolution I got ugly big
black and white squares ?!
Comment 1 Franjo 2006-01-27 11:35:33 UTC 
Created attachment 1957 [details]
input file
Comment 2 Alex Cherepanov 2006-01-28 17:24:09 UTC 
The sample file contains a single halftoned image.

q 0.24 0 0 0.24 0 0 cm
/R7 gs
q 0 1054.5 -2250 0 2400 150.004 cm
BI
/CS/G
/W 2109
/H 4500
/BPC 8
/F/Fl
/DP<</Predictor 15
/Columns 2109>>
ID
....
EI

When the image is subsampled the results depend on the relative phases of
the halftone cells on the inage and the sampling function. For instance, 
the inage looks great at 600 dpi.
Comment 3 Ray Johnston 2006-02-01 09:47:11 UTC 
-dDOINTERPOLATE allows this to work. 
 
THis is similar to bug 493348. 
 
Since this workaround lets it work and we already have an open bug, we 
will mark this as a duplicate. 

*** This bug has been marked as a duplicate of 493348 ***