The Persistence of Vision Raytracer (POV-Ray).

This is the legacy Bug Tracking System for the POV-Ray project. Bugs listed here are being migrated to our github issue tracker. Please refer to that for new reports or updates to existing ones on this system.

Attached to Project: POV-Ray
Opened by Mike H - 2009-11-06
Last edited by Chris Cason - 2010-12-31

FS#64 - Add "POV-Ray" metatags to images

Add metatags to output images identifying the file as having been created using POV-Ray.

Closed by  Chris Cason
Friday, 31 December 2010, 14:37 GMT
Reason for closing:  Implemented
Christoph Lipka commented on Saturday, 07 November 2009, 15:55 GMT

I'd advocate a few more metadata items in addition:

  • creation date/time
  • render time
  • maybe system information

As this metadata would increase file size, which a user may prefer to cut down on, and also disclose information the user may not want disclosed, the generation of this metadata should be governed by a command-line / INI-file switch, defaulting to "off".

For PNG images, the information should probably go in tEXt (or iTXt) chunks, using the following keywords:

  • "Software": "POV-Ray" followed by the version number (and possibly compiler/architecture information as shown at startup)
  • "Creation Time": current date/time of image output * "Source":
  • "Source": Hardware on which the render was performed (if such information is available)
  • (TBD): "Wall-clock" render time
Grimbert Jérôme commented on Friday, 01 January 2010, 11:16 GMT

It might also be interesting to get inside the image the whole set of options used to generate the image (such as AA, MB, and other renders settings)
Can be omitted : Library paths, input & output path, ini file, io-restrictions...
Purpose: being able to separate the draft render from the final one (is it AA=0.01 or just AA=0.3 ?). And eventually to replay it. Paths are not portable across systems/computers, so no need to provide that informations

Regarding the hardware & wall-clock: i do not find them useful. You cannot know if povray was not sharing the CPU with another big cruncher. And extracting hardware information might be non-portable & painful.
(Additionaly, what about a fake inside a Virtual Machine ? might turns out as a "proof" of very bad performance for povray. Not the kind of publicity one might wants.)

Grimbert Jérôme commented on Sunday, 21 March 2010, 14:46 GMT

Preliminary test for png: creation time is done automatically as create-date, as well as modify-date
Of usable keywords (as registered, but specification seems open), Software & Comment are usable.
Software can get PACKAGE_STRING directly, Comment could be multiline.

