I am using AMT 2.12 to write an edit while capture file via CreateAmtInterplayClip.

I am using the following running on VMs:

• Interplay 4.0
• Nexis Client Manger 7.11.0.8
• Avid ISIS 5500 4.7.11.16275 running in demo mode

I have ensured that all of my audio samples are being submitted to WriteAmtTrackSample. When I finish writing all of my samples, I do the following:

1. CloseAmtTrack on all opened tracks
2. GetUpdaetdAaf with finalize_aaf set to true and write the aaf to a file
3. CloseAmtFile
4. UnloadAmtPlugins

After the above is run, a second process takes the finalized aaf and checks it in using IWS via SOAP.

The issue is that the video and audio tracks present on the ISIS storage have a smaller file size than expected. For a 10 second file, Media Composer fails to play the file at all due to consistency check failures on the audio. I can scrub the video, but the last second shows duplicate frames. MC is accessing the clip via the Interplay Window.

On ISIS, the mxf is shown as 513 KiB for 10 seconds of 24 bit 48khz audio for each audio track, which should at minmum be 1406 KiB (24 / 8 * 48000 * 10 / 1024). The video track is more sane, but still short of what it should be. It is worth noting that the finalized AAF says that the clip is 10 seconds long. If I write to local storage using CreateAmtFile, the track sizes are all sane.

By default my ISIS-BufferSize registry entries were set to 16 MiB, or at least I assume that to be the default. When I modified them to be 512 KiB, I experienced an improvement. The audio track's file size was 1536 KiB, which allowed me to play the first 6 out of 10 seconds in Media Composer without issue.

Regardless of the length of my clip, it appears that the last 10 seconds has this issue. So to me it seems like on completion the sample data is not being flushed to ISIS properly.

Is there an operation in the AMT that I am skipping? Could the ISIS demo mode be to blame?

Thanks.

It is worth noting that writing to the ISIS share via CreateAmtFile produces complete files for each of the tracks. This AAF can be checked in and played in its entirety through MC. So the issue seems specific to CreateInterplayClip and ISIS.

Hi Mark,

Followed up on this issue in email. Troubleshooting typically requires engineering engagement and a support agreement in place.