Hi Tomerb, First of all Interplay PAM manages metadata separately from media. The check-in operation is to submit asset metadata into PAM database which comes in a form of AAF. AAF metadata is something what AMT can generate as a part of "AMT archive". If you have AMT DLL sample app successfully compiled please take a look at the RAW_TO_AMT

AMT XML is used to describe existing MediaComposer supported formats only. Changing it to some extent will work, but will not let you create a raster that doesn't exist in MC. If you're referring to the stored WxH of the H264 sample XMLs this gives you a real understanding of the internal stored picture. So even if you have full 1080p raster

Hi Rich, The fix is scheduled for the 3.8 release at the moment. Thanks

Ah, its Access only, now I see what you're saying. Let me run this through Jira Despite tracks column shows V1 is in there its not on the list of tracks.

Hi Rich, Thanks for the detailed description and samples. I've downloaded the files and removed the links from your post. In my lab I see no issues with the AAFs provided. First I've checked-in both AAFs using Interplay Access 3.7.3 and verified in MC 8.8.2 that both segments are visible in both cases. Then I deleted the assets and retried with

Yes, this is media tool view. MXF file is directly indexed by MC no AAF involved. You can see both source and master mobs show the start timecode.

James, please provide a screenshot of MediaComposer not showing the timecode. I can see it in my lab. Hope you understand we are not in control how the other mentioned tools handle and read metadata.

Hi James, Which tool are you using? Simply looking into MXF dump you can find start position as shown below:

Hi James, I'm still not sure what the issue is. Please describe the import workflow for AMT generated media. Using Media Tool also works as expected and start timecode is shown as specified. Also what do you mean by offline proxy? What is the "any solution" used to generate Avid OPAtom media you're using? I'll clarify which timecode

Here is the example, opening AAF gives the start timecode as specified in the XML file: