Skip navigation
ImAStreamer
ImAStreamer
Currently Being Moderated

H.264 Video Encoding Bug Introduced?

Oct 31, 2011 10:28 AM

I'm not sure if the issue is related to a fix for a previous bug, or just a new bug introduced for this player.

 

My original problem was with the reporting of Camera.activityLevel. It only reports 0 and 100 when encoding with H.264 in FP11+ release, Sorenson reports the results properly. I was told it was fixed in this beta, which it does appear to be

See this post: http://forums.adobe.com/message/3999479

 

However I now see a new problem in this beta.  My application allows me to change the video settings on my H.264 encoded stream (quality, resolution, fps, etc) during the broadcast. And it works perfectly in FP11+. However, with the beta it now appears to cause problems and be broken.

 

Changing settings on an existing stream (it looks to be when changing from 320x240 to 640x480) causes streaks of red, green, and blue vertical lines over the  video image and the aspect ratio is wrong. The image appears squished - everything short and fat like mabe it's increaing the width value, but not the height. I'm testing the beta on Windows 32bit IE7 with a Logitech 9000 and on a different machine using Windows 32bit IE8 with a Logitech C910 with the same results.

 

The camera.width & camera.height properties to seem to report their values properly, but the stream as viewed on the server is definitely not at the correct resolution.

 

Can anyone verify this or advise? This version looks like it will break my app if released so thankfully it's still a beta.

 

Thank you!

1609 Views   16 Replies   Latest reply: ImAStreamer, Dec 14, 2011 1:25 PM
 
