POV-Ray : Newsgroups : povray.beta-test : Software version missing in PNG comments : Re: Software version missing in PNG comments Server Time
28 Apr 2024 18:43:31 EDT (-0400)
  Re: Software version missing in PNG comments  
From: Le Forgeron
Date: 18 Jan 2016 04:16:35
Message: <569cad73$1@news.povray.org>
Le 18/01/2016 06:12, clipka a écrit :
> Am 18.01.2016 um 01:19 schrieb Mike Horvath:
>> On 9/18/2013 8:26 PM, Cousin Ricky wrote:
>>> When I open a JPEG image in GIMP, and show Image Properties, I get
>>> something
>>> like:
>>>
>>>     Render Date: 2013-09-19 00:15:52Z
>>>     Software: POV-Ray 3.7.0.RC7
>>>     Platform: x86_64-unknown-linux-gnu
>>>     Compiler: g++ 4.7
>>>
>>> When I do the same with a PNG image, I get something like this:
>>>
>>>     Render Date: 2013-09-19 00:15:16Z
>>>     Platform: x86_64-unknown-linux-gnu
>>>     Compiler: g++ 4.7
>>>
>>> Is this a PNG limitation, an oversight, or something else?
>>> ________________________
>>>
>>> POV-Ray version: 3.7.RC7
>>> Operating System: openSUSE 12.2 Linux
>>> CPU: Dell Inspiron 17R, Intel Core i7
>>
>> I just checked a PNG in version 3.7.0 and it is missing the 'Compiler'
>> flag.
>
> It might be helpful to disclose to us more details about the version of
> POV-Ray you're using - exact version (3.7.0 stable? A later 3.7.0
> version? 3.7.1-whatever?), platform and last not least compiler used to
> build it.
>
> If the compiler version wasn't auto-detected at compile-time, it won't
> be included.
>
>
>> I would like to see more info, such as the amount of time it took
>> to render.
>
> There was a discussion back then about what to put in there and what not.
>
> One result of the discussion was that all file formats that support
> metadata should include the same information, which limits it to 4 lines
> of 40(?) characters each.

IIRC, 4 lines of 80, due to Targa. (and no, 4 lines of 80 is not 320 !)
The comments are 4 lines, but there is other meta-data which can be 
provided with specific tags, or not, according to the format.
and IIRC, Bmp does not even have comments at all.

In fact, according to the format, the 4 lines of comments might have to 
be aggregated in a single comment field.

>
> As for the render time, there was no consensus whether to specifically
> include it, or specifically exclude it.
>
 From my point of view, the render time without the hardware & number of 
thread & core is kind of useless. (actually, the full command line & 
options would be needed, but they won't fit, and selecting which ones to 
put is another story)
Moreover, the render time can be "faked" using a continue.

And is it the CPU time or the wall-clock time that must be used ?

Also, it was not clear which time to report : is parsing part of the 
render, or not.

And it was kind of being painful to retrieve it in a portable way.


Post a reply to this message

Copyright 2003-2023 Persistence of Vision Raytracer Pty. Ltd.