Dear Avid AMT3 Dev Team, I have a problem that you probably can resolve. When ChainManager is running with a ISampleBasedPushInputAsset as source, I create a second task to call the IMPSink::write(MPBufferHolder buffer) function on each frame. On error exception the ChainManager does not respond to the IMPSink::write(MPBufferHolder buffer) function

Ok, Problem solved. I was working on outdated documentation. By the time XAVC-Intra 300 was a valid target now it have to be XAVC-Intra 300-CBG. As this valid value is not documented in EssenceInfo.xsd but only in IMediaAsset .h it takes some time to figure it out. And strangely the wrong value of target was not raised at all and Picture Strategy evaluation

Here we are also working with AMT-3.11.0. I can confirm that by passing to AMT3 <taggedvalue> <name>foo</name> <value>bar</value> </taggedvalue> We have in the AAFdump : Object of Class: TaggedValue Name: "foo" Value: (indirect type: aafString) "bar" And it's visible in MediaComposer when showing

Hello Simon, In AMT3 documentation, in MediaAssetDescription.xsd, there is a section TaggedValueType which describes how to use the API to set TaggedValues in the target AAF. Hope this will help you.

Hello Andy, I'm Grégoire, teammate of Gregor, partially in charge of AMT3 integration here at Woody Technologies. Thank you for your answer, but i still need a precision. When you say that " It is possible to describe a yuv 422 progressive 10bit format ", what are the good values for this PixelFormat description? Cause in actual