raw, file relations, buddy files, stacking

[hannes_hab]

1 I it recommended to use the FastPictureViewer Codec Pack? I use nikon and panasonic cameras (raw/jpg)

2 concerning relations (new database - file relations / changing relations): why must I define relations/file types every time i create a new database - would be nice if I could do that once (I always have to add xxx.nef.xmp and panasonic lumix .rw2 and the relation with this raw file - can I save these relation for the software or can I copy these from database to database?

3 buddy file .jpg does it mean that that there is a way to automatically do changings (Metadata?) in the raw also in the .jpg?

4 stacking and auto stacking: is there a feature where I only can see the raws and the .jpgs (I always shoot raw+jpg) are hidden?

[Mario]

1. No. This codec pack is outdated and has been updated the last time many years ago.
Where did you find the recommendation? In the IMatch help somewhere?

The WIC codecs integrated in Windows handle most RAW formats. If not, IMatch will automatically fall back internally to use LibRaw.

2. Relations are database-specific. Note than 98% of all IMatch users have only one database.

3. Buddy files don't do anything with metadata. Versions do. Please read File Relations: Versioning before you start propagating metadata, there are potential issues you need to consider. This is a feature for advanced users.

Usually you need buddy files (to keep the master and versions together during rename, move, copy, delete). Versions are optional.

4. You want to see only the RAW but not the JPEG?
This is automatic when you make the JPG a version of the RAW. See the documentation for versioning linked to above. Version stacks are explained in Version Stacks You can make versions just for this purpose, or also for propagating categories, rating, label or other metadata from the master to versions.

[hannes_hab]

thank you Mario!

2. Only one Database. For office and privat, photo and data. And searching/dividing with categories ... Is this the better way than to save in different databases? The bigger size is no factor/problem?

4. For raw and jpg I have seen that I can do this with a filter (hide buddy-files).

[Mario]

3. Typical IMatch databases are between 100,000 and 300,000 files. Large databases can have 500,000 to 1 million managed assets.

4. Whatever works for you. If you don't need versions, use the filter. If you need versions, they will be stacked automatically.