jauharshaikh / metadata-extractor

Automatically exported from code.google.com/p/metadata-extractor
0 stars 0 forks source link

Older Canon RAW (CRW) files fail as they are not TIFF format #42

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
I was trying to use this on a large number of images, many older, but all of my 
Canon CRW files fail to be parsed.

This is (I think) because they are guessed to be TIFF, but the older CRW files 
are not in standard TIFF format:

http://www.sno.phy.queensu.ca/~phil/exiftool/canon_raw.html

Therefore, when the TiffMetadataReader attempts to verify them, it falls over 
with ExifReader expecting 49492a but getting 49491a due to the incorrect format.

Michael.

Original issue reported on code.google.com by koala...@gmail.com on 21 Apr 2012 at 1:37

Attachments:

GoogleCodeExporter commented 8 years ago
Has this issue been scheduled to be resolved?

whitezelb@lesa.net

Original comment by white...@gmail.com on 18 May 2012 at 8:25

GoogleCodeExporter commented 8 years ago

Original comment by drewnoakes on 20 May 2012 at 5:52

GoogleCodeExporter commented 8 years ago

Original comment by drewnoakes on 24 May 2012 at 6:58

GoogleCodeExporter commented 8 years ago

Original comment by drewnoakes on 16 Oct 2012 at 7:59

GoogleCodeExporter commented 8 years ago
After doing some work recently with other raw formats, I took a look at this 
again. Unfortunately the CRW format is significantly different to the CR2 
format and will require a reasonable amount of work to include support for it.

However I would still really like to get this in soon, so I'm scheduling it 
tentatively for the 2.7.0 release.

If anyone would like to provide a patch for this, it would be greatly 
appreciated!

Original comment by drewnoakes on 30 Oct 2012 at 6:34

GoogleCodeExporter commented 8 years ago
It's worth noting that in order to support this feature, the 'magic number' 
checking that takes place in ImageMetadataReader will need to be extended to 
work on more than the first two bytes -- a change that will make other types of 
file checking more robust anyway.

It might be worth making a FileTypeInspector class with an enum of supported 
file types, as this operation could in fact be useful under other circumstances 
too.

Original comment by drewnoakes on 30 Oct 2012 at 6:37

GoogleCodeExporter commented 8 years ago
Marking as high priority due to the number of votes this has received.

Original comment by drewnoakes on 30 Oct 2012 at 6:37

GoogleCodeExporter commented 8 years ago
This issue has been migrated along with the project to GitHub:

https://github.com/drewnoakes/metadata-extractor/issues/2

Original comment by drewnoakes on 19 Nov 2014 at 11:15