Convert PFM to ORA
Turn PFM images into OpenRaster. Values from 0 to 1 are shown as black to white without a brightness curve, and values outside that range are clipped, so depth or disparity maps need scaling first.
Converted in an isolated sandbox on our serversDeleted after 24 hours
Drop PFM files on the dialor turn it to pick what to do
A layered image from a float map.The PFM pixel values become an ORA image you can open in MyPaint, GIMP or Krita.
What you get
One ORA file. ORA is a zip that holds the layers and a merged preview, and it opens in MyPaint, GIMP and Krita.
Values from 0 to 1 are shown as black to white. No brightness curve is applied, so the numbers map straight to the gray they land on.
What changes
Values outside the range of 0 to 1 are clipped. Anything below 0 becomes black, and anything above 1 becomes white.
Metadata is dropped and does not appear in the ORA file.
Depth and disparity maps
Depth or disparity maps often hold values outside 0 to 1. Scale them into that range first, or the clipped areas lose their detail.
To go the other way, use ORA to PFM.
PFM and ORA.What each format is.
The formats
Portable FloatMap
Floating-point pixels in the PNM family, used for HDR and depth maps.
- Extensions
- .pfm
- MIME type
- image
/x -portable -floatmap - Kind
- Images
OpenRaster
The open layered image format of MyPaint, GIMP and Krita. A zip with the layers and a merged preview.
- Extensions
- .ora
- MIME type
- image
/openraster - Kind
- Images
In your code.The same PFM to ORA conversion through the API, for your app or your agent.
$ cv convert photo.pfm photo.ora$ cv convert photo.pfm photo.oraQuestions.What people ask about PFM to ORA.
Its values lie outside 0 to 1, and those are clipped. Scale the map into that range before you convert it.
No. Values from 0 to 1 are shown as black to white without a brightness curve.
No. Metadata is dropped during conversion.
One file. It is an ORA with the layers and a merged preview.