RDD 44 ULs Parsing

A unified display of relevant technical and tag data for A/V files

Brought to you by: guillaumeroques, zenitram

#530 RDD 44 ULs Parsing

Milestone: More_attribute

Status: open-accepted

Owner: Jerome Martinez

Labels: None

Priority: 3

Updated: 2018-09-19

Created: 2018-08-29

Creator: cledwyn4

Private: No

Request to be able to parse all new ULs defined in RDD 44 - ProRes in MXF

Discussion

Jerome Martinez - 2018-08-29

Please provide a couple of files so I could verify that all is OK when I implement it (no need of all UL, just few).

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Jerome Martinez - 2018-08-29

status: open --> open-accepted

assigned_to: Jerome Martinez
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

cledwyn4 - 2018-09-17

Hi Jerome - Sorry for the delay. I've attached a frame each for 3 of the variants

ProResLT_709_Bars.mxf

ProRes_422_709_Bars.mxf

ProRes_HQ_709_Bars.mxf

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Jerome Martinez - 2018-09-17

Checking ULs, looks like that the only UL I miss in this file is "Available Representations" and it is empty.
What is missing from your point of view?

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

cledwyn4 - 2018-09-19

The Codec IDs aren't currently being parsed. See attached.
I can't tell which ProRes profile is being used from the info in the MediaInfo window

Screen Shot 2018-09-19 at 11.30.37.png

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Jerome Martinez - 2018-09-19

The Codec IDs aren't currently being parsed.

They are, but just for mapping to the ProRes decoder (and the profile is not in the ProRes frame... :( )

I can't tell which ProRes profile is being used from the info in the MediaInfo window

got it, I need to map the profile byte from MXF UL to the corresponding profile name.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Jerome Martinez - 2018-09-19

Accepted.

Warning: non-paid feature request are set to low priority, we don't know when we have time to handle it.
If you desire to accelerate the development, don't hesitate to contact us for a quotation.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

cledwyn4 - 2018-09-19

Exactly. Thanks again!

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Log in to post a comment.