Buddy files

[frlindla]

In my database I have dng-files, cr2-files, raf-files, jpg-files and tif-files. 

I use DxO to customize my photos. DxO creates a dop-file when edits are done to a photo.

Some questions:

1. Do you create a buddy relation for each? (Guess I need a buddy-relation when related files are moved, deleted)
2. Do I have to create a buddy relation to take care of the dop-files?
3. Maybe I haven`t seen the difference between buddy relations and versions, but I wonder if I edit a jpg-file in DxO, export the final jpg to original folder, shall I create a buddy relation or version-relation?
4. Will the final jpg with the edits be visible?

[Mario]

Buddy file relations control how IMatch 'keeps files together' during move, copy, rename and delete operations.
If you produce a "beach.dng" and/or "beach.jpg" from a "beach.cr2" master file and you want IMatch to move / rename / delete these derivative files when you move / rename / delete the CR2 file, you set up a buddy relation.

1. This depends on what you want to achieve and which files you consider to belong together

2. Most likely. If you rename only the original image but not the matching dop files, DxO will lose track

3. As said in my opening paragraph, buddy files control file system operations like move or rename. File versions control if and how IMatch propagates changes you do to the master file (metadata, categories, collections) to the versions. For example, if you add new keywords to the master file, do you want these keywords to be added to the versions too?

If you produce JPEG files from your DNG files, you usually want to cover that with a buddy file relation rule (DNG -> JPEG). This way, if you rename, move, copy or delete the DNG, the JPEG file will be moved/copied/renamed/deleted too.

If you want IMatch to propagate (copy) metadata changes you apply to the DNG also to the JPEG, setup a version rule. This also automatically stacks the DNG and JPEG file and you can show/hide the JPEG as needed.

4. If you want the DNG to "look" like the JPEG, setup the version rule as explained, and make the JPEG the 'visual proxy' for the DNG. IMatch then uses the JPEG file to display the DNG in the Viewer, Quick View Panel etc. This way you get the same look in IMatch for the DNG you get in DxO. You can also look at the original DNG if needed of course.

See: Uses

[ubacher]

..... to the DNG also to the JPEG, setup a version rule. This also automatically stacks the DNG and JPEG file and you can show/hide the JPEG as needed.

What is needed to set up this automatic stacking? In my setup this automatic stacking does not happen.
(I only have a version rule - no buddy file rule. DNG->jpg)

[Mario]

Masters and versions become automatically part of a version stack. No special action required.
You can collapse the stack via the commands provided in the version stack icon drop down menu, the context menu in the File Window or the corresponding keyboard shortcuts.

The corresponding help topic covers this in detail: Versions in the File Window

[frlindla]

Mario, what I want is to keep raw files and jpgs together if I move, rename or delete. So if I have a dng-file and a jpg of the same photo, I want both to be moved, renamed or deleted. Then I guess I have to create a buddy relation dng-jpg. So I guess this must be the case for raf-files and cr2-files too?

But DxO also creates dop-files. How do I set up such a buddy relation when I have to take care of both raw-jpg-dop?

I also wonder, if I edit a jpg file in DxO (the original file is a jpg and I adjust it in DxO), what do I have to do to get the adjusted jpg visible in Imatch? Version-relation?

[Mario]

Have you read the help topics I linked to? They explain all that in detail.

As I said, if you want to move/copy/rename files together => buddy relation.
Metadata Propagation or make one image look like another ("visual proxy") => version.

If you work with multiple master formats (RAF, DNG, CR2) you need to create buddy relations for each master/version combination, e.g. RAF->JPEG or whatever you use.
All the various files DxO places in your file system can also be configured as buddy files for the corresponding master files.

These questions have been asked and answered many times. I suggest you use the search function right at the top of this community web page to search for DXO to find all answers accumulated so far.

[thrinn]

Frlindla,
one aspect I personally was not clear about at first:
Buddy and version relation definitions are not mutually exclusive. They can (and sometimes must) be used together. For example, you can have a buddy relation from RAW to JPG which takes care of renaming, moving etc. these related files together. And at the same time, you can have a version relation, also from RAW to JPG, taking care of propagation, visual proxy stuff and such.

Another thing I want to mention because it was recently discussed here: If possible try to organize your files so that master and version share the same base folder, either by putting master and version in the same folder, or by using a sub folder of the master folder for versions. This simplifies things like automatic updating of visual proxies.

[Mario]

Frlindla,
one aspect I personally was not clear about at first:
Buddy and version relation definitions are not mutually exclusive. (...)

Good point. I've added some explicit explanation about this to both the general Relations topic and the Relation Configuration topic for the next update of the IMatch Help System.