I'm missing Metadata

Hello!

I use PhotoScape X to edit and catalog photos, which I later use to combine with clips in Davinci Resolve. The problem I'm having is that DR doesn't display the same metadata fields that I see in PhotoScape X. I was specifically interested in the keyword and comment fields, so I could easily generate smarts bins with those tags in DR.
Unfortunately, I can't see what I recorded in the other application. Is it possible to expand or change the visibility of the metadata in DR to see those fields, which appear to be opaque?

Note: Perhaps a simple plugin or script?

Tanks!

Google traslator

An interesting problem! This might be a good question for tomorrow's Python Scripting in Resolve class.

What format are the photos and what are you using to read their metadata?
I am wondering if photo metadata is different than video metadata.

/me scurries off to search for 'metadata' in The Manual...

An interesting problem! This might be a good question for tomorrow's Python Scripting in Resolve class.

What format are the photos and what are you using to read their metadata?
I am wondering if photo metadata is different than video metadata.

/me scurries off to search for 'metadata' in The Manual...

As I mentioned, I use Photoscape X to catalog and edit photos. The photos, in this case, come from my Samsung A70 smartphone. Interestingly, the fields I edit in the app appear with the same label in DaVinci Resolve. In the app, the metadata that appears is related to the camera, shooting parameters, GPS position, and the ones I edit, which are Keywords, Comments, Author, etc., all appear in the DR tab, but they appear empty. It's as if the metadata has another layer not visible to DR.

IN PHOTOSCAPE X



IN DAVINCI RESOLVE

I think I know what can happen, and it's not good...

According to my "friend" Gemini:

"In DaVinci Resolve, the metadata you edit on a clip within the timeline (e.g., on the Edit page) or in the Master section of the Media Pool is associated with the instance of the clip within your DaVinci Resolve project, not directly with the original media file on your hard drive.

This means:

Metadata changes within your DaVinci Resolve project are NOT automatically written to the original video file on your hard drive (the "source file"). This is by design, to protect the integrity of your original files.
If you import the same original file into a new DaVinci Resolve project, it won't have the metadata you added in the previous project, unless you specifically export and import that metadata.
How to Handle or "Transfer" Metadata
While there's no direct "automatic transfer" to the source file, here are some options:

Export Metadata from DaVinci Resolve (for import into another project or software):

You can export metadata from clips in the Media Pool or from a timeline. This is typically done in formats like CSV, ALE (Avid Log Exchange), or XML.
For the Media Pool: Go to File > Export Metadata From > Media Pool or Selected Media Pool Clips.
For a timeline: Right-click on the timeline in the Media Pool, then Timelines > Export > ALE or Edit Index (which can export metadata in CSV).
These metadata files don't modify the original file, but they contain the information you've added and can be imported into other Resolve projects or other editing software that supports these formats.
Render/Export the Clip with "Burned-In" or Embedded Metadata (only for output files):

When you render your project or individual clips on the Deliver page, DaVinci Resolve allows you to embed certain metadata into the output file. This means the metadata will be part of the new file you create when exporting, but not the original.
On the Deliver page, in the advanced export settings, look for options like "Data Burn-In" or "Write metadata to file" (if available for your output format). This is useful for dailies or review files.
Using the Scripting API (more advanced):

DaVinci Resolve 19 (and later versions) has improved Python scripting support, allowing you to get and set custom metadata per clip. This could be used to create a script that reads metadata from clips in your project and then manipulates or saves it in an external format. However, this still doesn't rewrite metadata directly to the original file on your file system.
Why Original File Metadata Isn't Directly Edited
The philosophy of DaVinci Resolve and most professional editing software is non-destructive workflow. This means they don't alter the original source files. The metadata you see and edit in DaVinci Resolve is stored within the Resolve project database, linked to that media file's reference within that specific project.

If your need is for the source media file itself to contain that metadata, you would need to use an external tool designed for file-level metadata editing (like ExifTool or other software utilities specific to video metadata, if the file format allows it and is recognized by these tools). DaVinci Resolve, by itself, does not do this automatically....."

In short:
DR reads the metadata it's interested in, and in testing, it only reads and shares the "Description" field if I add metadata in the PhotoScape X application. It's the only editable field they share. It's something, and you can create smart bins with this field.
Unfortunately, all editable metadata within DR isn't propagated to the original external file, so I can't tell if any other fields in the "Plans and Scenes" section would be visible in another application. "Metadata written in DR stays in DR"... it could only be exported in CSV or similar...
It's a shame,
because the editable fields in PhotoScapeX are perfectly visible, even in the file details within the macOX finder.

metadata in the Finder



metadata in the photoscapeX



same metadata in DR ("Description" from editable fiel visible)




first small disappointment.... we will continue investigating....

[Shrinivas Ramani]

DaVinci Resolve never changes underlying files from the media pool or the timeline.

A media pool listing is not a file - it is a media interpretation record with a file path. You can change the image / video to be interpreted as vertical, or as 60 fps, or with super scale or a specific LUT etc. You can add additional file paths - like for external audio or mattes or proxies. These are not written back to the main file path.

The media metadata helps with searching, sorting and classifying within the application. For your use case, consider exporting the metadata and translating using third party apps (or scripting as Stephen suggests).