Recent Posts

Pages: [1] 2 3 ... 10
The "exiftool" Application / Re: GPS data from DOD dashcam
« Last post by toasty on November 20, 2018, 06:48:08 PM »
I've downloaded and tried exiftool 11.20 and it works with the videos from my dashcam. Amazing response time, many thanks Phil!
The "exiftool" Application / Re: GPS data from DOD dashcam
« Last post by Phil Harvey on November 20, 2018, 11:09:41 AM »
I got your sample.

Good news:  ExifTool now decodes 21 different types of streaming GPS from videos.   :)

ExifTool 11.20 (just released) will decode the GPS from your file.

This turned out to be essentially the same as another type of streaming binary GPS, but with a different block size.

- Phil
This is sort of outside my realm of expertise.  I don't really know much about the details of image decoding.
:o From your amazing tool I thought you knew everything ! My search continues... and thanks again for your work and replies!
This is sort of outside my realm of expertise.  I don't really know much about the details of image decoding.

- Phil
The XMP exists in two raw profiles in this file.  ExifTool is editing the XMP raw profile, but there is more XMP in the photoshop "8bim" profile that ExifTool extracts but doesn't edit.

- Phil
Thanks, indeed I am looking for the bits for full resolution image when I view the full exiftool info. My point is that Nikon seems to report the actual BitsPerSample (12 or 14) and obviously still packs that info into 16bits. Apple iOS/Canon reports 16bits,  so then it seems there is no clear definitive way to deduce that information for iOS cameras?

Code: [Select]
======== DSC_0505.NEF
[IFD0]            272 Model                           : NIKON D7500
[IFD0]            258 BitsPerSample                   : 8 8 8
[SubIFD1]         258 BitsPerSample                   : 14
======== DSC_6019.NEF
[IFD0]            272 Model                           : NIKON D810
[IFD0]            258 BitsPerSample                   : 8 8 8
[SubIFD1]         258 BitsPerSample                   : 12
======== IMGP1018.DNG
[IFD0]            272 Model                           : PENTAX K-70
[SubIFD]        50717 WhiteLevel                      : 16319
[Pentax]          126 WhiteLevel                      : 16319
[IFD0]            258 BitsPerSample                   : 8 8 8
[SubIFD]          258 BitsPerSample                   : 14
[SubIFD1]         258 BitsPerSample                   : 8 8 8
======== IMG_0057.CR2
[IFD0]            272 Model                           : Canon EOS M100
[IFD0]            258 BitsPerSample                   : 8 8 8
[IFD2]            258 BitsPerSample                   : 16 16 16
======== iPhoneXRAW.dng
[IFD0]            272 Model                           : iPhone X
[SubIFD]        50717 WhiteLevel                      : 4095
[IFD0]            258 BitsPerSample                   : 8 8 8
[SubIFD]          258 BitsPerSample                   : 16
I don't see any contradiction here.  BitsPerSample represents the number of stored bits per sample, but some of these bits may be unused.  Of course, leaving unused bits is a waste of space, but it is a fairly common practice.

Looking at WhiteLevel may be more realistic, but there is nothing stopping the camera from, say, writing the upper 12 bits and setting the lower 4 bits to zero, which wouldn't show up in the WhiteLevel (although I don't know if any cameras do this).

BTW. You should be sure you are looking at tags from the IFD with a SubfileType of "Full-resolution Image".

- Phil
The "exiftool" Application / Re: exiftool(-k).exe - Freaking awesome!
« Last post by elhiero on November 20, 2018, 09:47:46 AM »
Would you like to share your Links too? I am specially interested in the Picasa "shortcuts" you made.
Some of my Windows shortcuts are shown in the picture I joined above

"Picasa" shortcuts are used to convert Picasa faces recognition data into standard keywords. It's explained in this post about avpicfacexmptagger:,9636.0.html  (Nov,20, 2018)
You will find there a downloadable config file (picasa_faces.config) and a "args.txt" file.

"DIRtoKeywords" shortcuts are used to move from a thematic classification by folder to a classification by keywords.
They require a configuration file (Dirtree.txt) to convert folder names into keywords.
It was written and explained by Phil here:,4513.0.html

Code: [Select]
ADD 12 Years
C:\Tool\exiftool.exe -k -ModifyDate+="0012:00:00 00:00:00" -DateTimeOriginal+="0012:00:00 00:00:00" -CreateDate+="0012:00:00 00:00:00"

Delete Oplympus
C:\Tool\exiftool.exe -ext orf -ext jpg  -imagedescription= -if "$imagedescription =~ /^OLYMPUS DIGITAL CAMERA/"

C:\Tool\exiftool.exe -delete_original -k

C:\Tool\exiftool.exe -restore_original -k

DIRtoAll Keywords
C:\Tool\exiftool.exe -config C:\Tool\conf\Dirtree.txt  -k -r -iptc:keywords+<dirtree -xmp-dc:subject+<dirtree

DIRtoIPTC Keywords
C:\Tool\exiftool.exe -config C:\Tool\conf\Dirtree.txt  -k -r -iptc:keywords+<dirtree

DIRtoXMP Subject
C:\Tool\exiftool.exe -config C:\Tool\conf\Dirtree.txt  -k -r -xmp-dc:subject+<dirtree

C:\Tool\exiftool.exe -k -exif:xpcomment<iptc:caption-abstract -exif:copyright<iptc:copyrightnotice -exif:xpauthor<iptc:by-line

C:\Tool\exiftool.exe -a -u -g1 -w txt

C:\Tool\exiftool.exe -a -u -g1 -G -lang fr -charset latin -w txt

C:\Tool\exiftool.exe -IPTC:Caption-Abstract<${FileName;s/\.[^.]*$//} -XMP:Description<${FileName;s/\.[^.]*$//} -L -k

C:\Tool\exiftool.exe -k -IPTC:Headline<${FileName;s/\.[^.]*$//}

C:\Tool\exiftool.exe -k -o %d%f.xmp -xmp:all

Picasa Full Keywords
C:\Tool\exiftool.exe -config "C:\Tool\conf\picasa_faces.config"  -if $PicasaRegionNames#  -@ "C:\Tool\conf\arguments.txt" -api "Filter=s/^/famille|/" "-xmp-lr:hierarchicalsubject+<PicasaRegionNames"

Picasa NoDups
C:\Tool\exiftool.exe -sep "##" "-xmp-lr:hierarchicalsubject<${xmp-lr:hierarchicalsubject;NoDups}" "-iptc:keywords<${iptc:keywords;NoDups}" "-xmp:subject<${xmp:subject;NoDups}" -k
Newbies / Re: Write Original Date Created back to file after transfer
« Last post by ArjayEl on November 20, 2018, 09:27:05 AM »
Thanks Phil, I didn't quite understand what i was doing in my first attempts, this cleared it up. Much appreciated.
Bug Reports / Feature Requests / BitsPerSample values from various RAW camera photos
« Last post by aboulfad on November 20, 2018, 09:18:19 AM »

as I was researching the iPhone RAW/dng bit per sample depth for the FULL resolution content, it quickly became very confusing to determine what is really the BitPerSample used in a DNG photo produced by an iPhoneX (mine). So I downloaded various RAW photos from various cameras, and used exiftool to display the relevant information. I am not sure why Canon and Apple report that information differently/incorrectly than the other camera manufacturers or is it a bug in exiftool (which I doubt) ?

One can potentially infer the "correct" BitsPerSample from the WhiteLevel, as per Adobe's Spec [(2 ** BitsPerSample) -1], so that would make the iPhone XsMax BitsPerSample 12, which somehow I doubt ... Is there another deterministic way from RAW values to determine this ?

System Info
1- MacOS HighSiera (10.13.6)
2- exiftool ver 11.11
3- exiftool -s -a -u -D -G1 -Model -WhiteLevel -BitsPerSample *
4/5- Have emailed link to images, exiftool output is attached.
Regards and thanks!
Pages: [1] 2 3 ... 10