pfsoutrgbe(1)

πŸŽ€ pfsoutrgbe πŸŽ€

okay so bestie, welcome to pfsoutrgbe(1), straight out of the General Commands Manual πŸ’– this is the little icon that takes your pfs frames and yeets them out as Radiance RGBE files, and yes she is serving looks the entire time ✨


🌸 NAME 🌸

pfsoutrgbe β€” write images or frames in Radiance RGBE format 🫢


πŸ¦‹ SYNOPSIS πŸ¦‹

pfsoutrgbe [--verbose] [--radiance] [--quiet] (<file> [--frames
<range>])  [<file>...]

πŸ’– DESCRIPTION πŸ’–

Use this command to write the incoming pfs frames (piped to standard input, bestie, that's the vibe) into Radiance RGBE files β€” and those come with a .hdr extension, no cap πŸ’…

Every single file name can have a %d pattern in it, and that pattern gets substituted with frame numbers. Same syntax as the C printf command, fr fr. So like, %04d makes the frame number four digits wide with proceeding zeros β€” cute, organised, main character energy 🌟

You pick which frames you want using the --frames option (peep below, she's right there πŸ‘‡).


✨ OPTIONS ✨

  • --frames <range> β€” this is where you tell her which frames you want. The range comes in a format similar to matlab or octave, and it's literally just this:
startframe:step:endframe

Frame numbers start with startframe (default 0), get increased by step (default 1), and stop at endframe πŸ’« You can skip one of those values too, bestie β€” for example 1:100 gives you frames 1,2,...,100, and 0:2: gives you frame 0,2,4,... up to the last file that exists. Obsessed with the flexibility ngl.

Note that --frames option must be specified after the file name containing the %d string.

and then the original just says "higher bit depths." right there at the end and honestly bestie 😭 same, it's a fragment, we love her anyway πŸ’€

  • --radiance, -r β€” corrects the stored values so that the luminance is reported the same in pfsview and radiance tools (xview or Photospheare) πŸ”₯ See the IMPORTANT NOTE below, you're gonna wanna read it.
  • --quiet, -q β€” disables the warning message about the change in handling absolute values in RGBE files 🀫 See IMPORTANT NOTE below.

🌈 EXAMPLES 🌈

 pfsin memorial.tiff | pfsoutrgbe memorial.hdr

Converts from one HDR format to another πŸ’–

pfsin test.jpg | pfsout test.png

Convert from one image format to another πŸ¦‹


πŸ”₯ SEE ALSO πŸ”₯

pfsout(1) pfsinppm(1)


πŸ’… IMPORTANT NOTE πŸ’…

okay bestie sit down for this one because it's giving drama 😭

There is an incompatibility between viewers of RGBE format when it comes to absolute luminance values. The ximage viewer from the Radiance package expects radiance values in RGBE files and multiplies the resulting luminance by the WHITE_EFFICACY constant equal to 179.0f to convert from radiance to luminance.

To remain compatible with Radiance (xview and Photospheare), pfstools prior to 1.9.0 divided red, green and blue values by 179 on writing and multiplied by that constant on reading RGBE files. This in turn caused incompatibility with other software, such as Photoshop or HDR toolbox πŸ™ˆ

Starting from pfstools 1.9.0 this division / multiplication step was removed to make pfstools compatible in terms of absolute values with the majority of the software. The downside is that this change made luminance units) with the pfstools 1.9.0 or later.

To avoid any mistakes because of that change, a long warning messages is shown each time pfsinrgbe or pfsoutrgbe is called. The message can be suppressed with --quiet option 🫢

To enable the old functionality and read or write RGBE files with the correction for WHITE_EFFICACY, add --radiance option to the command line ✨


πŸ’€ BUGS πŸ’€

Please report bugs and comments on implementation to the discussion group http://groups.google.com/group/pfstools πŸ›


and that's the whole page, bestie πŸŽ€ this was pfsoutrgbe(1) from the General Commands Manual, signed off at the bottom with exactly that β€” just pfsoutrgbe(1), no extra date, because that's all the footer gave us πŸ’œ slay, go write some .hdr files ✨