Summary: | Printing a picture at 5760dpi appears to result in a page at *1* dpi | ||
---|---|---|---|
Product: | [I don't know] kde | Reporter: | Andrew de Quincey <adq_dvb> |
Component: | general | Assignee: | KDEPrint Devel Mailinglist <kde-print-devel> |
Status: | RESOLVED NOT A BUG | ||
Severity: | normal | ||
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Gentoo Packages | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | 1 dpi image produced |
Description
Andrew de Quincey
2005-10-13 22:20:59 UTC
Created attachment 12978 [details]
1 dpi image produced
Its a photo of the statue of Charlemagne outside Notre Dame - heres a link to someone else's photo: http://members.virtualtourist.com/m/p/m/cd5f2/ The colours of the HUGE pixels are roughly what they are if you averaged all the colours in the original photo together from those areas. The image is 4x6 - and you can see there are 4 big pixels by 6 big pixels in the output. Sorry, I chose the wrong product when I submitted this bug - moved to kde-print-devel@kde.org (hope this is ok!) How do you print the picture? I used the latest release of digikam. When printing for real, I print from digikam using the standard kdeprint. That spools to a remote cups server which is running the commerical turboprint drivers. However, the problem also occurs if I ask for a print preview (the screenshot is from the print preview), so I don't _think_ it can be cups/turboprint causing the problem. Also, the file that cups gets to print is *tiny* - say about 17k. Whereas for a dpi that large, you'd expect > 80Mb. BTW, the ppd for that printer is at: http://lidskialf.net/epsonphoto.ppd Wasn't sure if I should attach it to the bug since it has a copyright notice in it. While you are viewing the result in the print preview, could you try to locate the actual temporary file used? It should be located in standard KDE temporary directory, named like kdeprint_xxxxxx. When found, cuold post it here? (Part primarily intended for Cristian) I thought that the regexp in kprinterimpl.cpp was unable to parse the resolution option as found in the PPD file (1440x1440dpi_1), but normally it should be able to do it. So the best is to try the given PPD and track the resolution given to Qt in KPrinter::preparePrinting(). Michael. Actually, I've just upgraded to 3.4.3, and the problem has gone away. The only remaining issue is that the print preview takes several minutes to display the picture 'cos the postscript file is so big, but I don't see how you would solve that, apart from some kind of cunning thumbnail if you're showing a preview. I can live with it. Reporter signals problem not appearing in newer version. |