Hello,

Something we are struggling with having now updated to SDK 2.11 from 2.10 is that we get an error message when encoding any JFIF resolutions. These worked just fine in SDK 2.10. It appears to work in SDK 2.12 which implies something has been fixed, but SDK 2.12 drops encoding of some formats so using that is not ideal.

Specifically when we call

CreateAmtFile using a destination directory, the input and output xml as specified in the spreadsheet (e.g. UNC_720_248_NTSC_2A.XML and JFIF_20_1_NTSC_2A.XML) and NULL and NULL as the final two parameters

we get AMT_COMPRESSION_FORMAT_NOT_SUPPORTED

If I revert the DLLs to those for SDK 2.10 we get an OK status returned instead.

As far as I can tell nothing has changed in the XML examples for the JFIF resolutions between these versions so I am mystified. The release notes for 2.11 suggest some tweaks to JFIF encoding but nothing is reflected in the example XML files so I can only assume that's internal fixes that don't concern an end user.

This call is ahead of transmission of any actual video and audio data. I've tried using the RAW_TO_AMT feature of the sample application with the same output XML file and that appears to run so perhaps a change has been made to what the JFIF codecs require as an input format and the spreadsheet has not been updated?

We're using the VC10x86 SDK. Any help would be gratefully received - is it just that JFIF encoding is busted in 2.11 or is there something I can do to make it work?

Thanks

Nick

Nick,

Sorry for the delay. We are looking at this now...

- Rob

Nick,

I checked with our support team. 

They confirmed that there was a change in AMT 2.11 that affected JFIF encoding. And this was fixed in AMT 2.12.

- Rob