ORF format

The ORF file format is a raw image format used in Olympus digital cameras. Like all other raw formats, this one contains image information rendered directly by a camera's sensor. ORF files feature so-called headers that present image characteristics, such as saturation, color temperature, contrast, etc. Headers also contain metadata, which includes camera's technical characteristics.

Olympus Raw Format (ORF)
Filename extension
.orf
Developed byOlympus
Type of formatraw image format

Overview

ORF files can be thought of as a format of "digital negatives." Just like film negatives, they are not usually intended to be directly viewed. Instead, ORF files contain all necessary information to create (or "develop") a usable image, in a more common format, with processing software.

Because ORF images come out without undergoing any processing, they present almost real color and shade characteristics, and they are more open for extensive editing than JPEG or TIFF images. ORF files have to be copied to a PC's hard disk, and then one can resort to an extensive array of adjustments. The format allows users to achieve maximum precision by setting their own white balance and saturation values, which is not feasible in JPEG or TIFF.

This approach is used by experienced professional and devoted amateur photographers. ORF files contain 12, 14 or more bits per pixel per channel, whereas JPEG images have only 8 bits per pixel per channel.

File name syntax

ORF files use the following syntax:

DigitSyntax
1stColorspace "_" for Adobe or "P" for RGB.
2ndMonth "1-9": Jan-Sep. "A-C": Oct-Dec.
3rd & 4thDay "01-31"
5th - 8thRunning auto numbering

Example: PC071138.ORF. This was taken RGB colorspace on December 7 with the number 1138 generated by the camera.

It has been confirmed on the Olympus E-410, Olympus E-420 and Olympus E-5.

gollark: VPNs prevent ISPs from seeing all this except possibly to some extent #3, but the VPN provider can still see it, and obviously whatever service you connect to has any information sent to it.
gollark: Anyway, with HTTPS being a thing basically everywhere and DNS over HTTPS existing, ISPs can only see:- unencrypted traffic from programs/services which don't use HTTPS or TLS- the *domains* you visit (*not* pages, and definitely not their contents, just domains) - DNS over HTTPS doesn't prevent this because as far as I know it's still in plaintext in HTTPS requestts- metadata about your connection/packets/whatever- also the IPs you visit, but the domains are arguably more useful anyway
gollark: On my (GNU/)Linux computing devices, which is all of my non-portable ones, I run dnscrypt-proxy, which acts as a local DNS server which runs my queries through DNS over HTTPS/DNS over TLS/DNSCrypt servers.
gollark: In other news, the first rule of tautology club is the first rule of tautology club.
gollark: Yes, Google is definitionally Google.

See also

This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.