News:

2023-08-10 - ExifTool version 12.65 released

Main Menu

txt files

Started by Archive, May 12, 2010, 08:54:25 AM

Previous topic - Next topic

Archive

[Originally posted by tallguy on 2008-09-18 10:39:04-07]

Phil

   I am a "newbe", so bear with me. I am using the GUI drag and drop, but cannot find the sidecar txt file.

Thanks

Dave (tallguy)

Archive

[Originally posted by exiftool on 2008-09-18 11:14:16-07]

Bogdan should be able to help with this, but if you are talking
about the output text file written by exiftool, I would expect
it to appear in the same directory as the image.

- Phil

Archive

[Originally posted by bogdan on 2008-09-18 16:20:35-07]

Hi,

I'm not sure what do you mean by "using the GUI drag and drop", and that you cannot find "the sidecar txt file". Are you talking about ExifToolGUI (from http://freeweb.siol.net/hrastni3/" target="_blank">http://freeweb.siol.net/hrastni3/ )? If yes, then....

Within ExifToolGUI you select (multiple) desired image files, and then use menu:

Extract/Import_Export metadata into_TXT files...

After that you're prompted with a form, where you can select what to export, and where to write txt files: by default into the same folder (directory), or into "txt" subfolder.

But maybe you are using another GUI... :-)

Greetings,

Bogdan

Archive

[Originally posted by tallguy on 2008-09-18 17:07:20-07]

Bogdan

   I am using the Exiftool ver 7.4.2 from Phil Harvey's site : exiftool(-a -u -g1 -w txt) exe.

Thanks

Archive

[Originally posted by exiftool on 2008-09-18 17:33:46-07]

Sorry Bogdan.  I thought when I saw "GUI" that he was using your
utility.

The .txt files should appear in the same directory as
the original images after dropping on this .exe.

- Phil

Archive

[Originally posted by tallguy on 2008-09-18 19:00:53-07]

Phil

   I checked the file folder where the images are stored and there does not seem to be any .txt files present.
   The images are stored on a partioned drive "G" and not "C" if that would make a difference.

Dave

Archive

[Originally posted by exiftool on 2008-09-19 10:20:14-07]

Hi Dave,

Thanks, that might be useful information.  I'll drag out the PC and test
this myself.  Give me a day or two to see if I can figure out what is going
on.

- Phil

Archive

[Originally posted by tallguy on 2008-09-19 10:34:44-07]

Phil

    Thanks, I will wait for your response.

Dave

Archive

[Originally posted by bogdan on 2008-09-19 10:55:34-07]

Hi,

Just for info... I've tried "exiftool(-a -u -g1 -w txt).exe" shortcut on my PC (.exe on C drive and image files on partitioned E: drive) using latest exiftool version (7.43) and it works as expected here.

Greetings,

Bogdan

Archive

[Originally posted by exiftool on 2008-09-21 10:23:56-07]

Thanks Bogdan.

I just tried this too:  I plugged in a flash drive so
I would have a second writable disk (drive e:), then I dropped an
image called "Writer.jpg" from e:\ onto "exiftool(-a -u -g1 -w txt).exe".
The file "e:\Writer.txt" was created.  I also tried dropping an image from
within a (deeply nested) folder (with spaces in the folder
names because some people have reported troubles with this
),
and as expected exiftool put the .txt file in the same folder as the image.
I then added a -r option and dropped the entire drive e: on
"exiftool(-a -u -g1 -w txt -r).exe" and it created .txt files beside all
image files on the drive.  So unfortunately I cannot reproduce the
problem.

Dave: Try adding a -k option so you can read the output
of the command, which will tell you how many output files were created.
Also, it will tell you if an output file already exists, and in this case
the full path name for the file will be listed.  So if you drop a file
twice, it should say "0 output files created" and list the full path
of the file that it was trying to create.  This may help you track
down the missing file.

- Phil

Archive

[Originally posted by tallguy on 2008-09-22 23:36:48-07]

 Phil

     I removed the ".exe" from the end of the detail "exiftool(-a -u
 -g1 -w txt)", dropped the image file on it, and the .txt file was
 created. I then added the "-k" and the "file created" info was shown
 in the command window, so all seems to be working.

    With my experience level, I probably screwed something up along the way.
 Some day some file will mysteriously come out of the woodwork with all
 the old info on it!

   Many thanks for helping me out with this.

 Dave (Lindsay, Ontario)

Archive

[Originally posted by exiftool on 2008-09-23 11:20:51-07]

Ah, OK.  This indicates to me that the ".exe" was probably hidden
in the original file name (ie. Windows hid the file extension, but
it was actually there).  So you likely had a file that actually had
two extensions when you could only see one.  This is very confusing,
and would cause the problem you observed because the embedded
arguments won't work if the file is named ".exe.exe".

Glad this problem is solved.

- Phil