GraphicsExportSetResolution error

[Jedidja Bourgeois]

Hey

Has anyone tried setting the output dpi (resolution) using
GraphicsExportSetResolution? If i call it as such:

Fixed dpi = Long2Fix(96);
GraphicsExportSetResolution(compInst, dpi, dpi);

and then open the file in Photoshop (or get info under XP), it shows
up as 95.987 and 95 respectively.

Is this normal behaviour for Quicktime? I tried saving an image out
using Quicktime Pro but it doesn't seem to let you set the DPI in the
configuration dialog.

TIA

[Mike Kluev]

In Article [email]b4b8c5a0.0308080659.3e1d8a38@posting.google.com[/email], Jedidja
Bourgeois wrote:

> Has anyone tried setting the output dpi (resolution) using
> GraphicsExportSetResolution? If i call it as such:
>
> Fixed dpi = Long2Fix(96);
> GraphicsExportSetResolution(compInst, dpi, dpi);
>
> and then open the file in Photoshop (or get info under XP), it shows
> up as 95.987 and 95 respectively.
>
> Is this normal behaviour for Quicktime? I tried saving an image out
> using Quicktime Pro but it doesn't seem to let you set the DPI in the
> configuration dialog.

What are dimensions of image in pixels? I guess they are too small,
and this is triggered by some rounding error. Try your code with
large image (like 1000 by 1000 pixels).

--
Mike Kluev

PS. Remove "-DELETE-." part of my e-mail address to reply.

[Jedidja Bourgeois]

> What are dimensions of image in pixels? I guess they are too small,

> and this is triggered by some rounding error. Try your code with
> large image (like 1000 by 1000 pixels).

Why would dpi have any relation to the size of the image? It has no
real bearing on the pixel data, just a flag for programs that need to
size the image for output (eg print) right? It does appear to be
rounding problems, yes, if I pass in 96.2 for instance, it shows up at
96.012 in Photoshop. Very odd...

[Thomas Engelmeier]

In article <b4b8c5a0.0308090723.3a366a58@posting.google.com >,
[email]jedidjab79@hotmail.com[/email] (Jedidja Bourgeois) wrote:

> > What are dimensions of image in pixels? I guess they are too small,
> > and this is triggered by some rounding error. Try your code with
> > large image (like 1000 by 1000 pixels).

>
> Why would dpi have any relation to the size of the image? It has no
> real bearing on the pixel data, just a flag for programs that need to
> size the image for output (eg print) right? It does appear to be
> rounding problems, yes, if I pass in 96.2 for instance, it shows up at
> 96.012 in Photoshop. Very odd...

In order to display 10 pixels of 96 dpi data (=.104166666... inch) on an
72 dpi system you need (7 or) 8 pixels = .111111... inch.

10 (original) pixels displayed within .111111... (real screen space)
inch give an resolution of 90.000 +- rounding dpi.

Ditto, if you convert an .104166666 inch wide 72 dpi image to 96 dpi
("preserving" dimensions), you will get the rounding error and an scaled
image..

Regards,
Tom_E

[Mike Kluev]

In Article bh37j8$tqtdb$1@ID-2640.news.uni-berlin.de, Thomas Engelmeier
wrote:

> In article <b4b8c5a0.0308090723.3a366a58@posting.google.com >,
> [email]jedidjab79@hotmail.com[/email] (Jedidja Bourgeois) wrote:
>

>>> What are dimensions of image in pixels? I guess they are too small,
>>> and this is triggered by some rounding error. Try your code with
>>> large image (like 1000 by 1000 pixels).

>>
>> Why would dpi have any relation to the size of the image? It has no
>> real bearing on the pixel data, just a flag for programs that need to
>> size the image for output (eg print) right? It does appear to be
>> rounding problems, yes, if I pass in 96.2 for instance, it shows up at
>> 96.012 in Photoshop. Very odd...

>
> In order to display 10 pixels of 96 dpi data (=.104166666... inch) on an
> 72 dpi system you need (7 or) 8 pixels = .111111... inch.
>
> 10 (original) pixels displayed within .111111... (real screen space)
> inch give an resolution of 90.000 +- rounding dpi.
>
> Ditto, if you convert an .104166666 inch wide 72 dpi image to 96 dpi
> ("preserving" dimensions), you will get the rounding error and an scaled
> image..

I would add to what Thomas said. The problem might be that Photoshop
might not show dpi stored in the image. Instead it might recalculate
it using pixelCount/imageSizeInInches formula. And it might round
imageSizeInInches to be representable in whole points (1/72 inches).
That's why I suggested you to try your code with big image and see
if the problem disappears.

--
Mike Kluev

PS. Remove "-DELETE-." part of my e-mail address to reply.

[Jedidja Bourgeois]

Unfortunately I've tried 500x500, 1000x1000, 1500x1500 and nothing
seems to change. The QT docs specifically mention that when you
convert 72 (long) to a Fixed, it should be 0x00480000, which is the
value i'm passing GraphicsExportSetResolution(). I find it a bit
strange that both Photoshop and Explorer XP would then go ahead and
disregard this value, but it seems to be what's happening. Exporting a
picture from Photoshop produces a file with the correct DPI in both
Photoshop and XP, so perhaps there's an extra tag or something that
Quicktime doesn't fill in?

[Jedidja Bourgeois]

Allright we figured it out. It's only with PNG files exported using
Quicktime that there is an issue. Using the reference library fixes
the problem. If you export TIFF or something else, the numbers come
out correctly. It has to do with the way PNG stores dpi internally.

[Mike Kluev]

In Article [email]b4b8c5a0.0308110835.fc55f7c@posting.google.com[/email], Jedidja Bourgeois
wrote:

> Allright we figured it out. It's only with PNG files exported using
> Quicktime that there is an issue. Using the reference library fixes
> the problem. If you export TIFF or something else, the numbers come
> out correctly. It has to do with the way PNG stores dpi internally.

What is "reference library" and what was the fix? The rest of us will
appreciate to know.

--
Mike Kluev

PS. Remove "-DELETE-." part of my e-mail address to reply.

[Thomas Engelmeier]

In article <b4b8c5a0.0308110835.fc55f7c@posting.google.com> ,
[email]jedidjab79@hotmail.com[/email] (Jedidja Bourgeois) wrote:

> It's only with PNG files exported using
> Quicktime that there is an issue. Using the reference library fixes
> the problem.

File an bug report ;)

Regards,
Tom"news:microsoft.test in the FUp´ removed"E

[Thomas Engelmeier]

In article <BB5E06C9.15302%mike@objc-source.-DELETE-.org>,
Mike Kluev <mike@objc-source.-DELETE-.org> wrote:

> > Allright we figured it out. It's only with PNG files exported using
> > Quicktime that there is an issue. Using the reference library fixes
> > the problem. If you export TIFF or something else, the numbers come
> > out correctly. It has to do with the way PNG stores dpi internally.

>
> What is "reference library" and what was the fix? The rest of us will
> appreciate to know.

<http://www.libpng.org/>

Regards,
Tom_E