Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Avid Media Composer Avid MC 3.5.4 – CONSISTENCY CHECK FAILURE Error

  • Avid MC 3.5.4 – CONSISTENCY CHECK FAILURE Error

    Posted by Andrew Timms on November 30, 2009 at 5:17 am

    Hi –

    Recently our editors have started getting this error in Media Composer 3.5.4.

    (The number associated with the message changes each time)

    This seems to happen when scrubbing around a timeline. Unfortunately we are a Final Cut based place and I can’t seem to find much info on this error so I’m not sure how to attack it.

    This happens in every project (RED, DV etc). Audio comes in from the soundy as wav files which I believe get imported by simply being dragged in.

    We run Apple XSAN (and have the Avid MediaFiles folder located on the root of that disk) and I can replicate this error on all our machines. They are various Mac Pros all running the same disk image (OS X 10.5.8 with QT 7.6.4). The output hardware is a Mojo SDI.

    I have an upgrade to 4.0.2 but not sure if that is going to fix my issue and I can’t break it during an edit.

    Thanks for any help –

    Andrew

    Chris Rennier replied 16 years, 8 months ago 3 Members · 11 Replies
  • 11 Replies
  • Matt Mullen

    December 1, 2009 at 12:43 am

    Is it on all machines with the same project or all projects?

    Looks like audio, if you turn off the audio does it stop?

    If you can narrow it down to a track or a clip it may be some corrupt media.

  • Andrew Timms

    December 1, 2009 at 12:58 am

    It is every project – that is the strange thing. It does it on any part of the timeline, so different media. Has done it on two jobs now.

    I can’t check the sound turn off thing right now, nor swap out the machine (it is swapped out since the last job anyway).

    I wondered if it was an XSAN thing, I’m going to try putting the media on a local HDD tonight to see if that helps.

  • Matt Mullen

    December 1, 2009 at 4:53 am

    That’s what I would do. If it is happening on every machine, every project it would seem to be a storage issue.

    How is the storage connected?

  • Andrew Timms

    December 1, 2009 at 4:54 am

    Still waiting for editor to leave..he mentioned it only seems to happen now when watching footage in reverse. (It is getting weerd now)

    Storage connected via Fibre – Apple XSAN2

  • Matt Mullen

    December 1, 2009 at 3:07 pm

    Do you know which model Mac? This is Fibre, are you going through an installed card? What slot is it installed into and is there any other hardware?

  • Andrew Timms

    December 1, 2009 at 8:11 pm

    Hi –

    Jumped on Avid this morning. Firstly I can replicate the error by playing the sequence backwards. It doesn’t do it on scrubbing but hitting J then waiting a few frames then get the error.

    I turned off all the audio layers and the problem went away – although the video didn’t play back great backwards (I’m not sure if it is meant to). It is only DV in this case (film offline).

    I also tried copying the Avid MediaFiles dir to a lacie FW800 drive and unmounting the XSAN – same error.

    The computer is this:

    and has this Fibre card:

    Fibre Channel Domain 0:

    Vendor: LSILogic
    Product: LSI7204EP
    Revision: Firmware 1.3.14.0
    Bus: PCI
    Slot: Slot-2
    Initiator Identifier: 126
    Node World Wide Name: 20:00:00:06:2B:11:15:A0
    Port World Wide Name: 10:00:00:06:2B:11:15:A0
    Address Identifier: 01:06:00
    Description: Port 0
    Speed: Automatic (4 Gigabit)
    Topology: Automatic (Point-to-Point)
    Status: Link Established
    Cable Type: Fiber Optic

    with these cards in the system

    The other video card listed is a Blackmagic Decklink HD Extreme 2. This is our slowest machine – I can replicate the problem with our Mac Pro 3,1 8 core also (same Fibre and Blackmagic card).

    Thanks for your help!

  • Matt Mullen

    December 1, 2009 at 9:13 pm

    Did Avid support have any ideas?

    I know it’s a pain but I would try removing all hardware to make sure there is not a conflict.

  • Andrew Timms

    December 1, 2009 at 9:15 pm

    To be honest – I hadn’t tried them yet as I didn’t think you got support without the support contract.

    Will give that a go next – I’ll pull the Blackmagic card out tonight to see if it helps.

  • Matt Mullen

    December 1, 2009 at 9:46 pm

    Whoops, sorry bout that. Thought you mentioned contacting support but now that I re-read the post I definitely misread the first time.

    Anyhow I think ruling out the hardware is a good thing so do that and let us know.

    -Matt

  • Matt Mullen

    December 3, 2009 at 8:59 pm

    Any luck after pulling the hardware?

Page 1 of 2

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy