We are currently finalising the development of our Avid ingest tool - to allow for the automated processing of content for Avid Media Composer - complete with offline media, AMA metadata for relinking, etc. The only element that we are stuck on is regarding the generation of the msmFMID.pmr outside of Avid Media Composer. We know that this can be done

We have a workflow using the AMT to produce JFIF offline media - which is then in turn re-wrapped using our own version of BMXLib to embed metadata that is required and is not possible to add from within AMT. This process is working fine and allows for relinking without issue. We have now performed the same workflow but using sources such as XDCAM

We have a workflow using the AMT to produce JFIF offline media - which is then in turn re-wrapped using our own version of BMXLib to embed metadata that is required and is not possible to add from within AMT. This process is working fine and allows for relinking without issue. We have now performed the same workflow but using sources such as XDCAM

Hi, After implementing JFIF 4:1s for our client - I wanted to explore what offline codecs were possible with Media Composer, and I have hit across what seems like an obvious oddity. At the very bottom end - using AMT you can produce a 0.8Mbps H264 proxy, or a 2Mbps H264 proxy. Stepping up from here, you get into JFIF 4:1s (approx 12Mbps), before then

Vadym, For now I have resolved this using the libmxf tools, compiling our own version of BMX that supports the required JFIF variants that we are using (e.g. 4:1s). I am doing some other work on getting the metadata updated for AMA linking, and so will publish here my final OPAtom for reference when I have completed it.

Understood - my only interest here is MediaComposer showing the timecode. To confirm - the screenshot you provide was achieved by adding in the OPAtom directly - without adding in the associated AAF? I will repeat my tests tomorrow and confirm - providing screenshots.

Well Media Composer critically - it shows no timecode. But then also MediaInfo, FFMPEG, FFMBC - none of these show a timecode stamp.

The workflow is the OPAtom media will be ingested via a referenced an AAF file - and so of course the AAF file can contain the timecode track for the OPAtom. However - we are wanting to keep this secure, and so we need to have the timecode stamped onto the file. If we look at a file export to JFIF from Avid Media Composer - we see a timecode on the

I have suggested this back to our client - and have received the following reply; "...This wouldn’t normally be the case with Avid media. When generating media via any solution to Avid OPatom, the TC would definitely be baked into the file. As AAF delivery across platforms is not always guaranteed and sequences can modify the metadata it

The issue is that when opening the media in MC - it shows as having no timecode track. Similarly the media in say MediaInfo shows as having no timecode track. If the media is opened via the AAF - are you suggesting that it would show as having a timecode track in MC?