Clipka: /* Output File Type */

2016-12-23T05:15:23Z

Output File Type

Clipka: Created page with "==Output File Type==

`Output_File_Type=`x{{#indexentry:Output_File_Type, ini-option}}
2016-12-23T05:11:16Z

Created page with "==Output File Type== <table width="100%" class="option-list"> <tr> <td width="30%"><code>Output_File_Type=</code>x{{#indexentry:Output_File_Type, ini-option}}</td> <td width="..."

New page
==Output File Type==
<table width="100%" class="option-list">
<tr>
<td width="30%"><code>Output_File_Type=</code>x{{#indexentry:Output_File_Type, ini-option}}</td>
<td width="70%">Sets file output format to x</td>
</tr>

<tr>
<td><code>+F</code>xn{{#indexentry:+f}}</td>
<td>Sets file output on; sets format x, depth n</td>
</tr>

<tr>
<td><code>-F</code>xn{{#indexentry:-f}}</td>
<td>Sets file output off; but in future use format x, depth n</td>
</tr>

<tr>
<td><code>Output_Alpha=</code>bool{{#indexentry:Output_Alpha, ini-option}}</td>
<td>Sets alpha output on/off</td>
</tr>

<tr>
<td><code>+UA</code>{{#indexentry:+ua}}</td>
<td>Sets alpha output on</td>
</tr>

<tr>
<td><code>-UA</code>{{#indexentry:-ua}}</td>
<td>Sets alpha output off</td>
</tr>

<tr>
<td><code>Bits_Per_Color=</code>n{{#indexentry:Bits_Per_Color, ini-option}}</td>
<td>Sets file output bits/color to n</td>
</tr>
</table>

{{#indexentry:output formats}}
{{#indexentry:bmp, output formats}}
{{#indexentry:exr, output formats}}
{{#indexentry:gif, output formats}}
{{#indexentry:hdr, output formats}}
{{#indexentry:jpeg, output formats}}
{{#indexentry:pgm, output formats}}
{{#indexentry:png, output formats}}
{{#indexentry:tga, output formats}}
{{#indexentry:tiff, output formats}}
Note: As of version 3.7 the default output file type for all supported platforms is PNG. You may select one of several different file types by using <code>Output_File_Type=</code>x or <code>+F</code>x where x is one of the following:
<table width="100%" class="option-list">
<tr>
<td width="30%"><code>.. B</code>{{#indexentry:Bitmap output}}{{#indexentry:Output, Bitmap}}{{#indexentry:+fc}}</td>
<td width="70%">Universal Bitmap image file format</td>
</tr>
<tr>
<td width="30%"><code>.. C</code>{{#indexentry:Targa output, compressed}}{{#indexentry:Output, Targa, compressed}}{{#indexentry:+fc}}</td>
<td width="70%">Compressed Targa-24 format (RLE, run length
encoded)</td>
</tr>

<tr>
<td width="30%"><code>.. E</code>{{#indexentry:OpenEXR output}}{{#indexentry:Output, OpenEXR}}{{#indexentry:+fe}}</td>
<td width="70%">OpenEXR High Dynamic-Range format</td>
</tr>

<tr>
<td width="30%"><code>.. H</code>{{#indexentry:Radiance output}}{{#indexentry:Output, Radiance}}{{#indexentry:+fh}}</td>

<td width="70%">Radiance High Dynamic-Range format</td>
</tr>

<tr>
<td width="30%"><code>.. J</code>{{#indexentry:JPEG output, compressed}}{{#indexentry:Output, JPEG, compressed}}{{#indexentry:+fj}}</td>
<td width="70%">JPEG format (Note: This format is not loss-free and will generate compression artifacts)</td>
</tr>

<tr>
<td><code>.. N</code>{{#indexentry:PNG output}}{{#indexentry:Output, PNG}}{{#indexentry:+fn}}</td>
<td>PNG (portable network graphics) format</td>
</tr>

<tr>
<td><code>.. P</code>{{#indexentry:PPM output}}{{#indexentry:Output, PPM}}{{#indexentry:+fp}}</td>
<td>Unix PPM format</td>
</tr>

<tr>
<td><code>.. S</code>{{#indexentry:System-specific output}}{{#indexentry:Output, system-specific}}{{#indexentry:Output, BMP}}{{#indexentry:BMP output}}{{#indexentry:+fs}}</td>
<td>System-specific format: See the notation at the end of this section.</td>
</tr>

<tr>
<td><code>.. T</code>{{#indexentry:Targa output, uncompressed}}{{#indexentry:Output, Targa, uncompressed}}{{#indexentry:+ft}}</td>
<td>Uncompressed Targa-24 format</td>
</tr>
</table>

{{New}} as of version 3.7.1, instead of <code>Output_File_Type=C</code> you can also use <code>Output_File_Type=T Compression=1</code> to choose RLE-encoded Targa format.


PNG is an image format designed not only to replace GIF, but to improve on its shortcomings. PNG offers the highest compression available without loss for high quality applications, such as ray-tracing.


{{New}} Prior to version 3.7.1, PPM output always created the compact raw (binary) format. The <code>Compression=0</code> ini setting can now be used to select the plain (ASCII) format instead.


The system specific format depends on the platform used and is covered in the appropriate system specific documentation.


JPEG is particularly good at achieving high compression rates with photographic or photorealistic images, making it one of the most frequently used formats on the Internet. However, it is not loss-free. Images generated with this option will always contain compression artifacts (image defects). If you need to keep a high-quality image you should render using one of the loss-free formats.

Note: Chroma sub-sampling has been disabled in JPEG output, and there has been a reduction in the default quality setting.

The JPEG compression quality can be controlled using the <code>Compression</code> ini file option which, if set, needs to be an integer between 0 and 100. If values of 0 or 1 are specified then the default compression quality setting of 85% is used. Otherwise the value specified (2-100) is used as the compression quality setting. A value of 2 produces the smallest file (maximum compression), but looks terrible. A value of 100 produces the largest file (least compression) but can still contain some compression artifacts. Values lower than 0 are clipped to 0. Values greater than 100 are clipped to 100.


Most of these formats output 24 bits per pixel with 8 bits for each of red,
green and blue data. PNG and PPM allow you to optionally specify the output bit
depth from 5 to 16 bits for each of the red, green, and blue colors, giving
from 15 to 48 bits of color information per pixel. The default output depth
for all formats is 8 bits/color (16 million possible colors), but this may be
changed for PNG and PPM format files by setting <code>Bits_Per_Color=</code>n
or by specifying <code>+FN</code>n or <code>+FP</code>n,
where n is the desired bit depth.

Specifying a smaller color depth like 5 bits/color (32768 colors) may be
enough for people with 8- or 16-bit (256 or 65536 color) displays, and will
improve compression of the PNG file. Higher bit depths like 10 or 12 may be
useful for video or publishing applications, and 16 bits/color is good for
grayscale height field output (See section [[Reference:Height Field|:Height Field|Height Field]] for
details on height fields).

Targa format also allows 8 bits of alpha transparency data to be output,
while PNG format allows 5 to 16 bits of alpha transparency data, depending on
the color bit depth as specified above. You may turn this option on with
<code> Output_Alpha=on</code> or <code>+UA</code>. The default is off or
<code> -UA</code>. 
The alpha channel stores a transparency value for each pixel, just like
there is also stored a value for red green and blue light for each pixel. In
POV-Ray, when the alpha channel is turned on, all areas of the image
where the background is partly or fully visible will be partly or fully
transparent. Refractions of the background will also be transparent, but not
reflections. Also anti-aliasing is taken into account
The philosophy of the alpha channel feature in POV-Ray is that the
background color should not be present in the color of the image when the
alpha channel is used. Instead, the amount of visible background is kept in
the alpha and only in the alpha channel. That ensures that images look
correct when viewed with the alpha channel.
See section [[Reference:Image Map#Using the Alpha Channel|Using the Alpha Channel]] for
further details on using transparency in imagemaps in your scene.

Note: In version 3.7 alpha handling for image file output has changed. Effectively, the background now requires a <code>filter</code> or <code>transmit</code> value in order for alpha transparency to work properly.

Previous versions of POV-Ray always wrote associated alpha for output, this has been changed on a per-file-format basis as follows:
<ul>
<li> PNG will use straight alpha as per specification.</li>
<li> OpenEXR <strike style="color:red">and TIFF</strike> (Editor's Note: TIFF output is not supported) will use associated alpha as per specifications.</li>
<li> TGA and BMP 32-bit RGBA will use straight alpha, retaining file input compatibility for now, until a final decision has been made on these formats.</li>
</ul>

In addition to support for variable bit-depths, alpha channel, and grayscale
formats, PNG files also store the <code>File_Gamma</code> value so the
image displays properly on all systems.
The <code>hf_gray_16</code> global setting, as described in section
[[Reference:Global Settings#HF_Gray_16|:HF_Gray_16|HF_Gray_16]] will also affect the
type of data written to the output file.
The [http://radsite.lbl.gov/radiance/HOME.html Radiance] Synthetic Imaging System or .hdr image format was originally developed to aid lighting designers and architects by predicting the light levels and appearance of a space prior to construction. The [http://www.openexr.com/index.html OpenEXR] or .exr image file format was developed by Industrial Light & Magic™ for use in computer imaging applications.
Most image formats now include metadata (BMP is a notable exception). This metadata contains the POV-Ray version, render date/time (GMT), platform (e.g. x86_64-pc-win), and compiler used to build the POV-Ray executable.
Note: System-specific or type "s" output file format is being retained for legacy support reasons. Windows and Unix mapping remains the same, BMP and TGA respectively, however on Macintosh it has been changed to PNG, and a warning is issued when type "s" is used.

@@ Line 34: / Line 34: @@
 <td><code>Bits_Per_Color=</code>n{{#indexentry:Bits_Per_Color, ini-option}}</td>
 <td>Sets file output bits/color to n</td>
 </tr>
 </table>

Reference Talk:File Output Options - Revision history

Clipka: /* Output File Type */