PSB files don't show IPTC: Original transmission reference field in Details or Thumbnails + labels views

[tomgoodell]

In the Browser > Columns settings I have the "IPTC: Original transmission reference" field set to display. I have that column displayed in my Details view. I also have included the "Original Transmission" field in my Thumbnail > Labels settings. It's the same field, it just has slightly different names in the Columns and Labels dialogs.

The field displays fine in Details view and Thumbnails + Labels view for PSD, TIF, and JPG files. It also displays properly in the ExifTool tab in the Info panel for all file types. But it does not display in Details or Thumbnails + Labels views for PSB files.

[jkm]

Tom, this might be a bug in XnViewMP, but maybe not; there is room here for misunderstanding. There may be a bug, but I'm not sure yet in which application.

How exactly are you setting that field? Because XnView will not allow the Edit IPTC function for PSB files...

If you are setting that field for other files (like JPEG or TIFF) in XnViewMP, then depending on how you have the Edit IPTC dialog configured, you might be setting either IPTC:OriginalTransmissionReference OR XMP:TransmissionReference OR both. That can affect your interpretation of further results, because you might think you're doing one thing but actually doing something else. What is your "Mode" setting on the Options tab of Edit IPTC?

Beyond that, there seems to be a disagreement between XnViewMP and Adobe as to how to read/write that field. (I tested with JPEG, PSD, and PSB; nothing more)

When I write the "Transmission Reference" field on the Origin tab in Photoshop, it writes both IPTC:OriginalTransmissionReference AND XMP:TransmissionReference, and exiftool sees both values. XnViewMP can also see this value using the IPTC:OriginalTransmissionReference function, but only in the JPEG file. To see the values written by Photoshop, XnViewMP must look at one of the following:
Exiftool:IPTC:OriginalTransmissionReference
XMP:TransmissionReference
Exiftool:XMP:TransmissionReference

So there are multiple possibilities here:
1. XnViewMP reads the field incorrectly in PSD and PSB files (which would be a bug in XnViewMP)
2. Adobe writes the value in a non-conformant way, but Exiftool is forgiving enough to read it anyway but XnViewMP is not
3. Some other confusion as to which field is actually being used depending on exactly what you're doing.

You should be able to work around this issue by using the Exiftool field:
Exiftool:IPTC:OriginalTransmissionReference

In a label, this would be written as {exiftool:OriginalTransmissionReference} (or {exiftool:IPTC:OriginalTransmissionReference})

Note: I do not see a difference between PSD and PSB files as you report. XnViewMP behaves for me the same for both file types.

Pierre will need to check if this is actually a problem in XnViewMP with reading that field in Adobe files.

[tomgoodell]

JKM—thank you for that detailed response. I will answer as best as I can, being still fairly green to XnView MP.

The "Mode" settings on the Options tab of Edit IPTC is set to IPCT-IIM, update or create XMP

Almost always I set the field in Photoshop using the Custom Metadata for Photoshop plugin (https://exchange.adobe.com/apps/cc/1037 ... for-bridge). When I check in the Origin field in Photoshop it is correctly written there.

I also see that this results in writing to both IPTC:OriginalTransmissionReference AND XMP:TransmissionReference, and exiftool sees both values. I can see both values in the Info panel—Original transmission reference in the IPTC-IIM and ExifTool tabs, and Transmission Reference in the XMP tab. The value shows up in all 3 tabs for all file types.

When I examine a jpg or psd file, the value also shows up in both Transmission Reference and Original Transmission Reference fields.

In the Info panel it also shows up in both fields for PSB files.

Using your suggestion in the Details view I replaced the IPTC:OriginalTransmissionReference with the XMP:TransmissionReference field and that now shows up correctly in that column for all file types including PSB.

In the Thumbnail Labels section I do not see the XMP:TransmissionReference as an option, only IPTC: Original Transmission which I now notice is different from the other two we have been discussing. Nonetheless the value does show correctly as a label under thumbnails for jpg and tif files. But it does not show as a label under either psd or psb files.

I thought of pasting your suggestion of {exiftool:OriginalTransmissionReference} into a custom label field but the "Custom label" field is not responsive—I can't click in it.

Please let me know if I'm providing useful information and if there's anything else I can provide. Your explanation clarified for me that there are several different fields in different systems that are interacting here. I appreciate your guidance. I'm learning steadily ...

[jkm]

Nonetheless the value does show correctly as a label under thumbnails for jpg and tif files. But it does not show as a label under either psd or psb files.

Ok, this at least clarifies you're getting the same results as I am, which is what I would hope.

I thought of pasting your suggestion of {exiftool:OriginalTransmissionReference} into a custom label field but the "Custom label" field is not responsive—I can't click in it.

In this case, the functionality works fine, it's just you. This is perhaps a peculiarity of the app... In order to use a "Custom" label, you don't just click on the Custom label field and start typing (which sounds reasonable). Instead, first, if you look at the list of available fields to the right, you will see that there are 5 numbered "Custom" entries. Double-click one of those to add it to the list on the left. Then you can click it once in the left list to select it, and you will see the "Custom label" field down below filled out. Now you can edit it to your heart's content, and add other fields to it with the little >> button next to it. Many (but not all I think) of the preset fields are available there, or you can access any field you want by invoking exiftool using the syntax I showed you before.

So that entry field is only active when you've selected and are editing one of the 5 custom slots.

You can add multiple pieces of data on a single line this way, but you are limited to a total of 5 "custom" lines in labels. It's a bit odd, but that's the way it is. I'm sure this made sense to Pierre when he first did it, but I confess the virtue of this approach is lost on me. Since it is not in good taste to have umpteen lines of labels, overhauling this is not a priority.

Please let me know if I'm providing useful information and if there's anything else I can provide. Your explanation clarified for me that there are several different fields in different systems that are interacting here. I appreciate your guidance. I'm learning steadily ...

Not at this time. I think Pierre needs to check if he's reading the field correctly or if the blame is on Adobe. Phil has been known to make allowances for Adobe idiosyncrasies before, so just because Exiftool can read it does not necessarily mean the file is to standard. It is certainly possible for one field to be broken in particular circumstances in XnViewMP while working elsewhere in the app; it's happened before.

Pierre might want you to supply links to some PSD and PSB files where Exiftool sees the fields and XnViewMP does not.

[tomgoodell]

Thanks for that explanation. Pasting {exiftool:OriginalTransmissionReference} into a custom field now shows the value in thumbnails + label view, so I've got my bases covered.