Re: [webrtc-pc] How should be populated codecs capabilities fmtp lines? (#3024)

FWIW, restricting to H264, VP8  and VP9 which are in all browsers for now:

For VP8
- Chrome has 1 entry (no parameters)
- Firefox has 1 entry for VP8 (max-fs and max-fr parameters)
- Safari has 1 entry (no parameters)

For H264
- Chrome has 10 entries (5 profiles, with level-asymnetry-allowed and packetization-mode=0 or 1)
- Firefox has 2 entries for H264 (1 profile with  level-asymnetry-allowed and packetization-mode=1 or omitted)
- Safari has 4 entries for H264 (2 profiles with level-asymnetry-allowed and packetization-mode=0 or 1)

For VP9
- Chrome has 4 entries (different profiles)
- Firefox has 1 entry (no profile but max-fs and max-fr parameters)
- Safari has 2 entries (two profiles)

I wonder how we could converge here.

-- 
GitHub Notification of comment by youennf
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/3024#issuecomment-2491678610 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Thursday, 21 November 2024 16:16:39 UTC