Skip to main content
E
emam-dev
Inspiring
June 13, 2017
Answered

How to identify the MXF-OP Atom files in a Premiere project

  • June 13, 2017
  • 1 reply
  • 5303 views

Hi All,

Is there any way we can go through a large project and find the MXF-OP Atom files in that project?

Is there any way to get the codec/wrapper details of the files in a Premiere project?

We are trying to achieve this using our HTML5-CEP based panel.

Thanks and Regards,

Anoop NR

This topic has been closed for replies.
Correct answer e_d_

You're not alone in thinking such functionality should be within PPro, though the providers of those third-party tools might not agree.


I don't expect it. I'm just curious (as with many other things) how it's possible that one has made the effort to implement (mostly) proper OP-Atom reading and then just stopped. One could call it an incomplete feature. I see your reasoning behind it, but from a user perspective it's a PITA, breaking workflows in many places.

1 reply

E
e_d_
Inspiring
June 13, 2017

Hi,

it is possible to determine the wrapper (i.e. file extension) and video codec of an item using

app.project.rootItem.children.getProjectMetadata()

-> for example, DNxHD is AVdn, XDCAM-HD422 is xd5c (sounds familiar? ), but it won't tell you if the clipitem really is a OP-1a or OP-Atom container. Premiere figures this out "under the hood", presumably by checking the file's internal GUIDs (which requires them to have been properly generated, otherwise OP-Atom files won't import as a single clip anyway).

E
emam-devAuthor
Inspiring
June 13, 2017

Hi,

Thank you e.d. for that info.

But as you said, we can only get the codec- AVdn, and its common for OP1a and OP Atom.

We cannot depend on that one.

Thanks and Regards,

Anoop NR

E
e_d_
Inspiring
June 13, 2017

Hi Anoop,

I know, Premiere's codec info is not sufficient for this application...What would be useful and feasible is to do a binary read of the MXF header and have the relevant byte(s) tell you what kind of essence(s) the file is containing.

(One hour of research later...)

As far as I understand it, if one looks at offset 16h of an MXF container, the byte value provided there gives the exact offset (x+1) of the OP descriptors. So if it says "83", the offset for the identifier is 84h (found this in XDCAM OP-1a, in OP-Atom generated by MC the offset is 89h).

BTW, the "magic number" for OP-1a is 06 0E 2B 34 04 01 01 01 0D 01 02 01 01 01 09 00,

whereas OP-Atom is 06 0E 2B 34 04 01 01 02 0D 01 02 01 10 02 00 00 . You might as well just regex-match for this in the first 300 bytes of the file...

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices