Quantcast
Channel: Avid MediaCentral Forum
Viewing all articles
Browse latest Browse all 249

Interplay Access version 3.1 and higher show partial status for some clips.. Sample math issue?

$
0
0

I am hoping that this is the correct forum for this.  I apologize if not.

We have recently found that some clips and media either ingested with our AutoIngest product OR using the editor P2 import feature, are showing partial offline status after "refresh from media indexer" with the latest IPE.  Interplay Access versions 2.5, 2.7 and 3.0 show the same clips as online (green status).

I think that this is a sample math issue and the resulting clip, although 303 video frames long, works out to 302.9995 video frames and Access properties shows video as partial.

There is a sample P2 image here, one clip, that is 303 frames long.  Please use the legacy P2 import and check the clip into Interplay and the problem is easily seen.ftp.nltek.com/nlttemp/Avid/AccessPartialOfflineIssue/CONTENTS.zip I think the issue depends on how sample math works out.  With this clip, it is 303 video frames.  AMA/consolidate is making audio mxf that is 485284 samples in size. The metadata part of these files are 485285.   485284 samples is 302.9995 video samples.  485285 is 303.0001 video samples. I think because the media length with AMA is 1 sample shorter, the video is showing as partial (with the newer Interplay Access). With autoingest, we are creating mxf audio with 485284 samples of data AND the metadata is 485284 samples.  But the video is still partial as shown with newer Interplay Access. NOTE: the p2 audio files are 485284 samples long. (302.9995 frames).  Neither autoingest or the editor import is padding this out with one more sample to make it 303.0001 frames. SO the question is.. Is this an Interplay ACCESS Issue?  I think the AMA/P2 consolidate has an issue.  What should the correct sample count be?  Should they be padded out in the MXF essence for audio?   It seems like a rounding issue somewhere... Please let me know if there are any questions.  I want to help resolve this...  Can you advise if this is something that WE should address (padding out mxf) or is it likely an Access problem?   I do think something similar came up with this a couple of years ago... Please let me know if you have any questions..

Viewing all articles
Browse latest Browse all 249

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>