Hi Avid

When we have detected a problem in our pipeline feeding frames to AMT, we call abort on the MediaProcessor::ChainProcessing::ChainManager in order to halt AMT and do a clean tidy up.

Often the abort appears to be ignored and AMT, which just keeps returning AMT_STALLED_IN_READER.  Is this a known issue?

Thanks

Steve