To write any unknown tag (or change the definition of any existing tag), all you have to do is add an entry to the config file. In your case, this entry in the %Image::ExifTool::UserDefined hash will do it:

(The value conversions are not strictly required, but will prevent binary data from being sent to your console if you extract this tag.) With this addition, you would use the following command line:

See the ExifTool_config file included with in the ExifTool distribution for more details.

- Phil

Great, that works like a charm. Any idea how I can transfer all 998 possible paths (if avalilible, of course). I think adding 1000 config file entries and havong 1000 command line options is a bit overkill.... regards Alex

Hi, first of all thanks for your great support so far. I managed to get a configuration file (http://www.grans.eu/exiftoolconfig) with an alias and all 1000 pathtags included (wrote a small java programm to generate the file ;) However I just relized that the path names aren't transfered: In the file you've got something like: .... 0x3842494d 0x07d0 0x06 "Pfad 1" some 0x00 Pathdata... If I understod correctly, 0x3842494d="8BIM" is the Photoshop marker, folled by the Path tag 0x07d0. 0x06 seems to be the length of the Path name (6 here, if the Path is called "Pfad 11" its 0x07). However exiftool skips over the path name, and doesn't insert it into the destination file. Do you have an idea how to copy that, too? regards Alex

I've done some more thinking about the IRB resource names, and have come up with a system that allows you to 1) preserve resource names when copying Photoshop tags between files, 2) define new resource names when writing new tags, and 3) define default resource names to be used when writing. I think this covers all the bases.

I have just released ExifTool 6.54 with this update.

In your case, I think you probably just want to preserve the existing resource names, in this case all you have to do is define a "SetResourceName" flag in the tag information hash for the desired tag. I have done this for you in your config file and posted it here

As well, I have added a couple of new features that allow the config file to be simplified somewhat.

I hope this helps.

- Phil

Hi Alex,

Sorry for being so quick... ;) First of all, thanks for the sample, this was a tricky bug that would have been very hard to track down with this.

There was a problem in the new "SetResourceName" feature that caused it to fail if a specific byte pattern appeared in the path data. Fortunately your sample contained this pattern, otherwise this bug could have lurked silently for quite some time. I have fixed this now, and the new code should be immune to arbitrary byte patterns in the path data.

This update will appear in version 6.57, and I have uploaded a 6.57 pre-release in case you get a chance to test it out before the official 6.57 release.

- Phil