MakerNote

From Just Solve the File Format Problem
(Difference between revisions)
Jump to: navigation, search
(Created page with "{{FormatInfo |formattype=electronic |subcat=Graphics }} Exif tag 37500, "MakerNote", is (unfortunately) a popular way store custom metadata. By the Exif standard, it is ...")
 
m
Line 4: Line 4:
 
}}
 
}}
  
[[Exif]] tag 37500, "MakerNote", is (unfortunately) a popular way store custom metadata.
+
[[Exif]] tag 37500, "MakerNote", is (unfortunately) a popular way to store custom metadata.
  
 
By the Exif standard, it is merely a block of arbitrary bytes, which creators of Exif files may use in any way they like.
 
By the Exif standard, it is merely a block of arbitrary bytes, which creators of Exif files may use in any way they like.
  
Some of the data formats used in MakerNotes have been documented or reverse-engineered. A MakerNote usually begins with a signature of some sort, such as the name of a camera manufacturer, which can help to identify its contents.
+
Some of the data formats used in MakerNotes have been documented or reverse-engineered. A MakerNote usually begins with a signature of some sort, such as the name of a camera manufacturer, to help identify its contents.
  
 
== External links ==
 
== External links ==

Revision as of 18:44, 19 February 2013

File Format
Name MakerNote
Ontology
Exif tag 37500, "MakerNote", is (unfortunately) a popular way to store custom metadata.

By the Exif standard, it is merely a block of arbitrary bytes, which creators of Exif files may use in any way they like.

Some of the data formats used in MakerNotes have been documented or reverse-engineered. A MakerNote usually begins with a signature of some sort, such as the name of a camera manufacturer, to help identify its contents.

External links

Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox