Robert Krueger
Forum Replies Created
-
I am not questioning the advice. The question was more asking for “yes I have had a case where camera X did not work with the card anymore because there was an additional file on it”. This sort of thing.
-
I know and respect that position. My question was rather technical in nature.
-
Off the top of my head MXF is one option but I would have to check the spec and Premiere’s list of compatible formats to find the one that’s the most versatile. Depending on what kind of codecs you work with, MXF may be too restrictive.
-
Bart,
unfortunately I only got confirmation from Adobe that those are still the options one’s got on the table. I got advice from the integrator support to do the integration internally with a custom Premiere panel but it does not fit into my workflow at all and it does not solve the problem of potentially rewriting huge files, because my understanding is, if you apply metadata to a file from within the panel using their api all happens automagically but it is still the same thing, i.e. for a mov that does not have enough free space reserved in its header, the file will be rewritten entirely.
Not 100% but pretty sure that this is correct, unfortunately. I will probably live with the rewriting and implement this using their XMP SDK.
I would like to lobby a bit, so Adobe opens up to the thought of (at least optionally) honouring sidecar files for formats that support embedding but I am pessimistic as far as my leverage is concerned.
-
Is there a way to find out by looking into the project file? I tried naively by looking for strings in the form of “10.*” but did not find anything.
-
It is called “Blender Road Movie Clip” and is contained in the Event “Updated Projects” and I can doubleclick it, then the timeline opens and has that name and is empty. I have gone through the process with other projects for which the update simply worked.
-
Thanks for looking into this.
I was afraid this was the case. Setting files to read-only is not a general option for my workflow but out of curiosity I will try.
Are Adobe people following this forum? Maybe I should post this (after a little more research) in their forums.
Cheers,
Robert
-
Thanks, I did not know that Bridge does support arbitrary metadata in a way. Not relevant for my current workflow as I am happy with the predefined schemas but valuable information indeed.
-
I know that mov supports embedded XMP. Let me explain why I am looking at the sidecar option first:
The workflow will be this: Files have already been enriched with metadata that is structurally compatible with XMP in an external DAM that stores the metadata in a database. I am working on an export function for that DAM to prepare clips for import in Premiere. This step has to work without Premiere being installed on the local computer because the roles/responsibilities are like this:
– Production partner using DAM prepares disk and sends it to client
– Client imports data from that disk into Premiere and needs to have XMP metadata available thereI could use embedded XMP metadata using Adobe’s SDK but
– Mov files would typically have to be rewritten, if not enough free space has been allocated in them when they were created and I have no control over that process and it hurts to write gigabytes of data just to add a few bytes of e.g. location, creator information
– I would have to do the additional step of SDK integration. The sidecar option I already have working
– The sidecar workflow works without modifying files and in some environments people used MD5 hashes to check data integrity which and changing the original file content would complicate all that -
So far, Prelude is not part of the workflow I am working on, so I was not planning on adding it just to associate existing metadata with the clips (that step will be automated in the DAM export). Right now I am trying to find out the limitations of Premiere to make an informed decision how to get this done in the simplest way possible.