Replies
  • ImAStreamer
    Currently Being Moderated
    1. ImAStreamer,
    Oct 31, 2011 10:31 AM   in reply to ImAStreamer
    Report

    The beta build I am using is 11,2,201,18d.

     
    |
    Mark as:
  • bmai209
    Currently Being Moderated
    2. bmai209,
    Nov 7, 2011 3:01 PM   in reply to ImAStreamer
    Report

    Do you have a sample app I can use to reproduce this issue with?

     
    |
    Mark as:
  • ImAStreamer
    Currently Being Moderated
    3. ImAStreamer,
    Nov 7, 2011 7:05 PM   in reply to bmai209
    Report

    Yes I can provide you with a test application I've created. Please let me know how to get it to you.

     

    Thanks!

     
    |
    Mark as:
  • bmai209
    Currently Being Moderated
    4. bmai209,
    Nov 8, 2011 8:29 AM   in reply to ImAStreamer
    Report

    Can you log a bug at bugbase.adobe.com and add your media there.  Once you're done please post the bug here and I'll retrieve it from the bugbase and have it looked at.

     

    Thanks,

     

    ~Bao

     
    |
    Mark as:
  • ImAStreamer
    Currently Being Moderated
    5. ImAStreamer,
    Nov 8, 2011 10:04 AM   in reply to bmai209
    Report

    Here is the bug report: https://bugbase.adobe.com/index.cfm?event=bug&id=3022636  Please let me know what you find.

     

    Thanks for your help!

     
    |
    Mark as:
  • ImAStreamer
    Currently Being Moderated
    6. ImAStreamer,
    Nov 22, 2011 2:10 PM   in reply to ImAStreamer
    Report

    OK, in FP11 Beta 2 it appears you have fixed this bug (aspect ratio messed up when switching from 320x240 to 640x480), but now you've reintroduced the Camera.activityLevel bug again. It only reports 0 and 100, this was fixed in Beta 1.

     

    To summarize:

     

    FP 11 release

    Camera.activityLevel - broken, only reports 0 and 100

    Changing camera size from 320x240 to 640x480 - works

     

    FP 11.2 beta 1

    Camera.activityLevel - fixed

    Changing camera size from 320x240 to 640x480 - broken, turns video from color to black and white and has a strange aspect ratio

     

    FP 11.2 beta 2

    Camera.activityLevel - broken, only reports 0 and 100

    Changing camera size from 320x240 to 640x480 - works

     

    Hopefully you'll have everything working in beta 3.

     

    Do I need to submit a bug report for the Camera.activityLevel bug in FP 11.2 Beta 2?

     
    |
    Mark as:
  • bmai209
    Currently Being Moderated
    7. bmai209,
    Nov 22, 2011 3:57 PM   in reply to ImAStreamer
    Report

    The Camera.activityLevel for h.264 encoding is either 0 or 100 since FP11 when this feature was introduced.  That was a known issue base on the limitation of the h.264 codec we use for encoding.  There was never a fixed for that, not even in beta 1.  If you think otherwise, please submit a bug and attached to the bug the media you used demonstrating this issue. 

     
    |
    Mark as:
  • ImAStreamer
    Currently Being Moderated
    8. ImAStreamer,
    Nov 22, 2011 4:42 PM   in reply to bmai209
    Report

    I tested it and it worked in Beta 1. Is was also confirmed in this thread by another employee: http://forums.adobe.com/message/3999479#3999479. Can you please check?

     
    |
    Mark as:
  • bmai209
    Currently Being Moderated
    9. bmai209,
    Nov 22, 2011 5:28 PM   in reply to ImAStreamer
    Report

    I am positive this is not fixed in any player.  We still have an outstanding bug open for it.  If you insist that it was fixed in beta 1, please log the bug and add your test media so we can verified it.  What we have internally shows that if you published h.264 stream, the activity level is either 0 or 100.

     
    |
    Mark as:
  • ImAStreamer
    Currently Being Moderated
    10. ImAStreamer,
    Nov 22, 2011 6:39 PM   in reply to bmai209
    Report

    Do you have a link to download Beta 1? It doesn't look like I kept the install package. I'd need it for both IE and Firefox. I'll try to test it again, but I'm 99.9% sure that it worked. Thanks!

     
    |
    Mark as:
  • ImAStreamer
    Currently Being Moderated
    11. ImAStreamer,
    Nov 23, 2011 9:58 AM   in reply to ImAStreamer
    Report

    I appreciate your attention to this problem. However, you are incorrect. I found FP 11.2 Beta 1, installed it and tested my code and the Camera.activityLevel reports properly for H.264. I have submitted my test code and a screenshot to show that it works. I have submitted a bug as you requested. You can verify it internally here:

     

    https://bugbase.adobe.com/index.cfm?event=bug&id=3053822

     

    Again - working in 11.2 Beta 1, broken in 11.2 Beta 2.

     

    Please let me know if you can address this before FP 11.2 goes to release.

     

    Thank you.

     
    |
    Mark as:
  • ImAStreamer
    Currently Being Moderated
    12. ImAStreamer,
    Dec 13, 2011 5:08 PM   in reply to ImAStreamer
    Report

    I'm confused. This bug report has now been closed with a reason of AsDesigned.  Are you telling me that it's designed to have the activityLevel report with Sorenson, but not with H.264?  And again it WAS working in Beta 1 and stopped working again in Beta 2.  Can you give an update please?

     
    |
    Mark as:
  • bmai209
    Currently Being Moderated
    13. bmai209,
    Dec 14, 2011 9:24 AM   in reply to ImAStreamer
    Report

    That's right, the activityLevel report are for only Sorenson and not h.264 base on the limitation of the h.264 video codec that we're using.  It beta 1 we were adding some feature that mistakenly report the Sorenson activityLevel when you're publishing h.264 streams.  We have since resolved that issue hence the activityLevel is back to the way it is with 11.1.

     
    |
    Mark as:
  • ImAStreamer
    Currently Being Moderated
    14. ImAStreamer,
    Dec 14, 2011 10:21 AM   in reply to bmai209
    Report

    Thank you for the explanation. Curious though - isn't reporting the Sorenson level better than not reporting anything? How much of a difference between those numbers would there really be?

     

    So I should then expect I won't be getting the activityLevel for H.264 anytime soon then? If not, I can abandon my project that was going to rely on that and save me a lot of effort.

     

    Thanks again for the update.

     
    |
    Mark as:
  • bmai209
    Currently Being Moderated
    15. bmai209,
    Dec 14, 2011 12:00 PM   in reply to ImAStreamer
    Report

    It's a performance issue.  We had both the Sorenson and H.264 encoder on instead of just the H.264 encoder when the activityLevel was reporting something other than 0 and 100 in beta 1.

     
    |
    Mark as:
  • ImAStreamer
    Currently Being Moderated
    16. ImAStreamer,
    Dec 14, 2011 1:25 PM   in reply to bmai209
    Report

    Ah - in that case I'd agree that's not a viable solution. Thank you for you help.

     
    |
    Mark as:
Actions

More Like This

  • Retrieving data ...

Bookmarked By (0)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points