Hi guys,


I'm trying to export an Apple ProRes HQ and when I get to a certain point very early on in the export it comes up with this error. It's a single clip with a subtitle track and it also has a 5.1 audio track. 

I have read several posts about this error and I tried the "Video Mixdown" solution but it just came up with this error message; 

"SWDC_DodecInterface_Task;;Execute0
CONSISTENCY CHECK FAILURE !?! : [<idNum>]
The media created to this point may be unusable and/or incomplete."

I tried exporting just the audio and it was fine, so it's something to do with the video. I exported it as "Same as Source" and it was fine, the problem is I need a ProRes. I also tried exporting a ProRes from this clip in Premiere and it worked without any issues. I could go with that but I'm not overly familiar with Premiere and it's subtitling so I'd prefer to try and solve it in Avid if I can. 

Cheers,

@jimmy23: http://avid.force.com/pkb/articles/en_US/Error_Message/Consistency-Check-Failure

jimmy23:

I'm trying to export an Apple ProRes HQ and when I get to a certain point very early on in the export it comes up with this error. It's a single clip with a subtitle track and it also has a 5.1 audio track. 

The media attached to that clip's corrupt. You'll have to re-transcode, then re-insert it into your timeline.

Had this literally yesterday. I rendered all of my video-effects and one effect always remained unrendered. It was a corrupt transition.

@Isaac T

Apologies, I forgot to mention I'm exporting from an ama-linked ProRes file (the whole point of what I'm doing is adding a subtitle track), so there hasn't been any transcoding. 

What codec would I have to transcode to in order to minimise the loss of quality? Or is the fact that there's an issue with the ama-link going to prevent anything from happening?

Cheers,

@jimmy23:

jimmy23:

I'm exporting from an ama-linked ProRes file (the whole point of what I'm doing is adding a subtitle track), so there hasn't been any transcoding. 

When the export fails, try this:

1. Open the Console (⌘ + 6) and MC should tell you which clip is bad. More accurately, it'll point you directly to the media (e.g. MXF) that made your export fail. 

