The clips can then be added to the editor bin using the Interplay window. Then the editor should be restarted, this forces any cached values to be released. If these editor bins had been checked into Interplay, they should be rechecked in at this point. If reingesting media is required then all referrences to these clips (and sequences) must be removed from all editor bins. Any NEW media/clips ingested will not be subject to any restrictions when using the new MXF file format available in V2.8. This only makes the older style media files which have the limitation when changing audio tracks and re-ingesting. Using the older style MXF file still does not allow changing the number of audio tracks when re-ingesting. AutoIngest will provide warnings about this and provide a mechanism to make the old style MXF files if re-ingest is absolutely necessary (see Site Settings). One caveat is that any clips re-ingested with AutoIngest V2.8 (and future versions), will cause a similar issue if re-ingesting over media ingested with earlier versions (prior to V2.8). This offset (after V2.8) will always be at a fixed offset from the actual video regardless of other data. (The number of audio tracks ingested was adjusting the index table offset in the video MXF file). So if the media is re-ingested with a different count of audio tracks, then the index table offset is no longer valid in the new MXF file.
The problem is traced to the fact that Avid caches the location of a long gop mpeg clip's index table offset into it's editor database. We have made a change to AutoIngest (released in V2.8) that will make this a non-issue.
If a clip is ingested with audio tracks, place that clip into the editor bin, and then subsequently change the number of audio tracks and then re-ingest and overwrite the previous mxf files, the clip is "broken". We reserve the right to monitor and remove inappropriate posts.ĭocumented solutions for some commonly asked questions.Īvid Editor DIDMapper error where we are at with re-ingesting media which is causing the DIDMapper errors. Engage the community by asking questions or announcing your latest successful project.
This public forum provides users a collaborative environment to discuss the features, configuration, and deployment of AutoIngest & the Media Transcoder.