For compatibility issue with libpng 1.2, I would recommend to AVOID iTXT (unless writing a smart #ifdef'ed code), even if it cost us to stay in ascii instead of utf-8.

In png.cpp :

static png_text p_text[]= {
{-1,"Comment", DISTRIBUTION_MESSAGE_2 "\n"
static int num_text =sizeof(p_text)/sizeof(png_text);
static png_textp text_ptr=&p_text[0];

End of the write function:

  if (messages.error.length() > 0)
    throw messages.error.c_str();

  for(int j=num_text;j;j--)
  png_set_text(png_ptr, info_ptr, text_ptr, num_text);
  png_write_end(png_ptr, info_ptr);
  png_destroy_write_struct(&png_ptr, &info_ptr);

Grimbert Jérôme commented on Thursday, 17 June 2010, 11:01 GMT

More requests in  FS#134 

Mike H commented on Sunday, 20 June 2010, 00:02 GMT

Would also like an option (disableable) to render some of this info onto the image itself.

Mike H commented on Saturday, 21 August 2010, 22:39 GMT

"It might also be interesting to get inside the image the whole set of options used to generate the image"

Great idea!

Grimbert Jérôme commented on Friday, 27 August 2010, 09:03 GMT

For information, I made a summary of the possible image file format & metadata supports (at least the ones supported by povray)

There is no way for BMP (+FS window) to have metadata.
Other formats allow metadata, in one form or another.

It might be time to focus on the content we want inside the metadata.

(investigating hdr: there is already a line
SOFTWARE=Persistence of Vision Raytracer v3.7.0.beta.38

Grimbert Jérôme commented on Tuesday, 31 August 2010, 21:09 GMT

After deeper analysis off the various supported file output, here come my proposal (code to be provided if nobody objects whenever I get the energy and time... as for weddings, speak now or remain silent...)
(well, until I actually code something, you have plenty of time... and code can be rejected too)

  1. BMP won't get any (there is no room for that)

Metadata would consist of, only in ASCII (low range, 32-126):

  • Software name, up to 40 bytes
  • Software version, as a short (with major as short/100, minor short%100) and a letter. (a string presentation might be substituted according to the output format, but the information is basically "XX.YY c"
  • Date & Time of creation (from local clock, from year on 4 digits to second)
  • 4 consecutive lines of up to 80 bytes each (what you want in these lines is still opened to discussion)

Mandatory evolution of file format: Targa must evolve from version 1 to version 2 (adding a 26 bytes footer, and a 498 bytes extension area)

Rational for this proposal:

  • Jpeg will get all the metadata in marker JPEG_COM, as one string (support upto 65535 bytes), with local line feed to separate the metadata and label inside the text to introduce each pieces of information.
  • Exif is NOT used for Jpeg (it's far too complex: marker APP1 must be right after SOI marker, and then a lot of structures must be pushed to provide mainly numeric-only data that are unavailable from a raytracer)
  • PNG: Sofware & Version (as text) get into Software key, Date & time are automatically done by the libpng, remaining goes in the Comment key (as concatenation with line feed)
  • PPM: Everything is dumped as many comment lines (# ), introduced with label similar to the jpeg one; Max length of a line is 1024
  • Openexr : Everything goes into the header, the version is textual: Comments, Software, Date & Time
  • hdr (Radiance .pic format in fact) : SOFTWARE= is already present (might be updated), multiples lines of COMMENT= should be ok, DATE= & TIME= also (the header is ended by an empty line)
  • targa (compressed or not): In version 1, metadata is way too short, only the ID area could be used (but its purpose is to identify the picture, not its making, and it's ascii and at most 255 bytes). Version 2 provides the Extension area, which gives a lot of fields.

The stronger constraint come from the targa fields: they are fixed size, with mandatory 0 at fixed places, and padding with nulls or spaces is required when not meaningful.
It's where the 40 & 80 limits (as well as 4 lines) come from.
There is a possibility to put in targa a developper area, but we better do not. (it won't be accessible from other programs)

There is other fields in targa Extension area, but mapping them into png seems a bit gross (in fact, short of Software & Comment, the standardisation for png's keys is an enigma).
If you have a particular battle-horse field from Targa you want as metadata, please suggest the PNG mapping (as other files format would just have "some text")

Please notice, the proposal is for 4 lines of 80 chars, it is not exactly the same as 320 chars.

Final note: we have an issue with the version numbering, at least for beta... how can it be solved ?

Specification of Targa (1991)

Chris Cason commented on Wednesday, 01 September 2010, 00:12 GMT

Despite my attachment to it (targa being the main format we used back in the old days of POV), I am not sure if it even really matters if we don't add metadata to the TGA output. I really don't think many people will use it anymore, and if it's forcing constraints onto the other image metadata, then we could just leave metadata support for it out.

Grimbert Jérôme commented on Thursday, 02 September 2010, 19:34 GMT

Don't worry for targa... it now write version 2 file (and hopefully, I got the right gamma value)

Here come a tar of updated files (+one new include) to have metadata in all but one output file format (the missing one is BMP, which does not allow them).
hdr, jpeg, openexr, png, ppm & targa.
The files go in source/base/image

The content of meta data is defined in metadata.h (a class that I'm not very happy with, the constructor is worthless, all functions are statics)
The Version field in targa is not used, the software identification string contains it.

You get Software, 4 comment lines (which are truncated to 80 only for targa) and the current time (when writing the file).
Feel free to change the customisation to the data you want as metadata.
(but keep each comment to less than 1000 char or you will need to protect ppm)

Have a nice day.

Grimbert Jérôme commented on Tuesday, 26 October 2010, 21:44 GMT

change #5166 (#5163 + #5165) have been provided.

Grimbert Jérôme commented on Wednesday, 03 November 2010, 09:28 GMT

Should be tested in beta 40

Grimbert Jérôme commented on Thursday, 09 December 2010, 13:27 GMT

The windows version is generating a meta information about the rendering date which seems bogus:
it reports the local wall clock as Zulu (UTC/GMT), whatever your timezone!

For instance, I rendered at around 14:00 (my timezone is France, GMT-1 in winter, GMT-2 in summer)
and I get a picture with the following metadata (only copying the Render Date):

Render Date: 2010-12-09 14:00:09Z

I would have expected
Render Date: 2010-12-09 13:00:09Z
Render Date: 2010-12-09 14:00:09+0100
Render Date: 2010-12-09 14:00:09+01:00

(I'm only one hour off... but Australia has a bigger shift)

I have not yet checked for Unix from sources.

Christoph Lipka commented on Thursday, 09 December 2010, 13:37 GMT

Oops, yes - I messed that up with change #5210. Will fix.

Christoph Lipka commented on Thursday, 09 December 2010, 13:51 GMT

PNG tIME chunk was broken, too (using local time instead of GMT as per file format spec).
Fixed with #5251.

Grimbert Jérôme commented on Thursday, 30 December 2010, 10:19 GMT

Tested with beta 41.

Render Date: 2010-12-30 10:14:38Z

For a picture rendered at 11:14 local time, gmt+1, so it's ok.


Available keyboard shortcuts


Task Details

Task Editing