I wanted to build an awesome place for people to discuss module specific issues, but I don't have any more time
for this, and there are much better places to discuss Perl-related issues. I'd recommend asking your question on Stack Overflow or
on Perl Monks.
If you are looking for a Perl tutorial or Perl-related news,
I hope these links will serve you well.
I'd assume this may be caused by Sigma not really conforming to standards. I hope my assumption is wrong and that you've got a simple solution for this dilemma.
I was thinking of reading the 'datetimeoriginal' and writing it to 'file-list.txt' with a header like '$filename/$datetimeoriginal', listing each filename with its unique 'datetimeoriginal'.
In a second step I'd use the file-list.txt and read the data to be put into the corresponding tif-file. I guess that might be a complicated workaround (? ), but still, I am not succeeding with the proper syntax.
Your advice is highly appreciated, thanks. Looking forward to hearing from you,
with kind regards, Hans.
But I do not quite succedd with the same command for a list of files in 'file_list.txt'.
OK, I must admit the tag 'datetimeoriginal' is perfectly updated with this command:
exiftool -Tagsfromfile %d../%f.x3f "-datetimeoriginal" -@ d:\images\2009\file_list.txt
473 image files updated
54 files weren't updated due to errors
- The file_list.txt contains the filenames only.
- 'File_list.txt' must be placed where there are no spaces in the path. (?)
- The command was executed from the folder containing the files that receive the tag 'datetimeorignal' from the X3F one folder up in the brach.
All the German Umlaute like 'ä', 'ö', 'ü' get trashed. 'Graubünden' becomes 'GraubÃ¼nden'. Probably caused by US-ASCII charset.
I bet there is a way to handle this as well since exiftool appears in Japanese.
What would be the syntax to preserve the utf-8 charset in textfields like 'Location', 'State' or 'Description'?
Or, how can I avoid that these values get thouched at all? (seekeing the more elegant way to accomplish this).
Then when using the verboose option '-v', it gets somewhat scarry. Quite some information is displayed, seems as the whole image is being rebuilt.
Yes, the verbose option gives a lot of detail. This is normal.
If a path contains spaces, you must put quotes around the argument.
The command you give should only write the DateTimeOriginal tag,
so I don't understand why you say the special characters get trashed,
because they won't be affected by this command. (Unless you are
doing something funny in your -@ file.)
I really don't understand what you are doing. Please give more specific
Posted on 2009-05-26 11:49:37-07
by snahin response to 10825
Re: no writeable tags found - <filename>.x3f
your answer and my update crossed eachother, so here is what I want to do:
Read the tag 'datetimeoriginal' from Sigma-X3F files and insert it to the corresponding TIF and PSD files which are already converted but in those files the tag 'datetimeoriginal' got screwed up by some software I was playing with (no back-up available).
With Exiftool I can restore the correct value from the original RAW file into the converted files.
It sounds like you have solved all your problems except for
your issue with the -v option. If you write to an
image, yes, the file gets rewritten. If you don't want to see
the details, then don't use the -v option.