Specs: Avid MC 3.01, OS 10.4.11, QT 7.6
Following a CM_INVALID_TRIM error and selecting "Quarantine All", Avid MC quarantined 881 mediafiles. - moving the 881 mediafiles from the quarantine folder back into the original media folder resulted in Avid putting them back into quarantine. - copying the 881 from an external HDD backup made six days earlier into the original media folder also resulted in quarantine.
- attempt at moving to another Unity partition resulted in same
- attempt at moving 2 of the 881 to an external HDD (non-Unity), resulted in same
Other than corruption, why would the Avid quarantine these 881 files? Have these files been corrupt since they were created and the Avid just noticed this now? It seems odd that copies made 6 days earlier are equally corrupt as the originals that were working fine until last night's de-syncing. If the 6-day-old copies inherited their corruption from the originals, then why were the originals not being flagged for quarantine these six whole days? Four Avids working Monday-to-Friday offered plenty of opportunity for scanning and detecting any corruption that existed, or would it? It shakes my confidence in our media backup practice when the backup proves equally quarantinable. Here's the unity error:
Exception: 'CM_INVALID_TRIM' An error occurred scanning the file 'media15:Avid MediaFiles:MXF:SYSTEM 5.1:MUS-LilyAlA02.C69524A6FACDC.mxf'. Action: File 'Quarantined'. New File Location: 'media15:Avid MediaFiles:MXF:SYSTEM 5.1:Quarantined Files:MUS-LilyAlA02.C69524A6FACDC.mxf'. Action: 'Quarantine All' was select ed. See below for information on files that were Quarantined.
Here's the external HDD error:
Exception: 'CM_INVALID_TRIM' An error occurred scanning the file 'BE2_BACKUP02:Avid MediaFiles:MXF:1:05 Everything - Mic4A4B9E98.mxf'. Action: File 'Quarantined'. New File Location: 'BE2_BACKUP02:Avid MediaFiles:MXF:1:Quarantined Files:05 Everything - Mic4A4B9E98.mxf'.
CM = Composer Manager.
Based on the error above I suspect you have a corrupt precompute. Have you tried trashing the Media Data Bases on the workspace? If that does not clear the error you might have to perform a divide and conquer to track down the offending culprit. Draw a line in the sand when the problem began happening and isolate the clips and or precomputes occuring post when the error began happening.
HTH
I tried trashing the media databases on that partition and the rebuilt ones also ended up quarantining the same 881 files. I've tried adding single random files from the quarantined 881 back, but each was quarantined also, so I had gatthered that the rest must be corrupt. I can try more single random files adds to see if any of the 881 aren't corrupt. If Avid scans the folder and keeps quarantining the same 881 files, doesn't that mean that all 881 are corrupt? Or does it scan them alphabetically and once it hits a corrupt file #1000, it just automatically assumes that the 880 that follow it are corrupt also?
I haven't tried adding the files to another system's workspace yet, so I'll try that today. Maybe another Avid can digest these mediafiles.
A bunch of the files look like songs that were batch-imported. Can batch-importing lead to corruption?
Is there a way to batch import which won't lead to quarantined media?
We re-batch-imported the quarantined files. A week later a quarantine of 583 files erupted. Avid doesn't seem to like our wav/aiff music library. Going to my external drive, when I restore any of these 583 mediafiles copies to the unity, they are immediately quarantined as well.
Why does the Avid hate our music library?
Exception: 'CM_INVALID_TRIM'An error occurred scanning the file 'media18:Avid MediaFiles:MXF:SYSTEM 5.1:MUS-LilyAlA02.C69F74A79FC8A.mxf'. Action: File 'Quarantined'. New File Location: 'media18:Avid MediaFiles:MXF:SYSTEM 5.1:Quarantined Files:MUS-LilyAlA02.C69F74A79FC8A.mxf'.
I often get this message if I have to rescan a drive with audio precomputes on it. In my case MC seems not to like the precomputes generated by the Time Shift or Time Compression Expansion Audiosuite plugin. Nevertheless, if I click Ignore All, all my audiosuite renders remain online and accessible. I'm sure this isn't Avid-recommended, and may not work in your case, but for me I've found that sometimes MC wants to quarantine perfectly good media, and not letting it do that seems to do no harm.
I also find that my Media Composer 7.02 does not like precomputes/ renders of audio files with audio suite DAE effects such as reverb. And especially does not like audio renders where i have applied EQ and DAE/Reverb.
Those precomputes start being shown as corrupt during a database rebuild and giving me CM invalid trim errors and, in the timeline I then get a spinning beachball and a "AMDConsumer::Preload() Error [0] unable to: Preload Audio Samples: numSamplesToPreload"
Just thought i would add this info here in case it helps someone else.
Also perhaps my workflow is incorrect & i should not be layering effects on the same audio clip??
I'm still getting this error five years later:
Exception: 'CM_INVALID_TRIM'
An error occurred scanning the file '/Volumes/2TB One/Avid MediaFiles/MXF/301999//SH 301 LocA03.CFF6D53D161D0.mxf'.
Action: File 'Quarantined'.
New File Location: '/Volumes/2TB One/Avid MediaFiles/MXF/301999/Quarantined Files/SH 301 LocA03.CFF6D53D161D0.mxf'.
The media is a transcode of audio I did yesterday. I moved the media from the MXF/1 folder to the MXF/301999 folder and this error came up asking me to abort / quarantine / quarantine all / ignore / ignore all. If I ignore all the media is playable but as soon as I toggle out of the application and back again I get this prompt again. If I choose quanatine all the sequence with the media won't play
Exception:
@ Fri Jul 25 11:15:13 2014
• File 'SH 301 LocA02.CFF6D53D161D0.mxf' not found.
How could this media become corrupt in one day? I will re-transcode and hope this goes away.
P.S. When I re-transcode and put the re-transcoded media into the MXF/301999 or MXF/301998 folder the quarantine prompt comes up again. Avid doesn't like transcoded media? I am now re-installing the software.
P.P.S. re-installing the software didn't work. I guess trancoded audio from an AMA quicktime doesn't like to change MXF folders or else it becomes unscan-able and goes into quarantine. Imported (non-AMA style) the audio and tried to relink and that didn't work so I ear-matched it all back into the cut, cut-by-cut. Very aggravating. Wish there was a way to make transcode work and wish there was a way to relink imported audio when transcoded audio doesn't work. Not a lot of options to work with here.
I just AMA / transcoded about 2,000 music files to create a new music library. I'm using Michael and Justin's MUS-ID software, which is brilliant (www.mus-id.com). I recommend it to everyone.
Unfortunately, when MC goes to re-build database files for the folder I have that media in, I get CM_INVALID_TRIM errors. I hit IGNORE ALL and it seems to re-built just fine. But I'm wondering why the Avid hates these files? I have the same problem with my sound FX library. Lots and lots of small audio MXF files bunched together.
One fix I have found is that if I AMA and transcode in to grab metadata, then batch import all the media again once they are in I stop getting errors. I have done that with SFX before and it's worked. Haven't done it with the music library yet. I just wish I knew why this happened in the first place. PS I'm on MC 7.0.3.
2 guesses:
1. AMA AutoDetect isn't guessing correctely?
2. AMA generally isn't used for audio files.
Must think of something clever to go here...
© Copyright 2011 Avid Technology, Inc. Terms of Use | Privacy Policy | Site Map | Find a Reseller