As of August 30, 2023, this AWS Solution is no longer available. Existing deployments will continue to run. The functionality provided by Content Analysis on AWS will be superseded with functionality in Media2Cloud on AWS and Content Localization on AWS. We encourage you to explore these solutions.
MXF could contain multiple channels that use different configurations for different purposes. In order to automatically process these inputs, MIE should use MediaInfo to analyze the configuration of the packaged media and then adjust the settings for the MediaConvert proxy encode to extract the correct audio for downstream content analysis.
So, here are a few common scenarios:
MIE works:
Channel 1 to 6 are 5.1 channels. this case you would be ok.
MIE doesn't work:
Channel 1 & 2 are L & R; Channel 3 & 4 are Audio Description tracks
Channel 1 & 2 are English; Channel 3 &4 are Spanish NG
I also came across file that contains test tone signal track (for timing, I believe) NG
MediaConvert downmix channels into stereo by default. As you can imagine, you get very mixed up stereo output and that would affect the rest of the workflow like Transcribe and Comprehend.
MXF could contain multiple channels that use different configurations for different purposes. In order to automatically process these inputs, MIE should use MediaInfo to analyze the configuration of the packaged media and then adjust the settings for the MediaConvert proxy encode to extract the correct audio for downstream content analysis.
So, here are a few common scenarios:
MIE works:
MIE doesn't work:
MediaConvert downmix channels into stereo by default. As you can imagine, you get very mixed up stereo output and that would affect the rest of the workflow like Transcribe and Comprehend.