2. Open that MXF in VLC (http://www.videolan.org/) and locate it in your timeline. Like derDoyle said, it could even be a corrupt transition or effect.

3. Depending on what you find, try these before re-exporting:

  a. Remove and re-apply the effect or transition.

  b. Delete the clip from your timeline and re-insert it over AMA.

jimmy23:

Or is the fact that there's an issue with the ama-link going to prevent anything from happening?

I'll draw the ire of the community, but never rely on AMA / Linking as your source media. Always transcode transcode to the appropriate Avid-based codec before you begin a project. 

jimmy23:

What codec would I have to transcode to in order to minimise the loss of quality?

Depends on your flavor ProRes.

Do this:

1. Open one of your source ProRes MOV's in QuickTime.

2. Do a [Get Info] and look at the "Format".

3. Find that format in this document, "About Apple ProRes": https://support.apple.com/en-us/HT202410. Take note of the "target data rate" (e.g. ProRes 422 = 147 Mbps).

4. Click on one of these Avid docs:

  a. DNxHD White Paper (pp. 9, 10): https://www.avid.com/~/media/avid/files/whitepaper-pdf/dnxhd.pdf?la=en. Take note of the column "Mbps" (MegaBITS per second).

  b. DNxHR Codec Bandwidth Specifications: http://avid.force.com/pkb/articles/en_US/white_paper/DNxHR-Codec-Bandwidth-Specifications. Take note of the column "Data rate in MB/s for specified frame rate (exact value)" (MB/s = MegaBYTES per second. 1 MegaByte = 8 Megabits. Take the number in this column for your project frame rate and resolution and convert it from Megabytes to Megabits.)

5. Match your source ProRes MOV's Target Data Rate and frame size to the desired Avid codec's data rate and frame size. The desired codec is dependent on your project.

6. Select all clips, transcode, then re-insert into your timeline.

Sorry. I wish it were easier.

"Sorry I wish it were easier"
It wouldn't be the AVID we know and love if it was

Just to make sure that I'm taking the transcoding route correctly.
The ProRes that I have been ama-linking to has a data rate of 189.31 Mbit/s

So according to the DNxHR White Paper link you sent me, the best option would be to go for the Avid DNxHD 175 as that gives me a Mbps of 176, which is the closest match. I know that DNxHD 350x has a Mbps of 352 but that seems a bit excessive? Or is there a way to adjust it so that is specifically meets the ProRes' data rate? 

@jimmy23:

jimmy23:

The ProRes that I have been ama-linking to has a data rate of 189.31 Mbit/s

jimmy23:

So according to the DNxHR White Paper link you sent me, the best option would be to go for the Avid DNxHD 175 as that gives me a Mbps of 176, which is the closest match.

If that's what's available in your project, correct.

Best way to test: pick your most visually complex shot (think Bourne Ultimatum chase scene) and transcode that. Sounds like you picked the right one with DNxHD 175, but this way you'll know for sure.

Quick Note: DNxHD <Number> = the data rate of that codec. So:

• DNxHD 175 = data rate of 175 Mbps (MegaBITS per second), 8-bit color depth

And if you see an "x" after the number, that codec has 10-bit color depth support. So:

• DNxHD 175x = same data rate, but 10-bit color depth

So I tried to transcode it and it processed for all of 5 seconds before coming up with this error message again; 
"SWDC_CodecInterface_Task;;Execute0
CONSISTENCY CHECK FAILURE !?! : [<idNum>]"

I went into the console and this is what it says;

"DecodeFrame error: ProResCodec ERROR DECODER IN DECODE PROCESS

ProResCodec: Decode Error -28

Decode frame failed.

CChannel: error: CMError_Codec, function Execute, line 250, internal codec error string: ProResCodec ERROR DECODER IN DECODE PROCESS

DecodeFrame error: ProResCodec ERROR DECODER IN DECODE PROCESS

Exception caught in APlayer::Play - Exception: CORE_CONSISTENCY_CHECK_FAILURE, className:SWDC_CodecInterface_Task, methodName:Execute, mDecodeResult:2

FileDebugDump - bad sample: 586, length: 977296 bytes, starting offset: 0x15a99f88 in file: /Volumes/PETRUCCI 6TB_2018/2018 FEATURES/Becoming Animal /MASTERS/BecomingAnimal_PRHQ-1080-25p_51ci_180214.mov

Exception caught in APlayer::Play - Exception Exception: std::exception, what:CORE_CONSISTENCY_CHECK_FAILURE raised Quiescing in the exception handlerDIDRMapperHelperSegmented::ClearAllMappers: 0 Cleared: 1 Still Alive

Exception:

@ Thu Mar 8 09:49:14 2018"

It seems that this is an issue that can't be fixed and I'd need to request a new ProRes file to work with?

Did you try a Fast Import to rule out AMA as a problem?

Only out of curiosity, consolidation does not work and brings the same error?

Which version of MC do you work with?

Doyle

Am currently trying a fast import as I type, will see if that works.

EDIT: No issue during the import, but again when I tried to export it, I got the same error [:'(]

I'm using 8.6.4.

@jimmy23: try transcoding the clip outside of Media Composer using Compressor or MPEG Streamclip. Transcode to your project’s desired data rate and codec, then import it. Not AMA + transcode, but import. Should be a Fast Import if it matches yoir project.

Could be the file, could be your version of MC.

In MC8.7 was a Bug-Fix for transcoding/consolidating ProRes-Files and I can remember some strange behaviour in early versions regarding ProRes.

If it's possible, request a new file, maybe a DNxHD185X-file and if possible as .mxf not .mov, so you don't need to import anymore. Depends on the system the file is coming from.

If I were you, I wouldn't invest more time in re-encoding the whole file unless you have to. Depends on your position for this project.

MPEG Streamclip is slow as hell and with re-encoding you lose quality, could create shiftings in color, lose time and so on.

I think it's the file. I've gone through this process with numerous other ProRes' and there hasn't been this issue. I will try updating my Avid just to make sure though as the ProRes was sourced externally and I would have to request a new one. 

So it was the file that was the issue. I rechecked it and there was a 'blink and you miss it' glitch very early on where some distorted pixels appear for literally a frame. I've requested a new ProRes so hopefully that will fix it.

Apologies for wasting people's time. Your advice was very much appreciated though as I now know steps I can take the next time it happens!