Hi,

Okay I've got one for you. What's with the sizing of output directed to a PDF? Following is a small code extract to give you the general idea of what's going on?

import processing.pdf.*;
String urltest = "filenamehere";
PImage img;
void setup(){
   img = loadImage(urltest);
   size(img.width,img.height,PDF,"filetest2.pdf");
   noLoop();
}  // end setup

void draw() {
paintimg();  // CALL THE OUTPUT ROUTINE
exit();
}  // end draw


What happens is as I work with small images and write them to the PDF all is fine. However, when I get to an image that is almost as large as my screen, the resulting image in the PDF seems to be about 35% larger than my screen.

The killer is the picture I really want to process is
2775 x 4463, 72dpi. When I try to open the PDF in Photoshop (which takes almost 2 hours just to get to the rasterize dialog) Photoshop says the picture size is 11563 x 18596 pixels. When I open the PDF in Reader, the PDF is complete and based on the zoom values, it looks like Photoshop is correct on the pixel size.

So why this vast inflation in size which seems to scale up as the raw image grows in size. I tried using images at both 72 and 300dpi but that appears to make no difference.

I tried using two different dpi versions because looking at the difference in size, the output is 4.1668 times larger than the input - a factor that is approximately the same as the factor difference between 72 and 300dpi.


Thanks.

Jim

Hi Ben,

fry wrote on Aug 30^th, 2008, 3:19am:


According to the doc the output is a vector PDF so based on the size and the number of line statements issued, I'm not to surprised at how long it takes PS to open. However, looking at the same PDF in Reader leads me to believe that Adobe is accurately reporting the size.

fry wrote on Aug 30^th, 2008, 3:19am:


Rats. That really dings the usefulness of the height and width fields because that means that before I load any image, I am going to have to go into a separate image app and manually find out what it's dimensions are and manually enter them into Processing. Being able to use the two fields to set size is so much more elegant.

Note in my prior version of the program I didn't use draw() - only setup() and all worked fine except for the sizing issue. I then modded the program to use draw() to see if that would make any difference but it did not.

Just tested placing size() first - it makes no difference in the outcome so I think I'll stick with loading first.

One more test and that will be to just do the draw commands without loading any image to see if that has any impact.

Jim