Known Participant

Answered

AS-11 file fails AQC due to incorrect Coding Equation

Forum|Forum|3 years ago
November 9, 2022
6 replies
4436 views

MacOS Ventura

Exporting an AS-11 from Premiere Pro v23.0

When testing with the AQC from Telestream (Qualify) it reports the following error:

Found 1 structural problem(s) with AS-11 UK DPP conformance: - Picture Essence Descriptor item 'Coding Equations' must be [060e2b34.04010101.04010101.02020000] (when present) but was [060e2b34.0401010d.04010101.02020000]

The second part of the descriptor is not what it should be. This is, I am told, an issue in the exporter from both PPro and MEnc and reported since at least 2019. It is embedded in the .mxf and cannot be edited externally. As this is a key element of getting programmes to broadcast it is essential that this gets fixed to live up to the 'Pro' part of Premiere's name.

This topic has been closed for replies.

Correct answer Kevin-Monahan

Hello @Mr Seaniepie, @rynprc, and @Chelsea27503698q32v,

Thanks for the messages, everyone. The team says the bug is with VidChecker for ACQ.

Unfortunately, Vidchecker isn't correctly identifying the UID; the color equation settings are showing as unknown instead of 709.
The PDF of the tool's output shows that Premiere Pro has the codingEquation set to CodingEquations = [060e2b34.0401.010d.04010101.02020000],
VidChecker shows that the 8th value in the UID should be 0x01 instead of 0x0D.
The SMPTE ST-400 doc states that the 8th byte represents a version number.
VidChecker is expecting a hardcoded value of 0x01, which is incorrect.

I hope that explains the anomaly. Please let me know if there's anything else I can do to assist with this problem. Thank you so much for your patience in receiving a response. Please take care!

I will move the post back to Discussions.

Thanks,

Kevin

michaelm11605974

Known Participant

I'm having this issue also - I'm not sure if it's really Vidcheckers fault as the 'Color Space' from Adobe AS-11 files are showing as 'Unknown' in other metadata apps....

Mr SeaniepieAuthor

Known Participant

It comes up as 'unknown' only because these other metadata apps have not hardcoded Adobes preset [060e2b34.0401.010d.04010101.02020000] into their software as being from Adobe. Perhaps you could send this to those developers too along with a link to this thread so they can make the necessary adjustments.

michaelm11605974

Known Participant

It's not really up to us the users to make Adobe applications compatible with industry standard software. Adobe should be testing it against software like Vidchecker when they're making an DPP export preset. It's next to useless if Vidchecker won't accept it when it accepts Avid AS-11 files.

Kevin-Monahan

Correct answer

Community Manager

Hello @Mr Seaniepie, @rynprc, and @Chelsea27503698q32v,

Thanks for the messages, everyone. The team says the bug is with VidChecker for ACQ.

Unfortunately, Vidchecker isn't correctly identifying the UID; the color equation settings are showing as unknown instead of 709.
The PDF of the tool's output shows that Premiere Pro has the codingEquation set to CodingEquations = [060e2b34.0401.010d.04010101.02020000],
VidChecker shows that the 8th value in the UID should be 0x01 instead of 0x0D.
The SMPTE ST-400 doc states that the 8th byte represents a version number.
VidChecker is expecting a hardcoded value of 0x01, which is incorrect.

I hope that explains the anomaly. Please let me know if there's anything else I can do to assist with this problem. Thank you so much for your patience in receiving a response. Please take care!

I will move the post back to Discussions.

Thanks,

Kevin

Kevin Monahan - Sr. Community & Engagement Strategist – Pro Video and Audio

rynprc

Participating Frequently

Hi @Kevin-Monahan & team, thanks for looking into this.

https://registry.smpte-ra.org/view/draft/labels_view.html defines 060e2b34.04010101.04010101.02020000 as ITU-R BT.709 Coding Equations. 060e2b34.0401010d.04010101.02020000 is not a defined label.

It should be noted that this is relating specifically to the DPP AS-11 specification, which does request 060e2b34.04010101.04010101.02020000

A real world example of this in a spec can be found in the Sky spec which is publically-Googleable - https://static.skyassets.com/contentstack/assets/bltdc2476c7b6b194dd/blt109e419dd7c40d1d/640b382d42ee69354723919b/Technical_Specification_for_Delivery_of_Content_to_Sky.pdf

michaelm11605974

Known Participant

Hi Kevin,

Sorry I didn't loop back on this. We're actually outside Vidcheckers support at the moment, and I couldn't justify renewing for this.

I would be interested in any update from the team on my above note though. I'm stull unconvinced this is a Vidchecker issue.

Re-wrapping the files in the out of support DPP App fixes it - which to me shows it's not a vidchecker issue, as my work doesn't have the same issue with Avid exports or by using the DPP App.

Kevin-Monahan

Community Manager

Hello @Mr Seaniepie,

Thanks for the message. It’s been a long time since you filed this bug, and I apologize for the lack of a response. Are you still having this issue? If so, the team will need more information from you to reproduce the bug. Can you provide the information required here? How do I write a bug report?

I'll move your post to the Discussions board while we await your information.

Thanks, 

Kevin

Kevin Monahan - Sr. Community & Engagement Strategist – Pro Video and Audio

R Neil Haugen

Legend

This seems to still be happening. Moved this to the Bugs section of the forum.

Neil

Everyone's mileage always varies ...

Mr SeaniepieAuthor

Known Participant

MacOS Ventura
Exporting an AS-11 from Premiere Pro v23.0
When testing with the AQC from Telestream (Qualify) it reports the following error:

Found 1 structural problem(s) with AS-11 UK DPP conformance: - Picture Essence Descriptor item 'Coding Equations' must be [060e2b34.04010101.04010101.02020000] (when present) but was [060e2b34.0401010d.04010101.02020000]

The second part of the descriptor is not what it should be. This is, I am told, an issue in the exporter from both PPro and MEnc and reported since at least 2019. It is embedded in the .mxf and cannot be edited externally. As this is a key element of getting programmes to broadcast it is essential that this gets fixed to live up to the 'Pro' part of Premiere's name.

rynprc

Participating Frequently

For what it's worth, & Adobe should fix this regardless, it can be externally edited. Either by running the file through the out of support DPP app (very slow) or using AMCDX to change the tag information in the header (very fast).

Pretty farcial that this is still happening though.

Kevin-Monahan

Community Manager

Hi @rynprc,

I have asked the team if they are working on this issue. If not, I'll file your bug internally. Let's move this post back to the Bugs forum, then.

Thanks,

Kevin

Kevin Monahan - Sr. Community & Engagement Strategist – Pro Video and Audio

R Neil Haugen

Legend

@Bruce Bullis or @Fergus H would be the people to check with on this.

Neil

Everyone's mileage always varies ...

Mr SeaniepieAuthor

Known Participant

No response from @Bruce Bullis or @Fergus H

Do Adobe look at these for bug reports?

R Neil Haugen

Legend

Bugs are still technically filed on their Premiere Pro UserVoice system. Though they are migrating over to here at some point apparently. They've done so with a couple other apps.

Neil

Everyone's mileage always varies ...

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded