versionning

Post Reply
babarnc
Posts: 30
Joined: 20 Jun 20 12:13

versionning

Post by babarnc » 01 Mar 21 22:17

Hello,
I am testing the v6 espescially the versioning
I had indeed some issue with latest version that would systematically remove the lightroom edits from the files (i.d: make all versions share the same development setting = all versions become the same)
So far it looks much better, I have only seen one strange xmp modification that I need to track down (not sure the versioning did it).
All the other XMP modification followed my settings so that I could change some value while retaining the development setting intact.
So that is really great.
However when I asked to cascade image details the development setting were then overwritten even though the help file says otherwise:
Cascade Image Details; this will copy all non-technical and descriptive
metadata from XMP to all images in the set.
unless you consider development settings to be non-technical.

It is no more a big issue for me as with last version of photosupreme but if it is a bug it would be nice to correct it or update the documentation accordingly

Regards

Hert
Posts: 6799
Joined: 13 Sep 03 7:24

Re: versionning

Post by Hert » 02 Mar 21 12:16

babarnc wrote:
01 Mar 21 22:17
unless you consider development settings to be non-technical.
You can create a text file in PSU's app data folder. Name the file XMPTagCascadeIgnoreList.dat and add whatever you'd like to have ignored on cascade, in this case add a line crs:* to delete all crs data.
Then restart PSU because PSU reads the content of the file on startup.

babarnc
Posts: 30
Joined: 20 Jun 20 12:13

Re: versionning

Post by babarnc » 02 Mar 21 19:51

Great thank you, I will try that. Mean while I find this "hidden" functionnality quite nice could be exposed in the help file.

babarnc
Posts: 30
Joined: 20 Jun 20 12:13

Re: versionning

Post by babarnc » 03 Mar 21 20:51

Hert wrote:
02 Mar 21 12:16
babarnc wrote:
01 Mar 21 22:17
unless you consider development settings to be non-technical.
You can create a text file in PSU's app data folder. Name the file XMPTagCascadeIgnoreList.dat and add whatever you'd like to have ignored on cascade, in this case add a line crs:* to delete all crs data.
Then restart PSU because PSU reads the content of the file on startup.
Hello I tried your trick but I may have done something wrong as it did not work

1. I did put the file here:
20210303 20_39_52IDimagerSystemInc.png
20210303 20_39_52IDimagerSystemInc.png (20.66 KiB) Viewed 502 times
and added the exact following lines
crs:*
crss:*
Indeed using exif tool I found out that crss is almost a copy of crs, and when cascading it is almost completly removed (id becomes identical to the crss content in the file I cascade the metadata from)

But the file does not change the behavior of psu
note that my catalog is not in the
appdata/Local/IDimager Systems, Inc/
Location

bimo
Posts: 125
Joined: 29 Aug 07 22:34
Location: Germany

Re: versionning

Post by bimo » 10 Mar 21 16:30

That doesn't seem to work for me either.

I wanted to exclude a custom field:

Code: Select all

xmp:icd:x_ColorIndicator
Is this definition correct?
Michael

Post Reply