Comments (4)
This turns out to be regression from #2935. Prior to that it said this in sLD:
![image](https://private-user-images.githubusercontent.com/3136226/324872761-734e3de6-cdb3-4686-83e8-9d30a93eda58.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MTUxOTg3MDQsIm5iZiI6MTcxNTE5ODQwNCwicGF0aCI6Ii8zMTM2MjI2LzMyNDg3Mjc2MS03MzRlM2RlNi1jZGIzLTQ2ODYtODNlOC05ZDMwYTkzZWRhNTgucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI0MDUwOCUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNDA1MDhUMjAwMDA0WiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9ZDcwNGRlYzQ2MjNiYjhkZDA4ODY4OTYwNDMxNWFmZGIxMzVlODVmNTU4MTVkYzM5M2Y0ZGIxNzY1NTZiM2RjYSZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QmYWN0b3JfaWQ9MCZrZXlfaWQ9MCZyZXBvX2lkPTAifQ.3YEFIVMWPQc9Q-DrGXe1lUMI_UmVJ1AnWBBrx5kDjGk)
...and this in create an RTCRtpTransceiver:
I.e. it starts out empty and is then populated based on negotiation (which may be non-empty or empty).
But with #2935 this got replaced with this in sLD:
...and this in create an RTCRtpTransceiver:
I.e. it starts out being entirely implementation-defined whether it is empty or includes the full set or something in between , and then "enabled" is only ever set to true, never false.
This means it cannot possibly represent the (subset of) codecs that were negotiated, which seems broken.
from webrtc-pc.
@alvestrand what are next steps? Do we back out #2935 for now, or do you have a PR in the hopper?
From #2925 (comment):
Suggested revised model
... When calling setCodecPreferences, checking is done against receiver.[[codecs]], not against sender/receiver.getCapabilities(). If setCodecPreferences() includes a codec with the “enabled” flag set to false in the receiver’s [[codecs]] slot, it is set to “true”.
We probably need new internal slots for this instead, e.g. transceiver.[[SendCodecCapabilities]] and [[ReceiveCodecCapabilities]] (defaulting to the implementation list), as appropriating [[SendCodecs]] or [[ReceiveCodecs]] for this (defaulting to empty) seems to interfere with their existing purpose of reflecting what's been negotiated (#2967).
from webrtc-pc.
From #2925 (comment):
Suggested revised model
... When calling setCodecPreferences, checking is done against receiver.[[codecs]], not against sender/receiver.getCapabilities(). If setCodecPreferences() includes a codec with the “enabled” flag set to false in the receiver’s [[codecs]] slot, it is set to “true”.
Also, was part of the intent here to repurpose receiver.getParameters().codecs
to be an input source for setCodecPreferences
?
If so, do we need non-static versions of sender/receiver.getCapabilities()
?
from webrtc-pc.
May look as if we had a name collision between previous [[SendCodecs]] at the PC level and [[SendCodecs]] at the sender/receiver level, and I did not detect it when moving [[SendCodecs]] (which I thought unique) to the sender/receiver level.
from webrtc-pc.
Related Issues (20)
- Update the accessibility section 14 to include RFC 8865 for real-time text in WebRTC data channel HOT 43
- Clarify a=rtpmap codec mappings should be offered even if the codec is not a preferred one HOT 20
- Existing setCodecPreferences NOTE is wrong and should be deleted HOT 8
- Specify what should happen if filtering [[PreferredCodecs]] on direction results in empty list HOT 7
- setCodecPreferences, sendonly codecs and dummy codecs HOT 21
- If a preferred codec is filtered out, does it still get assigned a PT? HOT 16
- Proposing setCodecPreferences to deal with both send and recv codecs HOT 6
- RTCSessionDescriptionInit vs "local" RTCLocalSessionDescriptionInit HOT 2
- Review mute/unmute/ended and constraints on RTCRtpReceiver's track. HOT 2
- Alternative storage for RTCCertificates needed HOT 6
- simple webrtc connection and manual signaling (QR, JSON, Carrier pigeon) - consent time out prevents connection HOT 3
- RTCIceCandidate's relayProtocol and url members can be null but not absent
- Missing tests for candidate amendments
- Incorporate jitterBufferTarget
- Confusion over duplicates in setCodecPreferences? Why allow them? HOT 10
- setCodecPreferences should take sequence<RTCRtpCodec>
- setCodecPreferences should trigger negotiationneeded HOT 3
- Implementations only update getParameters().codecs when negotiation has finished HOT 3
- Comparison rules for RTCRtpCodec needs clarification on how mimeType is compared HOT 10
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from webrtc-pc.