Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Avid Media Composer Database errors/Media tool won’t read clips

  • Database errors/Media tool won’t read clips

    Posted by Nate Smith on April 1, 2007 at 12:05 am

    Hi all-

    Real head-scratcher I’m dealing with:

    I can’t get the Media Tool in Media Composer to load clips from a couple of the firewire drives attached to our system. The clips appear online when I load them from their individual bins, but when I open the Media Tool, I see the following prompt:

    Exception: ‘CM_NO_TRACKS_FOUND’
    An error occurred loading database.
    DRIVE 4:Avid MediaFiles:MXF: 1

    (Drive 4 being one of the aforementioned firewire drives storing media).

    Then the Media Tool will load some or none of the clips on that drive. I know the media is on this drive, because it will load from each bin, and I can see the drive is full of media files. They just won’t open in the Media Tool.

    Among the peculiarties of this scenario is that this is happens to three of four firewire drives (gRaid’s 500 gb), but not the fourth. The project is a mix of DV and HDV, so each drive has lots of clips of each. All of the clips were captured as MXF files, and the audio files are OMF’s. (I didn’t realize that the audio settings need to be changed to MXF). But again, the drive that fully loads in the Media Tool has the same mixture of MXF and OMF files. Another wierd thing is that the Media Tool will load some clips when the project format is set to 30i NTSC, and some when it’s set to HDV. But the clips will not be all DV or all HDV respectively. I can’t really identify the logic behind what’s being read on the drive.

    I’ve trashed all databases and rebuilt them. I spoke with Avid who guided me through trashing site settings and attributes, which I did. Still no dice, the problematic drives won’t load all of their media in the Media Tool. I also tried all the drives on our Xpress Pro system, but the problem is the same there.

    Any thoughts would be appreciated.

    I’m working on a Media Composer system 2.6.6 on a quad 2.5 ghz Mac G5, running 10.4.8.
    Quicktime 7.1.3
    2.5 GB SDRAM
    4 external GRAID’s attached by firewire
    No MOJO, no Adrenaline BOB

    Many thanks,
    Nate Smith

    Nate Smith replied 19 years, 1 month ago 3 Members · 3 Replies
  • 3 Replies
  • Grinner Hester

    April 1, 2007 at 11:41 pm

    Since the meridien line went to this new improved ism, media tool is just flat out buggy. Sometimes it’ll load clips and sometimes it won’t. About once a year, I simply have to throw my media folders in the trash and start over because I run out of drive space and can’t laod the remaining clips in media tool to deleat em.
    The solution for me will be to move on to FCP. I can’t afford all these bugs anymore.

  • Jon Zanone

    April 2, 2007 at 12:42 pm

    From the Avid Knowledge base:

    Trashing the Media databases did clear the error message however this only worked once the corrupt media files were deleted from the drives. One side note be sure that the user is closed out of Xpress when deleting files from the drives. This error message came about while deleting files from the drives with XPRESS still running in the background.

    I just had a problem with my MC/Meridian on a Mac; I kept having to throw away corrupted media files (you know they’re corrupted when they have a ‘+’ before the name of the file). I also had an issue with a crammed full raid array – less than 150mb. Once I freed up some space, It worked like a charm.

    I also trashed the application preference file, as well as the MCState file.

    Hope this helps

    Jon

  • Nate Smith

    April 2, 2007 at 1:24 pm

    I’ll try a few other standard media management/troubleshooting options, and I’ll definitely try and isolate any corrupt files. I’m also in touch with Avid who may come up with some additional thoughts. I’ll post if I figure anything out.

    nate

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