exiftool Application Documentation

Started by Jom, March 16, 2020, 03:54:03 PM

Previous topic - Next topic

Jom

On page
https://exiftool.org/exiftool_pod.html#COPYING-EXAMPLES

I tried using this command
exiftool '-comment<ISO=$exif:iso Exposure=${shutterspeed}' dir

First I got this
f:\>exiftool '-comment<ISO=$exif:iso Exposure=${shutterspeed}' /
The system cannot find the file specified.


First and easiest, I just forgot to use double quotes because I'm using Windows
f:\>exiftool "-comment<ISO=$exif:iso Exposure=${shutterspeed}" /
    1 directories scanned
    1 image files updated
    1 image files unchanged

f:\>ls
$RECYCLE.BIN  System Volume Information  _MG_5003.CR2  _MG_5003.jpg  _MG_5003.jpg_original


cr2-file was not modified
This is now I found out that the "command" tag is only suitable for"jpg".
Up to this point, I've been learning on cr2-files and spent some time trying to figure out why I'm not getting anywhere.
f:\>exiftool "-comment<ISO=$exif:iso Exposure=${shutterspeed}" /
    1 directories scanned
    0 image files updated
    1 image files unchanged

f:\>ls
$RECYCLE.BIN  System Volume Information  _MG_5003.CR2


I checked directly
f:\>exiftool -comment="sdfgsdfgsdfg" _MG_5003.CR2
    0 image files updated
    1 image files unchanged

f:\>exiftool -comment="sdfgsdfgsdfg" _MG_5003.jpg
    1 image files updated


As a result of my research, it would probably be better to use a different, more universal tag for examples in Docs, such as exif:usercomment
f:\>exiftool "-exif:usercomment<ISO=$exif:iso Exposure=${shutterspeed}" /
    1 directories scanned
    2 image files updated

f:\>ls
$RECYCLE.BIN               _MG_5003.CR2           _MG_5003.jpg
System Volume Information  _MG_5003.CR2_original  _MG_5003.jpg_original

f:\>exiftool -exif:usercomment /
======== /_MG_5003.CR2
User Comment                    : ISO=100 Exposure=1/25
======== /_MG_5003.jpg
User Comment                    : ISO=100 Exposure=1/25
    1 directories scanned
    2 image files read


I am sure that this should be done so that beginners learning ExifTool do not suffer from additional difficulties that do not relate to the examples directly, because currently many people use raw, not just jpg.

Jom

#1
Probably, my message Reply #1 was either forgotten or not noticed.
Phil, please tell me what you think about this.

Jom

On
https://exiftool.org/exiftool_pod.html#WINDOWS-UNICODE-FILE-NAMES
two different designations of the same thing (I think):

...disabled by setting -charset filename="", and ExifTool may...
and
The -charset filename= option must come...

When a beginner tries to pay attention to all details, this disagreement leads to the question " What's the difference? Both options work, but they are written differently — why?".
It would probably be better to use only one option everywhere, -charset filename="" or -charset filename=?

StarGeek

Quote from: Andrei Korzhyts on March 16, 2020, 03:54:03 PM
because currently many people use raw, not just jpg.

But, IMO, most photographers don't directly edit their RAWs.  They're just too paranoid about it.  Most software writes to sidecar files, which just reinforces their opinions on keeping RAWs unchanged.

Most of the questions I've read here and on other forums are in regards to jpgs.

I'm not commenting on whether the example should be changed, I'm just disagreeing with presumption about the file types.
* Did you read FAQ #3 and use the command listed there?
* Please use the Code button for exiftool code/output.
 
* Please include your OS, Exiftool version, and type of file you're processing (MP4, JPG, etc).

Jom

QuoteI'm not commenting on whether the example should be changed, I'm just disagreeing with presumption about the file types.

I do not insist on my assumptions, I just suggest a more universal exif:usercomment tag for the examples in the documentation, so that everyone can perform these examples, not just the owners of jpg.

Paranoia appears where there is no knowledge.

I think that need to fill the RAW with metadata before any manipulation with these RAW. Then the sidecar files will be all right. And only need to use programs that you can fully control or know exactly what they do. Moreover, there are situations when the data in the RAW may be incorrect and they still need to be corrected. In short, simple paranoia will not save you, and one day there will still be trouble if there is no knowledge.

Jom

On
https://exiftool.org/faq.html#Q18
...then press RETURN at the command prompt.

It might be better for Windows
...then press ENTER at the command prompt.
?

Phil Harvey

Quote from: Andrei Korzhyts on March 24, 2020, 12:24:55 AM
It would probably be better to use only one option everywhere, -charset filename="" or -charset filename=?

These are identical options.  The command shell removes the quotes and passes the rest to the command-line application.

Quote from: Andrei Korzhyts on March 24, 2020, 02:23:56 AM
On
https://exiftool.org/faq.html#Q18
...then press RETURN at the command prompt.

It might be better for Windows
...then press ENTER at the command prompt.

Changed.

- Phil
...where DIR is the name of a directory/folder containing the images.  On Mac/Linux/PowerShell, use single quotes (') instead of double quotes (") around arguments containing a dollar sign ($).