I noticed you were using FF33.1 which actually sends Mode 1 even when Mode
0 is negotiated.   Could you try again with the current release version
which is 36.  Also go to about:addons and verify that the OpenH264 codec is
1.3.  It takes a few minutes after you first run for the plugin to update.

Before you change your app to Mode 1 I would like to try to debug Firefox's
implementation of Mode 0 since we advertise it in the SDP.  Also is Firefox
able to decode the Mode 0 stream sent from your application?  Thanks.

-EH


On Fri, Mar 6, 2015 at 7:13 AM, Randell Jesup <[email protected]> wrote:

> On 3/6/2015 9:16 AM, [email protected] wrote:
>
>> We have an application that expects 
>> profile-level-id=42801F;packetisation-mode=0,
>> and it doesn't decode the openH264 video sent from firefox (I was using
>> version 33.1).
>>
>> Is it possible to specify the profile level and packetisation mode that
>> firefox sends (by any means, but preferably using webRTC api) or is our
>> application stuck in the dark ages (requiring an update)?
>>
>
> There's a bug in the mode 0 support.  See bug 1097524.  This seems to have
> gotten sidetracked because of a lack of good mode-0 endpoints to test
> against.  I'll check the patches there for bitrot and then you can see if
> that fixes it for you.
>
> However, I would suggest moving to mode 1, which is what most equipment
> prefers.  Generally mode 0 is old, old equipment.
>
> --
> Randell Jesup, Mozilla
>
> _______________________________________________
> dev-media mailing list
> [email protected]
> https://lists.mozilla.org/listinfo/dev-media
>
_______________________________________________
dev-media mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-media

Reply via email to