| 1 |
|
.\" RCSid "$Id$" |
| 2 |
|
.TH RTPICT 1 3/19/2018 RADIANCE |
| 3 |
|
.SH NAME |
| 4 |
< |
rtpict - generate a RADIANCE picture using rtrace |
| 4 |
> |
rtpict - generate a RADIANCE picture or layered image using rtrace |
| 5 |
|
.SH SYNOPSIS |
| 6 |
|
.B rtpict |
| 7 |
|
.B "-n nproc" |
| 8 |
|
[ |
| 9 |
+ |
.B "-o[vrxlLRXnNsmM] out_dir" |
| 10 |
+ |
][ |
| 11 |
+ |
.B "-d ref_depth/unit" |
| 12 |
+ |
] |
| 13 |
+ |
[ |
| 14 |
|
.B "rpict options" |
| 15 |
|
] |
| 16 |
|
[ |
| 48 |
|
.I \-af |
| 49 |
|
option if an irradiance cache is being generated; |
| 50 |
|
otherwise, your speed-up will be far from linear. |
| 51 |
< |
.SH EXAMPLE |
| 51 |
> |
.PP |
| 52 |
> |
If the |
| 53 |
> |
.I \-o |
| 54 |
> |
option has additional characters corresponding to output types from |
| 55 |
> |
.I rtrace, |
| 56 |
> |
it must be followed by the name of a directory that either exists or |
| 57 |
> |
will be created to contain image layers, one per output type. |
| 58 |
> |
The supported types are listed below, and do not include types that |
| 59 |
> |
are useless or have no convenient representation. |
| 60 |
> |
The table below shows the correspondence between output type and file name |
| 61 |
> |
in the specified directory: |
| 62 |
> |
.sp |
| 63 |
> |
.nf |
| 64 |
> |
v radiance.hdr |
| 65 |
> |
r r_refl.hdr |
| 66 |
> |
x r_unrefl.hdr |
| 67 |
> |
l d_effective.dpt |
| 68 |
> |
L d_firstsurf.dpt |
| 69 |
> |
R d_refl.dpt |
| 70 |
> |
X d_unrefl.dpt |
| 71 |
> |
n perturbed.nrm |
| 72 |
> |
N unperturbed.nrm |
| 73 |
> |
s surface.idx |
| 74 |
> |
m modifier.idx |
| 75 |
> |
M material.idx |
| 76 |
> |
.fi |
| 77 |
> |
.sp |
| 78 |
> |
Different encodings are associated with different data types. |
| 79 |
> |
Color data (from the 'v', 'r', and 'x' types) will be converted to |
| 80 |
> |
a flat RGBE picture by |
| 81 |
> |
.I pvalue(1). |
| 82 |
> |
Distances (from the 'l', 'L', 'R', and 'X' types) will be |
| 83 |
> |
converted to a 16-bit representation by |
| 84 |
> |
.I rcode_depth(1), |
| 85 |
> |
and the |
| 86 |
> |
.I \-d |
| 87 |
> |
option should be used to assign the reference (median) depth and world |
| 88 |
> |
units, which applies to the overall scene. |
| 89 |
> |
Surface normals (from the 'n' and 'N' types) will be converted |
| 90 |
> |
to a 32-bit representation by |
| 91 |
> |
.I rcode_normal(1). |
| 92 |
> |
Finally, identifiers (from the 's', 'm', and 'M' types) will be |
| 93 |
> |
converted to a 16-bit index format by |
| 94 |
> |
.I rcode_ident(1). |
| 95 |
> |
.PP |
| 96 |
> |
If the |
| 97 |
> |
.I \-i |
| 98 |
> |
option is used to turn on irradiane output, then the picture associated |
| 99 |
> |
with the 'v' type will be renamed |
| 100 |
> |
.I "irradiance.hdr" |
| 101 |
> |
and some other output types become irrelevant (i.e., 'r', 'x', 'R', and 'X'). |
| 102 |
> |
If one or more of the associated output files already exists in the |
| 103 |
> |
destination directory, an error will be printed and the command will abort. |
| 104 |
> |
.SH EXAMPLES |
| 105 |
|
To render a scene with four processes: |
| 106 |
|
.IP "" .2i |
| 107 |
|
rtpict -n 4 -vf mypers.vf -ab 1 -af scene.amb scene.oct > scene_pers.hdr |
| 108 |
+ |
.PP |
| 109 |
+ |
To render radiance, first surface distance, and normals in a layered image: |
| 110 |
+ |
.IP "" .2i |
| 111 |
+ |
rtpict -n 8 -vf fish.vf @render.opt -ovLn fisholay scene.oct |
| 112 |
+ |
.SH NOTES |
| 113 |
+ |
Users should seriously consider using |
| 114 |
+ |
.I rpiece(1) |
| 115 |
+ |
when irradiance caching is employed with a shared ambient file. |
| 116 |
+ |
If |
| 117 |
+ |
.I rtpict |
| 118 |
+ |
is used in multiprocessing mode with a shared irradiance cache, |
| 119 |
+ |
it is trying to compute almost |
| 120 |
+ |
the same part of the same scanline in different processes, which |
| 121 |
+ |
results in many redundant calculations. |
| 122 |
+ |
The |
| 123 |
+ |
.I rpiece |
| 124 |
+ |
program avoids this by working on separate tiles in each |
| 125 |
+ |
process, with less overlap in the indirect irradiance calculation. |
| 126 |
+ |
Either program will benefit from an "overture" run of a |
| 127 |
+ |
single-process rpict to create the ambient file using a low-resolution |
| 128 |
+ |
rendering that is discarded, but this will not completely solve the |
| 129 |
+ |
problem for |
| 130 |
+ |
.I rtpict. |
| 131 |
|
.SH AUTHOR |
| 132 |
|
Greg Ward |
| 133 |
|
.SH "SEE ALSO" |
| 134 |
< |
getinfo(1), lookamb(1), mkpmap(1), oconv(1), pdfblur(1), pfilt(1), |
| 135 |
< |
pinterp(1), pmblur(1), printf(3), ra_rgbe(1), rad(1), rpiece(1), |
| 136 |
< |
rpict(1), rtrace(1), rvu(1) vwrays(1), |
| 134 |
> |
getinfo(1), mkpmap(1), oconv(1), pfilt(1), |
| 135 |
> |
pvalue(1), rad(1), rcode_depth(1), rcode_normal(1), rcode_ident(1), |
| 136 |
> |
rcrop(1), rpiece(1), rpict(1), rsplit(1), rtrace(1), rvu(1), vwrays(1) |
