Re: [webrtc-pc] Confusion over duplicates in setCodecPreferences? Why allow them? (#2955) from Bernard Aboba via GitHub on 2024-04-17 (public-webrtc-logs@w3.org from April 2024)

From: Bernard Aboba via GitHub <sysbot+gh@w3.org>
Date: Wed, 17 Apr 2024 01:13:56 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-2060163371-1713316434-sysbot+gh@w3.org>

I agree that 

```js
  {
    "clockRate": 90000,
    "mimeType": "video/H264",
    "sdpFmtpLine": "level-asymmetry-allowed=1;packetization-mode=1;profile-level-id=42001f"
  },
  {
    "clockRate": 90000,
    "mimeType": "video/H264",
    "sdpFmtpLine": "level-asymmetry-allowed=1;packetization-mode=0;profile-level-id=42001f"
  },
```
Are distinct codecs, because `packetization-mode` differs between them.  What I am not sure about is when these profiles are considered to "match": 

```js
  {
    "clockRate": 90000,
    "mimeType": "video/H264",
    "sdpFmtpLine": "level-asymmetry-allowed=1;packetization-mode=1;profile-level-id=42001f"
  },
  {
    "clockRate": 90000,
    "mimeType": "video/H264",
    "sdpFmtpLine": "level-asymmetry-allowed=0;packetization-mode=1;profile-level-id=42001f"
  },
```



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


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

Received on Wednesday, 17 April 2024 01:13:57 UTC