8 Replies Latest reply: Sep 19, 2012 10:41 AM by Mike Bresnahan RSS

    H264 stream is not encoded properly in AIR 3.2


      Hi all,


      I'm running latest AIR runtime on my desktop:

      My air appliation is compiled with latest air sdk also:

      Platform is Windows XP.

      The application is aka Cirrus Video Phone Lab app, where streaming is done to another instance of the AIR application.


      I do use this code to enable H264 encoding on the outgoing stream:


           var h264Settings:H264VideoStreamSettings = new H264VideoStreamSettings();

           h264Settings.setProfileLevel(H264Profile.MAIN, H264Level.LEVEL_3_2);

           outgoingStream.videoStreamSettings = h264Settings;


      Once my app is running i do check the VideoStreamSettings.codec on both outgoing and incoming streams:


           trace("outStream codec: "+outgoingStream.videoStreamSettings.codec+"\n");

           trace("inStream codec: "+incomingStream.videoStreamSettings.codec+"\n");


      Here is the output:


           outStream codec: H264Avc

           inStream codec: Sorenson


      So it appears that incomingStream is using Sorenson?! How is this possible to encode in H264 and decode using Sorenson and see the video?

      Or really it is Sorenson which is used for encoing irrelevant of what videoStreamSettings is set to? How about Adobe's claim they support H264 on the Air web page?

      Or am I missing something completely?






      An update:


      I've recompiled my test project to use web application and run it on a standalone flashplayer11_2r202_228_win_sa_debug_32bit.exe

      Result is the same: outgoing stream prints H264Avc, while incoming does Sorenson.

      So, I'm not really sure what's the deal about Adobe's claim about H264 support in AIR3 and FP 11.2? There are no H264 support in both. Period.

      Too bad Adobe, too bad... Sorenson has been since FP6 right? It's year 2012 now. I just want to remind you if you forgot about this.

      I undersdtand making creative art on the web page with useless claims (http://www.adobe.com/products/air/features.html) is much easier then making

      a product which stands for them, but with bugs like that it's better to keep the mouth shut then claim non-existent "features". Please also explain to us

      how are we suppose building that "cutting-edge" application running on "billions" of devices? Anyone?