Issue metadata
Sign in to add a comment
|
WebRtc: Need Support for H.264 AVC Payload Format Parameters
Reported by
rajsripe...@gmail.com,
Jul 1 2016
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.103 Safari/537.36 Steps to reproduce the problem: There is support for H264 AVC codec in Chrome canary builds. However, we need the ability for Chrome to communicate the required frame size, bit rate, frames per second etc from the peer using format parameters. ie the "a=fmtp" line in SDP. eg: "level-asymmetry-allowed=1;packetization-mode=1;profile-level-id=42e01f;max-fs=1237;max-br=1160000;max-fps=3000”. On the reverse direction, Chrome WebRtc should honour these parameters when a peer sends them in the SDP. What is the expected behavior? What went wrong? The app written on WebRtc do not currently have the ability to request what it expects from the peer for H264 AVC codec. Interop with other media stacks supporting H264 AVC is difficult as there is no way for them to request these constraints. Did this work before? No Chrome version: 51.0.2704.103 Channel: canary OS Version: 10.0 Flash Version: Shockwave Flash 22.0 r0
,
Jul 5 2016
Marking the above issue as Untriaged as this is a feature request. Dev team will take a call on the above request. Thank you!
,
Jul 5 2016
,
Oct 26 2016
,
Oct 26 2016
H.264 parameter work is in progress. Deduping with the relevant WebRTC bug. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by b...@chromium.org
, Jul 1 2016