This IS the Avid L2: [Avid-L2] Re: Help for audio files quarantined with CM_INVALID

Saturday, February 9, 2013

[Avid-L2] Re: Help for audio files quarantined with CM_INVALID_TRIM error

In tests I did a while back there was a Resolve setting having to do with maintaining reel names and other metadata necessary for later relinking in Avid after a round trip. I haven't played with it in a while but I'm sure somebody will know the exact settings to make sure are set. Not sure if that will solve your issue but the inability to relink might be related to those setting(s).

--- In Avid-L2@yahoogroups.com, "Terence Curren" wrote:
>
> Or Blackmagic could just buy Avid and finally integrate new tools into the color corrector. :-0
>
> --- In Avid-L2@yahoogroups.com, Bogdan Grigorescu wrote:
> >
> > Thanks for following up on this Michael. it should save others tons of time and grief.
> > Hopefully Avid will be able to fix it in a patch release.
> >
> > BG
> > www.finale.tv
> >
> > --- On Sat, 2/9/13, Bogdan Grigorescu wrote:
> >
> > From: Bogdan Grigorescu
> > Subject: Re: [Avid-L2] Help for audio files quarantined with CM_INVALID_TRIM error
> > To: Avid-L2@yahoogroups.com
> > Date: Saturday, February 9, 2013, 12:37 PM
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > Â
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > --- On Sat, 2/9/13, Michael Brockington brocking@> wrote:
> >
> >
> >
> > From: Michael Brockington brocking@>
> >
> > Subject: Re: [Avid-L2] Help for audio files quarantined with CM_INVALID_TRIM error
> >
> > To: Avid-L2@yahoogroups.com
> >
> > Date: Saturday, February 9, 2013, 12:34 PM
> >
> >
> >
> > Â
> >
> >
> >
> > I've identified the source of most (perhaps all) of these errors I've
> >
> >
> >
> > been experiencing.
> >
> >
> >
> > I can repeatably generate the problem (CM_INVALID_OFFSET error and
> >
> >
> >
> > quarantining of audio files) by importing .wav files via AMA, and
> >
> >
> >
> > consolidating them. Crucially, Avid will only quarantine the new audio
> >
> >
> >
> > files if they are consolidated in a project for which 'film options'
> >
> >
> >
> > have been selected during project creation.
> >
> >
> >
> > (It's worth noting that this appears to be a bad workflow for other
> >
> >
> >
> > reasons as well. When I AMA-import .wav files, the start timecode field
> >
> >
> >
> > is always 00:00:00:00, whereas the files get a proper start timecode
> >
> >
> >
> > assigned if they are imported the old-fashioned way.)
> >
> >
> >
> > I've attached more detail below, in case anyone wants to try to
> >
> >
> >
> > reproduce the problem.
> >
> >
> >
> > Project type 1080p/23.976 WITH film options (35mm 4 perf):
> >
> >
> >
> > -----------------------------------------------
> >
> >
> >
> > - import .wav files via AMA, and consolidate them to an empty MXF/1 folder
> >
> >
> >
> > -deselect 'skip media files already on the target drive'
> >
> >
> >
> > -check all audio conversion boxes to 48kHz/16 Bit and PCM (MXF)
> >
> >
> >
> > -choose "Keep masterclips linked to media on the original drive."
> >
> >
> >
> > Files consolidate succesfully, but Avid generates the following error before creating the .mdb database in the MXF folder, and crashes to the desktop after choosing 'continue':
> >
> >
> >
> > Assertion failed: iofRefNum != 0
> >
> >
> >
> > /Snapshots/relengsnow6_1343949798/coresw/core/Projects/Mac/../../src/filesys/coreMacFileLocator.c,
> >
> >
> >
> > Line: 1586
> >
> >
> >
> > When I restart Avid, I get the CM_INVALID_ERROR / Quarantine dialogue before even selecting a project.
> >
> >
> >
> > If I select 'Ignore all' at the Quarantine prompt my consolidated audio stays online (so the newly consolidated masterclips will play inside Avid). If I choose 'Quarantine All', all the newly consolidated audio is moved to the Quarantine folder.
> >
> >
> >
> > If I 'Ignore' rather than quarantining, any future rebuild of the database in that folder will generate the same error.
> >
> >
> >
> > Project type 1080p/23.976 WITHOUT film options:
> >
> >
> >
> > -----------------------------------------------
> >
> >
> >
> > Same as described above, up until the crash after consolidating.
> >
> >
> >
> > However, on restart, the databases can be successfully rebuilt without triggering quarantine or CM_INVALID_TRIM errors. If I switch to a project WITH film options, I can still rebuild the database in this MXF folder without error -- indicating the problem gets baked in during the consolidation, not during the rebuild.
> >
> >
> >
> > System:
> >
> >
> >
> > -------
> >
> >
> >
> > Avid Symphony 6.0.3
> >
> >
> >
> > Mac 2 x 2.4 GHz Quad-Core Intel Xeon, OSX 10.7.4, 24 GB RAM
> >
> >
> >
> > ATI Radeon HD 5870 1024 MB
> >
> >
> >
> > On 13-01-28 4:04 PM, Michael wrote:
> >
> >
> >
> > >
> >
> >
> >
> > > I have a MediaFiles folder with about 1953 audio files in MXF media
> >
> >
> >
> > > format, 85GB worth of material.
> >
> >
> >
> > >
> >
> >
> >
> > > When I trash the database files in that folder so Avid can rebuild
> >
> >
> >
> > > them, it quarantines about 1344 files with the error CM_INVALID_TRIM.
> >
> >
> >
> > >
> >
> >
> >
> > > If I move sample files from the quarantine folder back to the original
> >
> >
> >
> > > folder or to a different MediaFiles folder on a different drive, it
> >
> >
> >
> > > still wants to quarantine them.
> >
> >
> >
> > >
> >
> >
> >
> > > If I choose to "Ignore All" errors while rebuilding the database, the
> >
> >
> >
> > > rebuild will proceed, creating a new database file. I can drag the new
> >
> >
> >
> > > .mdb database file into an empty bin, and it populates with 265 clips.
> >
> >
> >
> > > Doing the same thing with the old database, which I've saved from the
> >
> >
> >
> > > Trash populates the bin with 1001 clips. Clearly the rebuilt database
> >
> >
> >
> > > is not indexing all the media in the folder when errors are ignored.
> >
> >
> >
> > >
> >
> >
> >
> > > I don't believe the quarantined audio MXF files are corrupt -- I can
> >
> >
> >
> > > play these MXF files with MXF4MacPlayer.app, and open them with
> >
> >
> >
> > > CalibratedMXFQstat.app. I can also move them back to their original
> >
> >
> >
> > > folder, restore the original database from the Trash, pull the old
> >
> >
> >
> > > database into a bin, and play back sample files that get quarantined
> >
> >
> >
> > > if the database is rebuilt.
> >
> >
> >
> > >
> >
> >
> >
> > > There's no obvious pattern to which files are quarantined, in terms of
> >
> >
> >
> > > creation date, file size or filename. CalibratedMXFQstat.app doesn't
> >
> >
> >
> > > show any unexpected differences between sample files that are
> >
> >
> >
> > > quarantined, and others that are not.
> >
> >
> >
> > >
> >
> >
> >
> > > I've seen a couple reports of similar troubles on the web, but no
> >
> >
> >
> > > solutions for rebuilding the database without quarantining the audio.
> >
> >
> >
> > >
> >
> >
> >
> > > Tried fresh user settings, but no help.
> >
> >
> >
> > >
> >
> >
> >
> > > Thanks in advance for any suggestions,
> >
> >
> >
> > > --Michael Brockington
> >
> >
> >
> > >
> >
> >
> >
> > > -------------------
> >
> >
> >
> > >
> >
> >
> >
> > > Avid Symphony 6.0.3 software-only / OSX 10.7.4 / Mac tower 2.24 GHZ
> >
> >
> >
> > > Quad-core Intel Xeon / 24 GB RAM
> >
> >
> >
> > >
> >
> >
> >
> > >
> >
> >
> >
> > [Non-text portions of this message have been removed]
> >
> >
> >
> > [Non-text portions of this message have been removed]
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > [Non-text portions of this message have been removed]
> >
>