To reproduce:
IMatch 2025.2.4
Preferences/Background Processing/File Relations -> both (all three) boxes unticked (especially "Automatically propagate...")
Select two images
right click/Versions/Create manual version link
As soon as the manual relation is established manually data is propagated from master to version (as configured in Preferences/File Relations).
Expectation: Data is not propagated unless I intentionally propagate (F4,P)
(since I unticked automatic propagation in preferences)
This bug may have been introduced in an earlier version but I really stumbled over it and tracked it down these days.
I think the option to not propagate is no longer needed.
What does this mean?
In the newest version, the propagation goes automatically?
I hope not.
I am still on version 2025.1.14, where I do propagate with F4 - P
I'm not sure I follow. Writing back the master or doing an explicit <F4>,<P> propagates data by writing the master and then copying the changes to all versions.
When in-database elements like, rating, label and collections are propagated, which was always immediate, when I'm not mistaken? I don't recall any related change in IMatch 2025.
What exactly do you propagate and does IMatch perform write-backs to copy metadata from the new master to versions?
I have a manual relation which propagates rating, label, collections and XMP data.
When I make a new version, it gets rating, label and collections from the master immediately, but not the metadata. Metadata is only propagated when I write back the master or do an <F4>,<P>
@sinus What data do you propagate?
I think, I have misunderstood this, sorry.
I do all propagation with F4 - P. Mostly I propagate all of the metadata, rating, label and collections.
But sometimes I do not want propagate headline, description and location, because I want not, that some (difficult ::) ) clients can see all infos there.
So, I guess, for me all is good. :)
Data is automatically propagated as soon as you link images manually
- without writing back or updating the Master
- without F4-P
That's the bug.
@Sinus: so you are affected by this bug - just try it out.
@Bolitho: Thanks.
As I wrote, I am still on version 2025.1.14.
To be sure, that we are talking from the same:
I do have a raw-image, in my case a nef.
In the preferences I have set relation to automatically, and the preferences to manual.
Hence, if I create a version of this file, IMatch import the version and detects the relation and "links" the two images together.
Means, both files are e.g. viewable in the version.
But the propagation is not performed. Means, all Metadata, what are in the nef, are not in the jpg.
Then I select the nef and click on F4 - P ... after a while the propagaion is done and the version has also the same metadata, collections, labels and so on, depends on the preferences, what I have done in the versioning-propagaton-panel.
Attached my preferences.
When you propagate rating and you change the rating for the master, if background propagation is on, all versions immediately get the same rating. Else not.
The difference is that, for
manually created versions, this setting is ignored for
in-database things like rating, label, and collection. If the master you manually create a version for has 3 * and a purple label, the new manual version will receive the same rating and label.
But other metadata is not propagated and no write-back or similar is performed. If the new master has a headline and keywords, the new manual version does not get them until you write-back the master or you press <F4>,<P>.
This is how manually created versions differ form normal versions.
I'm quite sure this is how it worked in IMatch 2023 already. Need to check when I have a minute.
Update
Had a minute. This was a deliberate change I've added to the code base on February, 12. 2025.
My post for this: https://www.photools.com/community/index.php?msg=104245
Corresponding topic: https://www.photools.com/community/index.php?topic=14824
I did not check is background propagation is disabled. I will add this for the next release.