[IM2021] question re video XMP sidecars

[henryS]

Hello Mario, I'm looking forward to upgrading to iMatch2021 but have an issue with embedding the XMP sidecars. In one database I have 11T of mpg videos where the annotations are in XMP sidecars and I need this arrangement in this database to remain as is. I also have a second database where I don't mind to embed XMP sidecars. I presume that iMatch does not attempt to embed the XMP sidecars by default but must be told explicitly to do this? And can I allow embedding in the second database but not the first one or would the settings apply to all databases in iMatch?
Also, when you say to backup before upgrading are you referring to doing the Pack-and-Go backup or making an image backup of drive C: with the operating system and also making a backup of all the files managed in iMatch?
With thanks
henry

[Mario]

See Upgrading to IMatch 2021 which links to Importing XMP Metadata.
This should answer your questions.

IMatch now by default embeds XMP metadata in video files, like most other cameras and video editors do. It's just how the industry standard has evolved.
You can force IMatch to not embed XMP metadata in video files via the standard file format options under Edit > Preferences > Metadata 2: File Formats. Press <F1> in that dialog for more information.

When I say backup your files, I mean to backup your video files before modifying them. Pack & Go does not backup your videos or images, it is a tool to transfer IMatch databases and settings between computers. Not a replacement for a backup software.

If you have 11TB of video data, I'm sure you have at least one full backup of these videos elsewhere already.

[henryS]

Thanks for your response, Mario. I re-read the Help but am still not clear about my particular situation with 2 databases. Upon the upgrade I understand that if don't change the default setting, nothing will change in the first database with the video files unless I first run the command to embed the XMP sidecars. But what will happen if I change the metadata in one of the videos - will iMatch write back the change to the XMP sidecar or will it ask to import the XMP sidecar and embed the change in that video, without forcing to embed the sidecars in all other unmodified videos?
And will this remain the case if upon the upgrade I leave the default settings and do embed the XMP sidecars in the second database?
Things would be clearer if I knew whether the change: "You can force IMatch to not embed XMP metadata in video files via the standard file format options under Edit > Preferences > Metadata 2: File Formats. Press <F1> in that dialog for more information" applies on a per database basis or applies to all separate databases in iMatch.
With thanks
henry

[Mario]

But what will happen if I change the metadata in one of the videos - will iMatch write back the change to the XMP sidecar

IMatch now embeds XMP metadata in video files by default.
It will not ask to import the sidecar - this is why I've explained that you need to that yourself once and added a new help topic and a dedicated import command.
If you don't import the XMP data into the video file as advised but change XMP data, you'll end up with two XMP records for your video file - one embedded and one in the sidecar.
IMatch will merge the records on import, but write only the embedded XMP record. This is a situation that should be avoided.

This is independent from how many databases you have. And you should avoid managing the same files in different databases. This requires extra care and control on your side and a concise workflow. Especially if you still change metadata in these files. If you don't write back and accidentally modify metadata for the same file in two databases, one database will win in the end.

Things would be clearer if I knew whether the change: "You can force IMatch to not embed XMP metadata in video files via the standard file format options under Edit > Preferences > Metadata 2: File Formats. Press <F1> in that dialog for more information" applies on a per database basis or applies to all separate databases in iMatch.

You really don't want this. Don't work against IMatch or common industry practices.
The settings are per database but it you change anything here, I may not longer be able to support you. Or understand all possible side-effects this may have.