Quantcast
Channel: Avid Community
Viewing all articles
Browse latest Browse all 30354

Getting lots of Consistency Check Failure errors and garbage frames.

$
0
0

Hi,

 

It's been some days now that I am getting more and more Consistency Check Failure errors and garbage frames in my Avid Projects.

 

It can happen in any project into any video track containing either a transcoded clip, a title, an Avid color correction track, or a third party effect track.

 

It will happen during the rendering of a track, or during playback of a track, at which points I'll have to check at which level the error occurs, and either re-render the effect, re-transcode the clip or re-generate the title.

 

Most of the time it's the error:

 

SWDC_CodecInterface_Task::Execute()

CONSISTENCY CHECK FAILURE !?! : [<idNum>]

 

And some times I get garbage frames with part of it intack and random noise, video glitches or pure digital garbage (Like a patch of purple noisy filler for example). Pretty much like in this thread:

 

http://community.avid.com/forums/t/136769.aspx

 

This is, as you can imagine, very frustrating, because I cannont render all my effects at once and let Media Composer alone. I need to render one track at a time and then re-transcode, re-render, or re-generate the deffective parts as I go, which is quite time consuming.

 

Nothing changed in my system recently.

 

I'm running Media Composer 8.3.1 on a HP Z400 with 25 Gigs of RAM, a 6-core W3690 3.47Ghz processor and a Nvidia Quadro 4000 video card.

 

Media composer itself is running on an Intel Solid State drive, and my work disk is connected externally through a eSata passthrough that plugs directly on one of my motherboard SATA port.

 

Should I reinstall Media Composer altogether? Should I be worring that my main video editing hard drive is showing signs of impeding failure?

Thank you for any help / advice you can provide!


Viewing all articles
Browse latest Browse all 30354

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>