Are there any recommendations for best practice regarding buddy files

[fisketjon]

I have currently my image files structured like this simplified example

2024 (contains one folder for each month)
  2024-01 (contains one folder for each camera used)
     camera1 (contains raw and or jpg files when there is no raw)
        converted (contains jpg files for the raw files in the parent folder)
     camera..n

After fiddling a bit with the relations I wonder if it's better to have the buddy files in the same folder. I've tried multiple times but seems unable to get Collections to show any Buddy files, I just get versioning.
By the way: Clicking "Defaults" in the Relations definition didn't seem to give me the initial setup I had with CR2, CR3 etc with B / V on alternate rows.

I also have a number of TIF files from film scanning where I would like to treat TIF/jpg pairs like raw/jpg pairs.

When stacking raw/jpg pairs I would prefer to see the jpg, as some of them may have been edited for various reasons, e.g. to level the horizon.

[Mario]

It is always helpful when you explain how you setup your buddy rules ("I tried multiple times" is not helpful, because it does'nt explain what you tried, which rules you have defined, which folders you let IMatch check for buddy files).

You can describe the details or just make a screen shot of the dialog box and attach it to your reply.

When I recall the functionality of the Defaults button correctly (I did not touch this code for many years) it removes all definitions and reloads the default definition IMatch creates.

[hluxem]

 I've tried multiple times but seems unable to get Collections to show any Buddy files, I just get versioning.

I don't think there is a collection for buddy files. In my case they are xmp and dop (Photo Lab) files without a need to display them. They are managed in the background when you move or rename the master file. I don't worry about the buddy files and for me there is no need to have them displayed. I think if you want them displayed, you will need to define them as buddy files and parallel as a version. If you want to check your definition, just rename a master and check in Windows Explorer if the corresponding file got renamed.

Since buddy files usually have to be in the same folder as the master file you don't need to worry about searching in sub-folders. There

I think it's best to have the buddy files in the same folder, that way the rename, move and copy of the master file works as expected. Don't know how Imatch could deal with move if they are in different folders. 



Heiner

[Mario]

There is no collection. But you can use variables like {File.BuddyFiles} to see if and which buddy files a file has.

Keeping buddy files in the same folder as the master file is a good idea, if possible. This avoids issues like IMatch having to create folders on-the-fly when you move master files into different folders. IMatch can handle a lot, but it's usually best not to stress things or to setup potentially fragile buddy relation constructs. IMatch cannot always prevent you from shooting in your own foot.

If you have no choice (e.g. a RAW processor insisting in creating buddy files in sub-folders), then you have to. If you control where the buddy files are stored - simpler is better!

[fisketjon]

I wonder if I have misunderstood what buddy files are.
I have always set my Canon cameras to record RAW+JPG. Are these file pairs "buddies" or just versions?

Njål

[JohnZeman]

Versions if that's what you want.

For me a typical buddy file usually isn't an image of any kind, it's usually one or more text files the raw processing program will create while processing the raw file.

For example I use ON1 Photo Raw 2025 as a raw processor, while processing a raw file ON1 creates a text file with the same name as the image but with an .on1 file extension.  That .on1 file is one of my buddy files as are files that end with .xmp

[Mario]

I wonder if I have misunderstood what buddy files are.
I have always set my Canon cameras to record RAW+JPG. Are these file pairs "buddies" or just versions?

Njål

You make a file a buddy file (in your case, probably the JPG) if you want IMatch to rename, move, copy, delete the buddy file when you rename, move, copy, delete the master (NEF). That's the purpose of buddy files.

Some RAW processors create configuration/setting files which must use a particular name derived from the image. Or the must be in the same folder or a sub-folder of the folder containing the image. Else the relation breaks. This is also a use-case for buddy files.

You make the JPG a version if you want to automatically propagate (copy) metadata, collections, categories etc. from the master to the version. For example, if you give the NEF 4 starts, IMatch can also apply 4 stars to the JPG. Or when you add a title and description to the NEF, IMatch can mirror that in the JPG if you setup a version relation.

You may want either one or both. This is why a version is not automatically a buddy file.

[thrinn]

I have always set my Canon cameras to record RAW+JPG. Are these file pairs "buddies" or just versions?

A Buddy relation is useful for pairs of files sharing the same name, but different extensions. With a Buddy relation, we can make sure that renaming or moving the "master" (RAW, for example) also renames or moves the buddy JPG file accordingly.
A relation of type Version, on the other hand, is useful for metadata propagation. Or to use the JPG as a Visual proxy to be displayed instead of the RAW.

For the use case of RAW/JPG pairs coming out of camera I did set up both: A Buddy relation to make sure that renaming the master RAW also renames the JPG. When ingesting new files, renaming the generic IMG_1234 according to my personal naming convention is the first step, so I want to make sure that RAW and JPG end up with the same target name. That's what a buddy relation ensures.

But then, I also want to propagate some metadata, categories etc. from the RAW to the JPG when I set this information afterwards. So, a second relation rule, this time of type Version, again linking the RAW to the JPG, takes care of that.

Note that it is not uncommon to use Buddy and Version rules in parallel for the same sets of files because they serve different purposes.

[sinus]

I wonder if I have misunderstood what buddy files are.
I have always set my Canon cameras to record RAW+JPG. Are these file pairs "buddies" or just versions?

Njål

I never really understand, what buddies are. 
Even if I read the comments here. Must be a gear in my head, what does not work correct. 

I use the same like you, raw + jpg, only with a Nikon.  I use the jpg as a version, always. I do then propagate some data from the raw to the version.

Never had a problem. 

[Mario]

I never really understand, what buddies are. 

If you rename the NEF, the JPG will not be renamed. Unless you make the JPG a buddy file of the NEF.
Same when you move the NEF in IMatch. IMatch will not move the JPG, unless you make it a buddy file.

Of course you can always manually rename or move both files - since you can see them in IMatch.

But when you work with buddy files not indexed by the database, like settings or config files, you won't even notice that your renaming or moving of images leaves files "behind". Or when you copy an image, the corresponding config file will not exist unless you copy it manually in Windows Explorer.

Not every IMatch user needs buddy files. I find them really important, because I don't have to take care myself that derived files I create from a RAW are renamed, copied, moved or deleted with the RAW. I let IMatch do that.

[sinus]

Thanks, Mario

Now even I understand this. I think. 
Means, if I want rename a jpg, to remember me, what it is, like cutted, or changed the contrast and so on, with adding a letter at the end of the filename  ... than this could not be a buddy-file.

Then this must be a version. 

If this is true, then I understand it now. 

[fisketjon]

Part of what confused me is that I expected a Canon buddy collection inside the Relations->Master Collection; and found none.

However I tried to move one of my old CRW files to a new folder, and the corresponding jpg went along, so I must have done something right.

Thanks for helping!

[Mario]

There are only collections for Masters and Versions, not for buddy files.