-
1. Re: No XMP ID written when ingesting through file directory view.
Jennyliffer May 8, 2013 12:58 AM (in response to KGCW)Hi,
I would like to confirm that I understand your question. Do you mean you can not add marker or edit metata for files from GoPro, Canon DSLR and Sound Devices PIX recoders?
So far Prelude does not have XMP support for GoPro and Sound Devices PIX recoders. But for Canon DSLR Prelude does have XMP support. I tried this with Prelude CS6 1.0.3 on Mac 10.8.3 and after importing the Canon DSLR clip I could add markers or edit the metadata of it.
-
2. Re: No XMP ID written when ingesting through file directory view.
Jennyliffer May 8, 2013 3:24 AM (in response to KGCW)Sorry for the misunderstanding!
I tried this again. For Canon DSLR clip with 'Locked' unchecked in the file property, after ingest it with Prelude CS6, I open the clip with TextWrangler and could find the 'DocumentID' in it. But if the clip with 'Locked' checked, after ingest with Prelude you can not find the 'DocumentID' in it. So please ensure the source clip you used does have the 'Locked' unchecked. Hope this will be helpful to you!
-
3. Re: No XMP ID written when ingesting through file directory view.
KGCW May 8, 2013 3:38 AM (in response to Jennyliffer)Hi jenny.
Ok my post wasn't maybe that clear, I was talking about the unique identifier that is supposedly written in the Basic > Identifier metadata field when you import files in Prelude, Media Encoder or Premiere Pro with this option enabled :
For clips imported through specific view mode, it works just fine and they get a long random string of characters generated and written on the Identifier field. For files imported through the basic file directory view, it does not seems to work and the Basic > Identifier field ends up empty. Amongst other things, having this XMP ID avoid cache file conflict for files that do have the same file name. And as we work on multiple project at the same time on a networked storage, we do end up sometimes with different files having the same name used concurrently. No problem when they have the XMP ID, but when they do not cache related stuff tends to be acting weird (like rebuilding and piling up new .pek peak files over and over every time the project is opened, we can end up with thousands of them).
The fast and easy way to avoid this is renaming everything we're going to import through file directory view but I'd prefer being able to benefit from the automated XMP ID generation.
Everything else metada related works about fine for me.
-
4. Re: No XMP ID written when ingesting through file directory view.
Jennyliffer May 9, 2013 1:32 AM (in response to KGCW)For files from GoPro and Sound Devices PIX recoders, since Prelude does not have the XMP support so even if you check "Write XMP ID to Files on Import", there will not have XMP ID into these files.
For Canon DSLR(Canon 5D Mark III), I tried this with Prelude CS6 1.0.3 under File Directory view. Please see my screen shots below.
If you can not see the 'DocumentID' with your Canon DSLR files when you ingest the file under file directory view, please let me know!
Thanks!
-
5. Re: No XMP ID written when ingesting through file directory view.
Jennyliffer May 9, 2013 2:35 AM (in response to KGCW) -
6. Re: No XMP ID written when ingesting through file directory view.
KGCW May 9, 2013 11:17 AM (in response to Jennyliffer)I guess I still have homeworks to do regarding XMP metadata.
I'll check the Document ID field on the different flavors of files and let you know.
-
7. Re: No XMP ID written when ingesting through file directory view.
KGCW May 9, 2013 11:16 AM (in response to Jennyliffer)Ok so now that I'm looking at the correct place, every file indeed get its own document ID, but it looks like cache data has some issues when handling files transcoded to .mov Quicktime Prores. If I ingest withouth transfer, ingest with transfer or ingest & transcode to .mxf HDCAM50, my .ims files ends up full of information, including the DocumentID. When I ingest the same file from the same source with a transcode to .mov Quicktime ProRes, the corresponding .ims ends up comparatively quite empty, with the DocumentID replaced with zeros.
Transcoded MXF (I get the same on simple ingest without transcode) :
Transcoded MOV :
I there any available documentation on the way those .mcdb, .ims, .cfa, .pek and .projc works and how do they interact with XMP metadata ? I feel like I don't get it all.
-
8. Re: No XMP ID written when ingesting through file directory view.
michaelgoshey May 9, 2013 12:17 PM (in response to KGCW)Hi –
XMP is designed to be accessed directly using the free and open standard libraries. We focus on ensuring the proper metadata is delivered into the XMP standard for interchange. I would suggest you rely on XMP whenever possible instead of the non-standard internal Adobe cache files. The Adobe cache files and project files can change at any time (format and content) and thus leave you with no access to the information you were hoping to find.
However, I am very curious why you are hoping to use the mcdb and other cache locations instead of XMP. Is there something missing from XMP you are hoping to use?
Thanks –
Michael
-
9. Re: No XMP ID written when ingesting through file directory view.
KGCW May 9, 2013 2:20 PM (in response to michaelgoshey)Hi michael.
Thank for your interest. I guess I went even more unclear than I was in my first post.
My initial issue was that some .pek files were continuously getting new versions of them written (with a "-1" appended to their file name) every time the projects containing their related video files were opened. It looks like Premiere keep "forgeting" were the .pek fils are and generate new one each time. I have checked "Save Media Cache files next to originals when possible" so those .pek files are with their associated files, not in the common cache folder. I noticed that it happened on files sharing the same file names and that renaming the troublemakers solved the issue. Those were almost all transcoded .mov QT ProRes files originating from GoPros.
While looking into this issue I noticed that files originating from Panasonic AF-101 did not have the issue while having similar names too (00000.mov, 00001.mov and so on). I saw in Prelude that they had their Basic > Identifier XMP field filled up while the files coming from GoPro and Canon DSLR did not, so I jumped to conclusions about XMP ID not being correctly writtent onto those and this being the cause of the issue. I was wrong, the XMP ID is correctly written on every files.
I then turned myself to the .ims and .mcdb files to see if I could spot something odd that could explain the issue, but as I don't know much about the way they work, I was only able to find what is shown in my two screengrabs : .ims files related to transcoded .mov QT ProRes (99% of the video files we work with at the moment) seems empty compared to .ims related to the very same file ingested or transcoded in another way.
I'm hopefully not trying to use the Premiere cache files to do anything Metada related (and I don't miss anything with XMP, I even wish that it could become a standard for metadata interchange), but I really do like and want to understand how things work under the hood.










