Web Real-Time Communications Working Group - Activity in 2023
No matches.
TR publications
-
9 documents published.
-
Identifiers for WebRTC's Statistics API published as a Candidate Recommendation Draft. History of Identifiers for WebRTC's Statistics API
-
Scalable Video Coding (SVC) Extension for WebRTC published twice as a Working Draft. History of Scalable Video Coding (SVC) Extension for WebRTC
-
Screen Capture published as a Working Draft. History of Screen Capture
-
Media Capture from DOM Elements published as a Working Draft. History of Media Capture from DOM Elements
-
WebRTC Encoded Transform published twice as a Working Draft. History of WebRTC Encoded Transform
-
WebRTC Extended Use Cases published twice as a Draft Note. History of WebRTC Extended Use Cases
-
Past meetings
Participants
-
1 participant joined.
-
Xinhong Yuan (Discord) joined.
-
GitHub
w3c/webrtc-pc
-
3 issues opened.
-
RTCIceCandidateInit members are linked instead of RTCIceCandidate attributes w3c/webrtc-pc#2916, by @sam-vi.
-
Composed RTCPeerConnection.gatheringState seems wrong in some cases w3c/webrtc-pc#2914, by @docfaraday.
-
-
2 issues closed.
-
RTCIceCandidateInit members are linked instead of RTCIceCandidate attributes w3c/webrtc-pc#2916.
-
RTCSctpTransport.maxMessageSize is a floating point type w3c/webrtc-pc#2822.
-
-
7 issues received 25 new comments.
-
Composed RTCPeerConnection.gatheringState seems wrong in some cases w3c/webrtc-pc#2914 (11 comments by @alvestrand, @docfaraday, @fippo)
-
setCodecPreferences vs unidirectional codecs w3c/webrtc-pc#2888 (8 comments by @alvestrand, @fippo, @henbos)
-
WebRTC spec should explicitly specify all causes of a PeerConnection-sourced track receiving mute/unmute w3c/webrtc-pc#2915 (2 comments by @alvestrand, @jan-ivar)
-
Clarify unmute event must fire on receiver.track AFTER sRD(offer) succeeds w3c/webrtc-pc#2880 (1 comment by @mickel8)
-
Intended outcome when modifying direction in have-local-offer w3c/webrtc-pc#2751 (1 comment by @mickel8)
-
RTCSctpTransport.maxMessageSize is a floating point type w3c/webrtc-pc#2822 (1 comment by @docfaraday)
-
data channel default binaryType value is 'blob' w3c/webrtc-pc#2170 (1 comment by @dontcallmedom-bot)
-
-
3 pull requests opened.
-
Update to ReSpec version 34.3.0 w3c/webrtc-pc#2918, by @dontcallmedom.
-
Fix references to RTCIceCandidate attributes. w3c/webrtc-pc#2917, by @sam-vi.
-
Change the default value of binaryType to "arraybuffer" w3c/webrtc-pc#2913, by @Orphis.
-
-
2 pull requests merged.
-
Fix references to RTCIceCandidate attributes. w3c/webrtc-pc#2917.
-
Change the default value of binaryType to "arraybuffer" w3c/webrtc-pc#2913.
-
-
2 pull requests received 2 new comments.
-
Change the default value of binaryType to "arraybuffer" w3c/webrtc-pc#2913 (1 comment by @alvestrand)
w3c/webrtc-nv-use-cases
-
1 issue opened.
-
N42 and N47 partly overlapping w3c/webrtc-nv-use-cases#127, by @stefhak.
-
-
1 issue closed.
-
N42 and N47 partly overlapping w3c/webrtc-nv-use-cases#127.
-
-
8 issues received 9 new comments.
-
Low Latency Streaming: Review of requirements w3c/webrtc-nv-use-cases#95 (1 comment by @dontcallmedom-bot)
-
Section 3.2.1: Improvements for game pad input w3c/webrtc-nv-use-cases#94 (1 comment by @dontcallmedom-bot)
-
N15 latency control should be formulated in a technology-agnostic way w3c/webrtc-nv-use-cases#91 (1 comment by @dontcallmedom-bot)
-
Is the DRM requirement in the Low latency Broadcast with Fanout use case satisfied by data channels? w3c/webrtc-nv-use-cases#86 (1 comment by @dontcallmedom-bot)
-
What is a "node" in the Low latency Broadcast with Fanout use case? w3c/webrtc-nv-use-cases#85 (1 comment by @dontcallmedom-bot)
-
Section 3.2: Feedback related to WebRTC-NV Low Latency Streaming Use Case w3c/webrtc-nv-use-cases#103 (1 comment by @dontcallmedom-bot)
-
2 pull requests opened.
-
Section 3.2.1: Add N49 - video decoding recovery after packet loss w3c/webrtc-nv-use-cases#129, by @xingri.
-
Made N42 and N47 orthogonal. w3c/webrtc-nv-use-cases#128, by @stefhak.
-
-
3 pull requests merged.
-
Made N42 and N47 orthogonal. w3c/webrtc-nv-use-cases#128.
-
Section 3.2.2: Clarify Use Case w3c/webrtc-nv-use-cases#123.
-
Clarify Requirement N37 w3c/webrtc-nv-use-cases#125.
-
-
1 pull request closed.
-
Further clarify cloud gaming w3c/webrtc-nv-use-cases#126.
-
-
6 pull requests received 32 new comments.
-
Section 3.2.1: Add N48 - bandwidth feedback speed w3c/webrtc-nv-use-cases#118 (14 comments by @alvestrand, @dontcallmedom-bot, @stefhak, @xingri)
-
Section 3.2.1: Add N49 - video decoding recovery after packet loss w3c/webrtc-nv-use-cases#129 (10 comments by @aboba, @alvestrand, @stefhak, @xingri)
-
Clarify Requirement N37 w3c/webrtc-nv-use-cases#125 (3 comments by @aboba, @dontcallmedom-bot, @jan-ivar)
-
Section 3.2.2: Clarify Use Case w3c/webrtc-nv-use-cases#123 (3 comments by @aboba, @dontcallmedom-bot, @jan-ivar)
-
Requirement N38 is satisfied by jitterBufferTarget w3c/webrtc-nv-use-cases#124 (1 comment by @dontcallmedom-bot)
-
w3c/mediacapture-screen-share
-
2 issues opened.
-
Multiple screen capture w3c/mediacapture-screen-share#292, by @trookie2000.
-
Inconsistent "hints" w3c/mediacapture-screen-share#290, by @jan-ivar.
-
-
1 issue closed.
-
Inconsistent "hints" w3c/mediacapture-screen-share#290.
-
-
5 issues received 9 new comments.
-
Handling of contradictory hints w3c/mediacapture-screen-share#276 (3 comments by @dontcallmedom-bot, @eladalon1983, @jan-ivar)
-
Distinguish cancellations from absent OS permissions w3c/mediacapture-screen-share#281 (3 comments by @dontcallmedom-bot, @eladalon1983, @jan-ivar)
-
Should pending getDisplayMedia() calls reject on sleep and/or screen-lock? w3c/mediacapture-screen-share#287 (1 comment by @marcoscaceres)
-
-
1 pull request opened.
-
UA MAY ignore systemAudio and surfaceSwitching hints w3c/mediacapture-screen-share#291, by @jan-ivar.
-
-
1 pull request merged.
-
UA MAY ignore systemAudio and surfaceSwitching hints w3c/mediacapture-screen-share#291.
-
-
1 pull request closed.
-
Clarify wording around heuristic rejection of gDM w3c/mediacapture-screen-share#288.
-
w3c/webrtc-stats
-
1 issue closed.
-
Feedback on audio capture stats w3c/webrtc-stats#741.
-
-
2 pull requests opened.
-
Add "only exists" clause to various audio/video stats w3c/webrtc-stats#774, by @fippo.
-
Remove audio capture stats that have moved to MediaStreamTrack's stats w3c/webrtc-stats#773, by @henbos.
-
-
1 pull request merged.
-
Remove audio capture stats that have moved to MediaStreamTrack's stats w3c/webrtc-stats#773.
-
-
2 pull requests received 3 new comments.
-
Remove audio capture stats that have moved to MediaStreamTrack's stats w3c/webrtc-stats#773 (2 comments by @alvestrand, @henbos)
-
w3c/mediacapture-main
-
1 issue opened.
-
Avoid circular definition of muted. w3c/mediacapture-main#982, by @jan-ivar.
-
-
1 issue received 34 new comments.
-
Avoid circular definition of muted. w3c/mediacapture-main#982 (34 comments by @alvestrand, @dontcallmedom-bot, @eladalon1983, @guidou, @henbos, @jan-ivar, @youennf)
-
-
1 pull request opened.
-
Update to latest ReSpec version 34.3.0 w3c/mediacapture-main#983, by @dontcallmedom.
-
w3c/webrtc-encoded-transform
-
2 issues opened.
-
Internal slots are not defined w3c/webrtc-encoded-transform#218, by @saschanaz.
-
WHATWG Streams have no `[[owner]]` but the spec sets it w3c/webrtc-encoded-transform#217, by @saschanaz.
-
-
3 issues closed.
-
API for processing keyframe requests in JS w3c/webrtc-encoded-transform#210.
-
Expose flow control information to transform w3c/webrtc-encoded-transform#206.
-
WHATWG Streams have no `[[owner]]` but the spec sets it w3c/webrtc-encoded-transform#217.
-
-
5 issues received 35 new comments.
-
Generalize ScriptTransform constructor to allow main-thread processing w3c/webrtc-encoded-transform#89 (11 comments by @alvestrand, @guidou, @jan-ivar, @youennf)
-
Rename RTCRtpScriptTransform object w3c/webrtc-encoded-transform#216 (8 comments by @alvestrand, @fippo, @jan-ivar, @youennf)
-
Is frame-level fanout in scope of WebRTC encoded transform - Should we add an encoded-source api? w3c/webrtc-encoded-transform#211 (8 comments by @alvestrand, @dontcallmedom-bot, @guidou, @jan-ivar, @youennf)
-
WHATWG Streams have no `[[owner]]` but the spec sets it w3c/webrtc-encoded-transform#217 (7 comments by @alvestrand, @dontcallmedom, @saschanaz, @youennf)
-
API for processing keyframe requests in JS w3c/webrtc-encoded-transform#210 (1 comment by @alvestrand)
-
-
1 pull request opened.
-
Readable and Writable [[owner]] slots are unused w3c/webrtc-encoded-transform#219, by @youennf.
-
-
5 pull requests merged.
-
Congestion control API proposal w3c/webrtc-encoded-transform#207.
-
Add an API for a "keyframe has been requested" event w3c/webrtc-encoded-transform#215.
-
Describe "data" attribute w3c/webrtc-encoded-transform#212.
-
Update references and remove empty section w3c/webrtc-encoded-transform#213.
-
Readable and Writable [[owner]] slots are unused w3c/webrtc-encoded-transform#219.
-
-
3 pull requests received 26 new comments.
-
Add an API for a "keyframe has been requested" event w3c/webrtc-encoded-transform#215 (20 comments by @alvestrand, @dontcallmedom, @dontcallmedom-bot, @youennf)
-
Describe "data" attribute w3c/webrtc-encoded-transform#212 (4 comments by @alvestrand, @dontcallmedom-bot, @youennf)
-
Remove restriction on streams being limited to only one PC w3c/webrtc-encoded-transform#201 (2 comments by @alvestrand, @youennf)
-
w3c/mediacapture-extensions
-
6 issues closed.
-
MediaStreamTrack audio delay/glitch capture stats w3c/mediacapture-extensions#93.
-
[Track Stats API] When to initialize frame counting w3c/mediacapture-extensions#116.
-
[Track Stats API] Support all types of MediaStreamTrack w3c/mediacapture-extensions#102.
-
Migrate capture metrics from RTCAudioSourceStats to MediaStreamTrack method w3c/mediacapture-extensions#96.
-
[Audio Stats] Add average, min and max latency w3c/mediacapture-extensions#128.
-
[Audio Stats] Add current latency w3c/mediacapture-extensions#119.
-
-
6 issues received 22 new comments.
-
Solve user agent camera/microphone double-mute w3c/mediacapture-extensions#39 (13 comments by @dontcallmedom-bot, @eladalon1983, @guidou, @jan-ivar, @youennf)
-
Move MediaStreamTrack stats in its own spec? w3c/mediacapture-extensions#132 (5 comments by @dontcallmedom, @henbos, @jan-ivar)
-
MediaStreamTrack audio delay/glitch capture stats w3c/mediacapture-extensions#93 (1 comment by @henbos)
-
Echo cancellation: Need to specify the source of the echo cancellation reference signal w3c/mediacapture-extensions#31 (1 comment by @Annoraaq)
-
Migrate capture metrics from RTCAudioSourceStats to MediaStreamTrack method w3c/mediacapture-extensions#96 (1 comment by @henbos)
-
[Audio Stats] Add average, min and max latency w3c/mediacapture-extensions#128 (1 comment by @henbos)
-
-
2 pull requests opened.
-
Add lack of consensus note on audio frame counters w3c/mediacapture-extensions#135, by @henbos.
-
Introduce avg/min/max audio latency and resetLatency() w3c/mediacapture-extensions#134, by @henbos.
-
-
4 pull requests merged.
-
Typo fix w3c/mediacapture-extensions#133.
-
Add lack of consensus note on audio frame counters w3c/mediacapture-extensions#135.
-
Introduce avg/min/max audio latency and resetLatency() w3c/mediacapture-extensions#134.
-
Add current audio latency metric w3c/mediacapture-extensions#124.
-
-
3 pull requests received 4 new comments.
-
Add lack of consensus note on audio frame counters w3c/mediacapture-extensions#135 (2 comments by @jan-ivar)
-
Introduce avg/min/max audio latency and resetLatency() w3c/mediacapture-extensions#134 (1 comment by @dontcallmedom-bot)
-
w3c/webrtc-extensions
-
1 issue opened.
-
Add API to control encode complexity w3c/webrtc-extensions#191, by @ssilkin.
-
-
3 issues closed.
-
icecandidatepairadd is fired on closed pc w3c/webrtc-extensions#176.
-
What does it mean to NOT nominate candidatePair? w3c/webrtc-extensions#179.
-
-
1 issue received 1 new comment.
-
2 pull requests opened.
-
Define a candidate pair match algorithm. w3c/webrtc-extensions#193, by @sam-vi.
-
Define an RTCIceCandidate match algorithm. w3c/webrtc-extensions#192, by @sam-vi.
-
-
3 pull requests merged.
-
Don't fire icecandidatepairadd if closed + avoid competing normative prose w3c/webrtc-extensions#177.
-
Move non-normative prose in nominate algo into a note. w3c/webrtc-extensions#189.
-
Refer to change of selected pair/state algo w3c/webrtc-extensions#190.
-
-
3 pull requests received 6 new comments.
-
Add RTCIceTransport method to remove candidate pairs w3c/webrtc-extensions#175 (3 comments by @dontcallmedom-bot, @sam-vi)
-
Don't fire icecandidatepairadd if closed + avoid competing normative prose w3c/webrtc-extensions#177 (2 comments by @henbos, @jan-ivar)
-
w3c/webrtc-svc
-
3 issues received 4 new comments.
-
Align exposing `scalabilityMode` with the WebRTC "hardware capabilities" check w3c/webrtc-svc#92 (1 comment by @dontcallmedom)
-
2 pull requests opened.
-
Rewrite of Privacy Considerations Section w3c/webrtc-svc#97, by @aboba.
-
Remove reference to Media Capabilities from Terminology Section w3c/webrtc-svc#96, by @aboba.
-
-
1 pull request merged.
-
Remove reference to Media Capabilities from Terminology Section w3c/webrtc-svc#96.
-
-
1 pull request received 2 new comments.
w3c/mediacapture-image
-
2 issues opened.
-
Which devices / cameras actually support this? w3c/mediacapture-image#307, by @Regaddi.
-
PTZ permissions and InputDeviceInfo.getCapabilities() / devicechange event w3c/mediacapture-image#306, by @guidou.
-
-
1 issue received 2 new comments.
-
Which devices / cameras actually support this? w3c/mediacapture-image#307 (2 comments by @beaufortfrancois, @fippo)
-
w3c/mediacapture-screen-share-extensions
-
1 issue received 4 new comments.
-
Auto-pause capture when user switches captured content w3c/mediacapture-screen-share-extensions#4 (4 comments by @dontcallmedom-bot, @eladalon1983, @jan-ivar)
-
w3c/mediacapture-region
-
1 pull request opened.
-
Demo - fix video size w3c/mediacapture-region#80, by @eladalon1983.
-
-
1 pull request merged.
-
Demo - fix video size w3c/mediacapture-region#80.
-
-
1 pull request received 1 new comment.
w3c/mediacapture-transform
-
1 pull request merged.
-
Update audio explainer with intro + WebIDL w3c/mediacapture-transform#75.
-
-
1 pull request received 2 new comments.
-
Update audio explainer with intro + WebIDL w3c/mediacapture-transform#75 (2 comments by @alvestrand, @youennf)
-
w3c/webrtc-rtptransport
-
1 issue opened.
-
Examples pipe multiple streams into a single writable w3c/webrtc-rtptransport#15, by @jan-ivar.
-
-
9 issues received 12 new comments.
-
SDP "Bumper lanes" w3c/webrtc-rtptransport#10 (3 comments by @aboba, @alvestrand, @dontcallmedom-bot)
-
Examples pipe multiple streams into a single writable w3c/webrtc-rtptransport#15 (2 comments by @aboba, @dontcallmedom-bot)
-
-
1 pull request opened.
-
Don't pipe multiple streams into a single writable w3c/webrtc-rtptransport#16, by @aboba.
-
TR publications
-
3 documents published.
-
Media Capture and Streams published as a Candidate Recommendation Draft. History of Media Capture and Streams
-
Scalable Video Coding (SVC) Extension for WebRTC published twice as a Working Draft. History of Scalable Video Coding (SVC) Extension for WebRTC
-
Past meetings
-
1 meeting.
Participants
-
1 participant joined.
-
Tove Petersson (Google LLC) joined.
-
-
1 participant left.
-
Shengyuan Feng (Agora.io) left.
-
GitHub
w3c/webrtc-rtptransport
-
8 issues opened.
-
Add/Update examples w3c/webrtc-rtptransport#14, by @jan-ivar.
-
Arbitrary RTP Header Extensions w3c/webrtc-rtptransport#12, by @aboba.
-
Arbitrary RTCP messages w3c/webrtc-rtptransport#11, by @aboba.
-
SDP "Bumper lanes" w3c/webrtc-rtptransport#10, by @aboba.
-
Customizing piecemeal w3c/webrtc-rtptransport#9, by @aboba.
-
WHATWG Streams support? w3c/webrtc-rtptransport#8, by @aboba.
-
How does cryptex work? w3c/webrtc-rtptransport#7, by @aboba.
-
-
2 issues received 4 new comments.
w3c/mediacapture-screen-share-extensions
-
1 issue reopened.
-
Avoid user-confusion by not offering undesired audio sources w3c/mediacapture-screen-share-extensions#7, by @eladalon1983.
-
-
3 issues received 24 new comments.
-
Auto-pause capture when user switches captured content w3c/mediacapture-screen-share-extensions#4 (22 comments by @eladalon1983, @jan-ivar, @tovepet, @youennf)
-
Avoid user-confusion by not offering undesired audio sources w3c/mediacapture-screen-share-extensions#7 (1 comment by @eladalon1983)
-
w3c/mediacapture-extensions
-
4 issues opened.
-
Move MediaStreamTrack stats in its own spec? w3c/mediacapture-extensions#132, by @dontcallmedom.
-
volume is not working w3c/mediacapture-extensions#131, by @Delphiswest67.
-
[Audio Stats] Disagreement about audio dropped counters w3c/mediacapture-extensions#129, by @henbos.
-
[Audio Stats] Add average, min and max latency w3c/mediacapture-extensions#128, by @henbos.
-
-
3 issues closed.
-
[Track Stats API] Rephrase sentence on when to update internal slots w3c/mediacapture-extensions#108.
-
volume is not working w3c/mediacapture-extensions#131.
-
[Stats] Example uses ratio, not percentage w3c/mediacapture-extensions#125.
-
-
1 issue reopened.
-
[Track Stats API] Rephrase sentence on when to update internal slots w3c/mediacapture-extensions#108, by @alvestrand.
-
-
9 issues received 95 new comments.
-
Solve user agent camera/microphone double-mute w3c/mediacapture-extensions#39 (53 comments by @alvestrand, @bradisbell, @dontcallmedom-bot, @eladalon1983, @guidou, @jan-ivar, @youennf)
-
[Audio Stats] Disagreement about audio dropped counters w3c/mediacapture-extensions#129 (19 comments by @alfredh, @dontcallmedom-bot, @fippo, @henbos, @o1ka, @padenot, @steely-glint, @vr000m, @youennf)
-
Background Blur: Unprocessed video should be mandatory to support w3c/mediacapture-extensions#121 (7 comments by @alvestrand, @dontcallmedom-bot, @eladalon1983, @youennf)
-
Move MediaStreamTrack stats in its own spec? w3c/mediacapture-extensions#132 (5 comments by @alvestrand, @dontcallmedom, @henbos, @jan-ivar)
-
[Audio Stats] Add average, min and max latency w3c/mediacapture-extensions#128 (4 comments by @henbos, @jan-ivar)
-
[Track Stats API] Rephrase sentence on when to update internal slots w3c/mediacapture-extensions#108 (3 comments by @alvestrand, @henbos)
-
Should web applications be aware of reaction effects added by OS to camera feeds? w3c/mediacapture-extensions#118 (2 comments by @fippo, @nbulankin)
-
Migrate capture metrics from RTCAudioSourceStats to MediaStreamTrack method w3c/mediacapture-extensions#96 (1 comment by @henbos)
-
-
2 pull requests opened.
-
s/[[CurrentTaskId]]/[[LastTask]]/ w3c/mediacapture-extensions#130, by @jan-ivar.
-
4 pull requests merged.
-
s/[[CurrentTaskId]]/[[LastTask]]/ w3c/mediacapture-extensions#130.
-
Decide whether to update stats based on CurrentTaskId w3c/mediacapture-extensions#127.
-
s/percentage/ratio/ w3c/mediacapture-extensions#126.
-
Eye gaze correction w3c/mediacapture-extensions#56.
-
-
4 pull requests received 31 new comments.
-
Decide whether to update stats based on CurrentTaskId w3c/mediacapture-extensions#127 (1 comment by @henbos)
w3c/webrtc-encoded-transform
-
2 issues opened.
-
Rename RTCRtpScriptTransform object w3c/webrtc-encoded-transform#216, by @alvestrand.
-
Evaluate how to expose SFrame packetization format to RTCScriptTransform and SFrameTransform w3c/webrtc-encoded-transform#214, by @youennf.
-
-
4 issues received 9 new comments.
-
Rename RTCRtpScriptTransform object w3c/webrtc-encoded-transform#216 (4 comments by @alvestrand, @fippo, @jan-ivar, @youennf)
-
Is frame-level fanout in scope of WebRTC encoded transform - Should we add an encoded-source api? w3c/webrtc-encoded-transform#211 (3 comments by @guidou, @youennf)
-
Generalize ScriptTransform constructor to allow main-thread processing w3c/webrtc-encoded-transform#89 (1 comment by @alvestrand)
-
Evaluate how to expose SFrame packetization format to RTCScriptTransform and SFrameTransform w3c/webrtc-encoded-transform#214 (1 comment by @youennf)
-
-
3 pull requests opened.
-
Add an API for a "keyframe has been requested" event w3c/webrtc-encoded-transform#215, by @alvestrand.
-
Update references and remove empty section w3c/webrtc-encoded-transform#213, by @dontcallmedom.
-
Describe "data" attribute w3c/webrtc-encoded-transform#212, by @fippo.
-
-
3 pull requests received 45 new comments.
-
Add description of an API for controlling SDP codec negotiation w3c/webrtc-encoded-transform#186 (38 comments by @alvestrand, @dontcallmedom-bot, @fippo, @henbos, @jan-ivar, @pthatcher)
-
Describe "data" attribute w3c/webrtc-encoded-transform#212 (4 comments by @fippo, @JonathanLennox, @stefhak)
-
Add an API for a "keyframe has been requested" event w3c/webrtc-encoded-transform#215 (3 comments by @alvestrand, @jan-ivar)
-
w3c/mediacapture-transform
-
1 issue received 2 new comments.
-
How does generator.mute change track states? w3c/mediacapture-transform#81 (2 comments by @alvestrand, @youennf)
-
-
1 pull request received 1 new comment.
w3c/mediacapture-screen-share
-
3 issues opened.
-
Should pending getDisplayMedia() calls reject on sleep and/or screen-lock? w3c/mediacapture-screen-share#287, by @eladalon1983.
-
What's needed w3c/mediacapture-screen-share#284, by @ghost.
-
Can a shared surface select its derivative window？ w3c/mediacapture-screen-share#282, by @trookie2000.
-
-
1 issue closed.
-
What's needed w3c/mediacapture-screen-share#284.
-
-
2 issues received 13 new comments.
-
Should pending getDisplayMedia() calls reject on sleep and/or screen-lock? w3c/mediacapture-screen-share#287 (10 comments by @bradisbell, @eladalon1983, @youennf)
-
-
4 pull requests opened.
-
Added DisplaySurfaceChangeCallback w3c/mediacapture-screen-share#289, by @tovepet.
-
Clarify wording around heuristic rejection of gDM w3c/mediacapture-screen-share#288, by @eladalon1983.
-
Define the windowAudio option w3c/mediacapture-screen-share#283, by @eladalon1983.
-
-
1 pull request closed.
-
test w3c/mediacapture-screen-share#285.
-
-
1 pull request received 4 new comments.
w3c/mediacapture-main
-
3 issues opened.
-
Transformation of camera signal into displayed frames on screen in a video capture pipeline. w3c/mediacapture-main#981, by @abd0200.
-
Improve definition/guidelines of capture mute and/or failure w3c/mediacapture-main#980, by @youennf.
-
How should MediaStreamTrack interact with BFCache? w3c/mediacapture-main#974, by @fergald.
-
-
1 issue closed.
-
MediaStreamTrack frame rate: configured versus actual? w3c/mediacapture-main#826.
-
-
4 issues received 5 new comments.
-
How should MediaStreamTrack interact with BFCache? w3c/mediacapture-main#974 (2 comments by @youennf)
-
Improve definition/guidelines of capture mute and/or failure w3c/mediacapture-main#980 (1 comment by @vr000m)
-
MediaStreamTrack frame rate: configured versus actual? w3c/mediacapture-main#826 (1 comment by @henbos)
-
It is unclear from the spec whether cloning a MediaStreamTrack preserves the subtype or not of the cloned track w3c/mediacapture-main#857 (1 comment by @dontcallmedom)
-
-
3 pull requests opened.
-
Define getMuteReasons() w3c/mediacapture-main#979, by @eladalon1983.
-
Update to latest ReSpec version 34.2.2 w3c/mediacapture-main#978, by @dontcallmedom.
-
Update to latest ReSpec version 34.2.1 w3c/mediacapture-main#976, by @dontcallmedom.
-
-
3 pull requests merged.
-
Update to latest ReSpec version 34.2.2 w3c/mediacapture-main#978.
-
Update to latest ReSpec version 34.2.1 w3c/mediacapture-main#976.
-
Update to latest ReSpec version 34.2.0 w3c/mediacapture-main#973.
-
w3c/webrtc-pc
-
4 issues opened.
-
Fix ICE server URL querystring validation w3c/webrtc-pc#2912, by @dontcallmedom.
-
Is it illegal to modify sdp between createOffer and setLocalDescription? w3c/webrtc-pc#2907, by @y-i.
-
Are various exposed RTCIceCandidate values object-comparable? w3c/webrtc-pc#2906, by @jan-ivar.
-
Name and export the RTCIceTransport algorithm for change in selected pair or state w3c/webrtc-pc#2904, by @sam-vi.
-
-
3 issues closed.
-
binaryType setter requirements are wrong w3c/webrtc-pc#2897.
-
Should garbage collecting RTCDataChannels be observable? w3c/webrtc-pc#2624.
-
3 issues received 10 new comments.
-
Is it illegal to modify sdp between createOffer and setLocalDescription? w3c/webrtc-pc#2907 (5 comments by @alvestrand, @henbos, @y-i)
-
setCodecPreferences vs unidirectional codecs w3c/webrtc-pc#2888 (4 comments by @alvestrand, @fippo, @henbos)
-
-
5 pull requests opened.
-
Update to ReSpec version 34.2.2 w3c/webrtc-pc#2911, by @dontcallmedom.
-
Document test updates associated with amendments w3c/webrtc-pc#2910, by @dontcallmedom.
-
Fix binaryType setter requirements w3c/webrtc-pc#2909, by @dontcallmedom.
-
Update to ReSpec version 34.2.1 w3c/webrtc-pc#2908, by @dontcallmedom.
-
Name and export the RTCIceTransport state update algo w3c/webrtc-pc#2905, by @sam-vi.
-
-
6 pull requests merged.
-
Update to ReSpec version 34.2.2 w3c/webrtc-pc#2911.
-
Name and export the RTCIceTransport state update algo w3c/webrtc-pc#2905.
-
Fix binaryType setter requirements w3c/webrtc-pc#2909.
-
Update to ReSpec version 34.2.1 w3c/webrtc-pc#2908.
-
Update to ReSpec version 34.2.0 w3c/webrtc-pc#2903.
-
Prevent GC of non-closed RTCDataChannels w3c/webrtc-pc#2902.
-
-
3 pull requests received 11 new comments.
-
Document test updates associated with amendments w3c/webrtc-pc#2910 (3 comments by @dontcallmedom, @henbos)
-
Name and export the RTCIceTransport state update algo w3c/webrtc-pc#2905 (3 comments by @jan-ivar, @sam-vi)
w3c/webrtc-svc
-
1 issue closed.
-
Nit: Typos in Privacy Considerations section w3c/webrtc-svc#91.
-
-
4 issues received 6 new comments.
-
Align exposing `scalabilityMode` with the WebRTC "hardware capabilities" check w3c/webrtc-svc#92 (2 comments by @aboba, @dontcallmedom-bot)
w3c/webrtc-nv-use-cases
-
1 pull request opened.
-
Further clarify cloud gaming w3c/webrtc-nv-use-cases#126, by @stefhak.
-
-
1 pull request received 19 new comments.
-
Section 3.2.1: Add N48 - bandwidth feedback speed w3c/webrtc-nv-use-cases#118 (19 comments by @aboba, @fippo, @stefhak, @xingri)
-
w3c/webrtc-extensions
-
4 issues opened.
-
Maintain an internal slot of candidate pairs that are valid inputs to RTCIceTransport operations w3c/webrtc-extensions#188, by @sam-vi.
-
Describe a match algorithm for two RTCIceCandidatePairs w3c/webrtc-extensions#187, by @sam-vi.
-
Describe a match algorithm for two RTCIceCandidates w3c/webrtc-extensions#186, by @sam-vi.
-
setSelectedCandidatePair should explicitly reference the RTCIceTransport algorithm for change in selected candidate pair w3c/webrtc-extensions#185, by @sam-vi.
-
-
3 issues closed.
-
Unclear when all side-effects of setSelectedCandidatePair have taken effect w3c/webrtc-extensions#182.
-
Can we rename setSelectedCandidatePair to selectCandidatePair ? w3c/webrtc-extensions#178.
-
What happens if setSelectedCandidatePair() is called early? w3c/webrtc-extensions#180.
-
-
2 issues received 3 new comments.
-
Exposing decode errors / SW fallback as an event w3c/webrtc-extensions#146 (2 comments by @dontcallmedom-bot, @xingri)
-
Maintain an internal slot of candidate pairs that are valid inputs to RTCIceTransport operations w3c/webrtc-extensions#188 (1 comment by @jan-ivar)
-
-
2 pull requests opened.
-
Refer to change of selected pair/state algo w3c/webrtc-extensions#190, by @sam-vi.
-
Move non-normative prose in nominate algo into a note. w3c/webrtc-extensions#189, by @sam-vi.
-
-
2 pull requests merged.
-
Rename setSelectedCandidatePair and return a promise w3c/webrtc-extensions#183.
-
Move algorithm to setSelectedCandidatePair method, and use [=this=]. w3c/webrtc-extensions#181.
-
-
4 pull requests received 28 new comments.
-
Add RTCIceTransport method to remove candidate pairs w3c/webrtc-extensions#175 (13 comments by @jan-ivar, @sam-vi)
-
Rename setSelectedCandidatePair and return a promise w3c/webrtc-extensions#183 (9 comments by @henbos, @sam-vi, @youennf)
-
Move non-normative prose in nominate algo into a note. w3c/webrtc-extensions#189 (3 comments by @dontcallmedom, @jan-ivar, @sam-vi)
-
Don't fire icecandidatepairadd if closed + avoid competing normative prose w3c/webrtc-extensions#177 (3 comments by @henbos, @sam-vi)
-
w3c/webrtc-stats
-
1 issue opened.
-
Sender-side packetsReceived can be negative from garbage RRs w3c/webrtc-stats#772, by @jan-ivar.
-
-
1 issue received 1 new comment.
-
Sender-side packetsReceived can be negative from garbage RRs w3c/webrtc-stats#772 (1 comment by @henbos)
-
TR publications
-
8 documents published.
-
MediaStream Image Capture published twice as a Working Draft. History of MediaStream Image Capture
-
Screen Capture published as a Working Draft. History of Screen Capture
-
WebRTC Encoded Transform published 3 times as a Working Draft. History of WebRTC Encoded Transform
-
WebRTC Extended Use Cases published twice as a Draft Note. History of WebRTC Extended Use Cases
-
Past meetings
-
1 meeting.
Participants
-
2 participants joined.
-
Jozsef Vass (Discord) joined.
-
Shridhar Majali (NVIDIA) joined.
-
GitHub
w3c/webrtc-extensions
-
6 issues opened.
-
Clarify how icecandidatepairnominate and selectCandidatePair are to be used w3c/webrtc-extensions#184, by @jan-ivar.
-
Unclear when all side-effects of setSelectedCandidatePair have taken effect w3c/webrtc-extensions#182, by @sam-vi.
-
What happens if setSelectedCandidatePair() is called early? w3c/webrtc-extensions#180, by @jan-ivar.
-
What does it mean to NOT nominate candidatePair? w3c/webrtc-extensions#179, by @jan-ivar.
-
Can we rename setSelectedCandidatePair to selectCandidatePair ? w3c/webrtc-extensions#178, by @jan-ivar.
-
icecandidatepairadd is fired on closed pc w3c/webrtc-extensions#176, by @jan-ivar.
-
-
1 issue closed.
-
ICE improvements: select a candidate pair w3c/webrtc-extensions#171.
-
-
4 issues received 10 new comments.
-
What does it mean to NOT nominate candidatePair? w3c/webrtc-extensions#179 (5 comments by @jan-ivar, @pthatcher, @sam-vi)
-
Can we rename setSelectedCandidatePair to selectCandidatePair ? w3c/webrtc-extensions#178 (3 comments by @henbos, @jan-ivar, @sam-vi)
-
Unclear when all side-effects of setSelectedCandidatePair have taken effect w3c/webrtc-extensions#182 (1 comment by @jan-ivar)
-
What happens if setSelectedCandidatePair() is called early? w3c/webrtc-extensions#180 (1 comment by @henbos)
-
-
3 pull requests opened.
-
Rename setSelectedCandidatePair and return a promise w3c/webrtc-extensions#183, by @sam-vi.
-
Move algorithm to setSelectedCandidatePair method, and use [=this=]. w3c/webrtc-extensions#181, by @jan-ivar.
-
Don't fire icecandidatepairadd if closed + avoid competing normative prose w3c/webrtc-extensions#177, by @jan-ivar.
-
-
1 pull request merged.
-
Extend RTCIceTransport to allow changing the selected candidate pair w3c/webrtc-extensions#174.
-
-
4 pull requests received 26 new comments.
-
Add RTCIceTransport method to remove candidate pairs w3c/webrtc-extensions#175 (15 comments by @aboba, @henbos, @jan-ivar, @pthatcher, @sam-vi)
-
Rename setSelectedCandidatePair and return a promise w3c/webrtc-extensions#183 (5 comments by @jan-ivar, @pthatcher, @sam-vi)
-
Move algorithm to setSelectedCandidatePair method, and use [=this=]. w3c/webrtc-extensions#181 (4 comments by @henbos, @pthatcher, @sam-vi)
-
Don't fire icecandidatepairadd if closed + avoid competing normative prose w3c/webrtc-extensions#177 (2 comments by @pthatcher, @sam-vi)
-
w3c/webrtc-encoded-transform
-
3 issues opened.
-
Is frame-level fanout in scope of WebRTC encoded transform - Should we add an encoded-source api? w3c/webrtc-encoded-transform#211, by @youennf.
-
API for processing keyframe requests in JS w3c/webrtc-encoded-transform#210, by @alvestrand.
-
Spec doesn’t say what happens on reuse w3c/webrtc-encoded-transform#209, by @jan-ivar.
-
-
7 issues closed.
-
Expose MIME type as frame metadata w3c/webrtc-encoded-transform#158.
-
SDP mangling: control encoding or control packetization? w3c/webrtc-encoded-transform#199.
-
Should we rename SFrameTransform and RTCRtpScriptTransform w3c/webrtc-encoded-transform#65.
-
Optimizing encoded frame buffer allocation and memory copies w3c/webrtc-encoded-transform#49.
-
Should there be a RTCConfiguration boolean to prevent data to be sent without being transformed w3c/webrtc-encoded-transform#104.
-
What does sender.generateKeyFrame() do when sender.track is null, ended or disabled? w3c/webrtc-encoded-transform#185.
-
Move RTP Timestamp to Metadata and rename w3c/webrtc-encoded-transform#203.
-
-
13 issues received 22 new comments.
-
Is frame-level fanout in scope of WebRTC encoded transform - Should we add an encoded-source api? w3c/webrtc-encoded-transform#211 (6 comments by @alvestrand, @guidou, @youennf)
-
What does sender.generateKeyFrame() do when sender.track is null, ended or disabled? w3c/webrtc-encoded-transform#185 (4 comments by @alvestrand, @jan-ivar, @youennf)
-
SDP mangling: control encoding or control packetization? w3c/webrtc-encoded-transform#199 (1 comment by @alvestrand)
-
Need APIs for using WebCodec with PeerConnection w3c/webrtc-encoded-transform#121 (1 comment by @alvestrand)
-
Should we rename SFrameTransform and RTCRtpScriptTransform w3c/webrtc-encoded-transform#65 (1 comment by @youennf)
-
Optimizing encoded frame buffer allocation and memory copies w3c/webrtc-encoded-transform#49 (1 comment by @youennf)
-
Encoded frame IDLs share definitions with WebCodecs w3c/webrtc-encoded-transform#99 (1 comment by @alvestrand)
-
Should there be a RTCConfiguration boolean to prevent data to be sent without being transformed w3c/webrtc-encoded-transform#104 (1 comment by @youennf)
-
Define needed data to pass between depacketizer and decoder w3c/webrtc-encoded-transform#174 (1 comment by @alvestrand)
-
Is "empty" value of RTCEncodedVideoFrameType useful? w3c/webrtc-encoded-transform#156 (1 comment by @youennf)
-
Expose flow control information to transform w3c/webrtc-encoded-transform#206 (1 comment by @alvestrand)
-
-
2 pull requests opened.
-
Remove (de)serialization of no longer existent RTCEncodedVideoFrame.timestamp w3c/webrtc-encoded-transform#208, by @dontcallmedom.
-
Congestion control API proposal w3c/webrtc-encoded-transform#207, by @alvestrand.
-
-
3 pull requests merged.
-
add mimeType to metadata w3c/webrtc-encoded-transform#140.
-
Remove (de)serialization of no longer existent RTCEncodedVideoFrame.timestamp w3c/webrtc-encoded-transform#208.
-
Move RTP timestamp members to Metadata objects w3c/webrtc-encoded-transform#204.
-
-
7 pull requests received 62 new comments.
-
Add description of an API for controlling SDP codec negotiation w3c/webrtc-encoded-transform#186 (36 comments by @alvestrand, @dontcallmedom, @fippo, @jan-ivar, @Philipel-WebRTC, @youennf)
-
Congestion control API proposal w3c/webrtc-encoded-transform#207 (10 comments by @alvestrand, @guidou, @youennf)
-
IDL changes for setMetadata for 3.2.2 webrtc nv use case w3c/webrtc-encoded-transform#202 (6 comments by @dontcallmedom, @palak8669)
-
add mimeType to metadata w3c/webrtc-encoded-transform#140 (6 comments by @alvestrand, @dontcallmedom, @fippo)
-
Move RTP timestamp members to Metadata objects w3c/webrtc-encoded-transform#204 (2 comments by @fippo, @saschanaz)
-
Remove restriction on streams being limited to only one PC w3c/webrtc-encoded-transform#201 (1 comment by @guidou)
-
Remove (de)serialization of no longer existent RTCEncodedVideoFrame.timestamp w3c/webrtc-encoded-transform#208 (1 comment by @alvestrand)
-
w3c/mediacapture-extensions
-
5 issues opened.
-
[Stats] Example uses ratio, not percentage w3c/mediacapture-extensions#125, by @henbos.
-
[Track Stats API] Make stats attribute nullable instead of throwing when unsupported w3c/mediacapture-extensions#122, by @henbos.
-
Background Blur: Unprocessed video should be mandatory to support w3c/mediacapture-extensions#121, by @alvestrand.
-
[Audio Stats] Add current latency w3c/mediacapture-extensions#119, by @henbos.
-
Should web applications be aware of reaction effects added by OS to camera feeds? w3c/mediacapture-extensions#118, by @youennf.
-
-
1 issue closed.
-
[Track Stats API] Make stats attribute nullable instead of throwing when unsupported w3c/mediacapture-extensions#122.
-
-
2 issues reopened.
-
Migrate capture metrics from RTCAudioSourceStats to MediaStreamTrack method w3c/mediacapture-extensions#96, by @henbos.
-
[Audio Stats] Add current latency w3c/mediacapture-extensions#119, by @henbos.
-
-
8 issues received 28 new comments.
-
Should web applications be aware of reaction effects added by OS to camera feeds? w3c/mediacapture-extensions#118 (10 comments by @eladalon1983, @fippo, @huibk, @nbutko, @nienkedekker, @riju, @youennf)
-
[Track Stats API] Rephrase sentence on when to update internal slots w3c/mediacapture-extensions#108 (8 comments by @alvestrand, @henbos, @jan-ivar)
-
[Track Stats API] When to initialize frame counting w3c/mediacapture-extensions#116 (2 comments by @henbos)
-
Migrate capture metrics from RTCAudioSourceStats to MediaStreamTrack method w3c/mediacapture-extensions#96 (2 comments by @henbos)
-
[Track Stats API] Make stats attribute nullable instead of throwing when unsupported w3c/mediacapture-extensions#122 (2 comments by @henbos)
-
Background Blur: Unprocessed video should be mandatory to support w3c/mediacapture-extensions#121 (1 comment by @huibk)
-
[Track Stats API] Support all types of MediaStreamTrack w3c/mediacapture-extensions#102 (1 comment by @henbos)
-
-
5 pull requests opened.
-
Decide whether to update stats based on CurrentTaskId w3c/mediacapture-extensions#127, by @henbos.
-
s/percentage/ratio/ w3c/mediacapture-extensions#126, by @henbos.
-
Add current audio latency metric w3c/mediacapture-extensions#124, by @henbos.
-
Make track stats nullable w3c/mediacapture-extensions#123, by @henbos.
-
Add current latency to audio track.stats (this has not actually merged, but my commits got entangled, do ignore) w3c/mediacapture-extensions#120, by @henbos.
-
-
3 pull requests merged.
-
Add current latency to audio track.stats (this has not actually merged, but my commits got entangled, do ignore) w3c/mediacapture-extensions#120.
-
Add MediaStreamTrackAudioStats interface w3c/mediacapture-extensions#117.
-
Make track stats nullable w3c/mediacapture-extensions#123.
-
-
4 pull requests received 40 new comments.
-
Add MediaStreamTrackAudioStats interface w3c/mediacapture-extensions#117 (33 comments by @henbos, @jan-ivar, @padenot)
-
Add current latency to audio track.stats (this has not actually merged, but my commits got entangled, do ignore) w3c/mediacapture-extensions#120 (1 comment by @henbos)
-
w3c/mediacapture-screen-share
-
1 pull request merged.
-
Reflow with tidy w3c/mediacapture-screen-share#279.
-
-
1 pull request received 5 new comments.
-
Reflow with tidy w3c/mediacapture-screen-share#279 (5 comments by @aboba, @dontcallmedom, @henbos, @jan-ivar)
-
w3c/mediacapture-image
-
1 issue opened.
-
Why is https://www.w3.org/TR/image-capture/#dom-mediatrackcapabilities-torch a boolean w3c/mediacapture-image#304, by @youennf.
-
-
2 issues closed.
-
Broken references in MediaStream Image Capture w3c/mediacapture-image#302.
-
Why is https://www.w3.org/TR/image-capture/#dom-mediatrackcapabilities-torch a boolean w3c/mediacapture-image#304.
-
-
1 issue received 1 new comment.
-
Why is https://www.w3.org/TR/image-capture/#dom-mediatrackcapabilities-torch a boolean w3c/mediacapture-image#304 (1 comment by @guidou)
-
-
1 pull request opened.
-
Make torch capability a sequence<boolean> like other similar capabilities like echoCancellation w3c/mediacapture-image#305, by @youennf.
-
-
2 pull requests merged.
-
Remove usage of no-longer defined DevicePermissionDescriptor/deviceId w3c/mediacapture-image#303.
-
Make torch capability a sequence<boolean> like other similar capabilities like echoCancellation w3c/mediacapture-image#305.
-
-
1 pull request received 1 new comment.
-
Make torch capability a sequence<boolean> like other similar capabilities like echoCancellation w3c/mediacapture-image#305 (1 comment by @youennf)
-
w3c/webrtc-pc
-
2 issues received 2 new comments.
-
Should garbage collecting RTCDataChannels be observable? w3c/webrtc-pc#2624 (1 comment by @jan-ivar)
-
2 pull requests opened.
-
Update to ReSpec version 34.2.0 w3c/webrtc-pc#2903, by @dontcallmedom.
-
Prevent GC of non-closed RTCDataChannels w3c/webrtc-pc#2902, by @jan-ivar.
-
-
1 pull request received 6 new comments.
-
Prevent GC of non-closed RTCDataChannels w3c/webrtc-pc#2902 (6 comments by @alvestrand, @jan-ivar, @youennf)
-
w3c/webrtc-stats
-
2 issues opened.
-
Define a mechanism for setting the trigger duration for a video freeze w3c/webrtc-stats#771, by @flyingzl.
-
Exposing audio interruption metrics to JavaScript w3c/webrtc-stats#770, by @flyingzl.
-
-
1 issue received 2 new comments.
-
Clarify media-source frame rates (frames and framesPerSecond) w3c/webrtc-stats#708 (2 comments by @henbos)
-
w3c/mediacapture-main
-
1 issue received 5 new comments.
-
Racy devicechange event design has poor interoperability w3c/mediacapture-main#972 (5 comments by @chrisguttandin, @guidou, @jan-ivar, @karlt)
-
-
1 pull request opened.
-
Update to latest ReSpec version 34.2.0 w3c/mediacapture-main#973, by @dontcallmedom.
-
w3c/webrtc-nv-use-cases
-
2 pull requests opened.
-
Clarify Requirement N37 w3c/webrtc-nv-use-cases#125, by @aboba.
-
Requirement N38 is satisfied by jitterBufferTarget w3c/webrtc-nv-use-cases#124, by @aboba.
-
-
1 pull request merged.
-
Requirement N38 is satisfied by jitterBufferTarget w3c/webrtc-nv-use-cases#124.
-
-
1 pull request received 4 new comments.
-
Section 3.2.2: Clarify Use Case w3c/webrtc-nv-use-cases#123 (4 comments by @aboba, @alvestrand, @jan-ivar)
-
w3c/webrtc-svc
-
1 issue opened.
-
Questions on Scalability Mode and Media Capabilities w3c/webrtc-svc#95, by @bc-lee.
-
-
1 issue closed.
-
Questions on Scalability Mode and Media Capabilities w3c/webrtc-svc#95.
-
-
1 issue received 1 new comment.
w3c/webrtc-rtptransport
-
1 issue opened.
-
RtpTransport should be called RTCRtpTransport w3c/webrtc-rtptransport#2, by @henbos.
-
-
5 pull requests opened.
-
Set up for automatic bikeshed generation and PR preview w3c/webrtc-rtptransport#6, by @dontcallmedom.
-
Fill in the outline and fix boilerplate w3c/webrtc-rtptransport#5, by @aboba.
-
Fill out README file w3c/webrtc-rtptransport#4, by @aboba.
-
RTC + RtpTransport = true w3c/webrtc-rtptransport#3, by @henbos.
-
Update README.md w3c/webrtc-rtptransport#1, by @henbos.
-
-
3 pull requests merged.
-
Set up for automatic bikeshed generation and PR preview w3c/webrtc-rtptransport#6.
-
Fill in the outline and fix boilerplate w3c/webrtc-rtptransport#5.
-
Update README.md w3c/webrtc-rtptransport#1.
-
-
1 pull request closed.
-
Fill out README file w3c/webrtc-rtptransport#4.
-
-
1 pull request received 3 new comments.
w3c/webrtc-provisional-stats
-
1 issue opened.
-
Identify the state of provisional stats w3c/webrtc-provisional-stats#43, by @youennf.
-
-
1 issue received 12 new comments.
-
Identify the state of provisional stats w3c/webrtc-provisional-stats#43 (12 comments by @henbos, @vr000m, @youennf)
-
w3c/mediacapture-handle
-
1 pull request opened.
-
Use selfBrowserSurface in demo w3c/mediacapture-handle#72, by @eladalon1983.
-
-
1 pull request merged.
-
Use selfBrowserSurface in demo w3c/mediacapture-handle#72.
-
-
1 pull request received 1 new comment.
TR publications
-
2 documents published.
-
Media Capture and Streams published as a Candidate Recommendation Draft. History of Media Capture and Streams
-
WebRTC Encoded Transform published as a Working Draft. History of WebRTC Encoded Transform
-
Past meetings
-
4 meetings.
Participants
-
1 organization joined.
-
Discord joined.
-
GitHub
w3c/mediacapture-main
-
2 issues opened.
-
Racy devicechange event design has poor interoperability w3c/mediacapture-main#972, by @jan-ivar.
-
Should getCapabilities() return an empty array or undefined for facingMode? w3c/mediacapture-main#969, by @youennf.
-
-
5 issues closed.
-
ResizeMode (crop-and-scale) is underspecified w3c/mediacapture-main#584.
-
Spec-inherent capabilities of one differ from other capabilities of one, an unnecessary variant w3c/mediacapture-main#941.
-
Can devicechange fire prior to enumerateDevices? w3c/mediacapture-main#956.
-
Don't block getUserMedia on the user typing in URL bar w3c/mediacapture-main#934.
-
-
12 issues received 53 new comments.
-
Should devicechange fire when the device info changes? w3c/mediacapture-main#966 (24 comments by @eric-carlson, @guidou, @jan-ivar, @youennf)
-
Garbage collection of live tracks w3c/mediacapture-main#910 (12 comments by @bradisbell, @eladalon1983, @guidou, @jan-ivar, @youennf)
-
Mark sampleRate, sampleSize, latency as features at risk w3c/mediacapture-main#958 (4 comments by @bradisbell, @jan-ivar, @padenot)
-
ResizeMode (crop-and-scale) is underspecified w3c/mediacapture-main#584 (3 comments by @guidou, @jan-ivar)
-
Racy devicechange event design has poor interoperability w3c/mediacapture-main#972 (2 comments by @guidou, @youennf)
-
Should getCapabilities() return an empty array or undefined for facingMode? w3c/mediacapture-main#969 (2 comments by @guidou, @jan-ivar)
-
It is unclear which of PermissionStatus change event or MediaStreamTrack ended event should fire first in case Permission is revoked w3c/mediacapture-main#862 (1 comment by @jan-ivar)
-
MediaStreamTrack frame rate: configured versus actual? w3c/mediacapture-main#826 (1 comment by @dontcallmedom)
-
Spec-inherent capabilities of one differ from other capabilities of one, an unnecessary variant w3c/mediacapture-main#941 (1 comment by @jan-ivar)
-
Don't block getUserMedia on the user typing in URL bar w3c/mediacapture-main#934 (1 comment by @jan-ivar)
-
-
2 pull requests opened.
-
Allow upscaling to conceal concurrent use. w3c/mediacapture-main#971, by @jan-ivar.
-
Update to latest ReSpec version 34.1.8 w3c/mediacapture-main#970, by @dontcallmedom.
-
-
3 pull requests merged.
-
Allow upscaling to conceal concurrent use. w3c/mediacapture-main#971.
-
Add note about deviceId and groupId inconsistency with other capabilities. w3c/mediacapture-main#942.
-
Update to latest ReSpec version 34.1.8 w3c/mediacapture-main#970.
-
-
1 pull request received 5 new comments.
-
Allow upscaling to conceal concurrent use. w3c/mediacapture-main#971 (5 comments by @alvestrand, @jan-ivar)
-
w3c/mediacapture-screen-share
-
6 issues opened.
-
Distinguish cancellations from absent OS permissions w3c/mediacapture-screen-share#281, by @eladalon1983.
-
Can I share some Windows? w3c/mediacapture-screen-share#280, by @trookie2000.
-
Use same enum for or all include or exclude enums? w3c/mediacapture-screen-share#278, by @beaufortfrancois.
-
Use a single enum for or all w3c/mediacapture-screen-share#277, by @beaufortfrancois.
-
Handling of contradictory hints w3c/mediacapture-screen-share#276, by @eladalon1983.
-
Handling of contradictory hints w3c/mediacapture-screen-share#275, by @eladalon1983.
-
-
1 issue closed.
-
Handling of contradictory hints w3c/mediacapture-screen-share#275.
-
-
3 issues received 30 new comments.
-
Distinguish cancellations from absent OS permissions w3c/mediacapture-screen-share#281 (14 comments by @alvestrand, @beaufortfrancois, @chrisguttandin, @eladalon1983, @youennf)
-
Can I share some Windows? w3c/mediacapture-screen-share#280 (14 comments by @bradisbell, @eladalon1983, @jan-ivar, @trookie2000)
-
Use same enum for or all include or exclude enums? w3c/mediacapture-screen-share#278 (2 comments by @beaufortfrancois, @eladalon1983)
-
-
1 pull request opened.
-
Reflow with tidy w3c/mediacapture-screen-share#279, by @dontcallmedom.
-
-
1 pull request closed.
-
Reflow with tidy w3c/mediacapture-screen-share#273.
-
-
1 pull request received 2 new comments.
w3c/mediacapture-screen-share-extensions
-
1 issue received 16 new comments.
-
Auto-pause capture when user switches captured content w3c/mediacapture-screen-share-extensions#4 (16 comments by @beaufortfrancois, @eladalon1983, @henbos, @jan-ivar, @youennf)
-
w3c/webrtc-encoded-transform
-
4 issues opened.
-
Expose flow control information to transform w3c/webrtc-encoded-transform#206, by @alvestrand.
-
Editorial: Strange expansion of class idlMemberType w3c/webrtc-encoded-transform#205, by @alvestrand.
-
Move RTP Timestamp to Metadata and rename w3c/webrtc-encoded-transform#203, by @tonyherre.
-
Frame-level fanout requires ability to move frames between PCs w3c/webrtc-encoded-transform#200, by @alvestrand.
-
-
3 issues closed.
-
Should we expose packetization level API to RTCRtpScriptTransform? w3c/webrtc-encoded-transform#131.
-
EncodedVideoFrame needs to be marked serializable w3c/webrtc-encoded-transform#181.
-
Add a clone operator to RTCEncodedVideoFrame w3c/webrtc-encoded-transform#161.
-
-
10 issues received 23 new comments.
-
Expose flow control information to transform w3c/webrtc-encoded-transform#206 (6 comments by @alvestrand, @steely-glint, @youennf)
-
How to handle transforms largely changing frame size w3c/webrtc-encoded-transform#50 (4 comments by @alvestrand, @fippo, @youennf)
-
Move RTP Timestamp to Metadata and rename w3c/webrtc-encoded-transform#203 (4 comments by @fippo, @tonyherre)
-
Add a metadata modifying method to RTCEncodedFrame w3c/webrtc-encoded-transform#162 (2 comments by @dontcallmedom-bot, @palak8669)
-
Frame-level fanout requires ability to move frames between PCs w3c/webrtc-encoded-transform#200 (2 comments by @dontcallmedom-bot, @palak8669)
-
Should we expose packetization level API to RTCRtpScriptTransform? w3c/webrtc-encoded-transform#131 (1 comment by @alvestrand)
-
EncodedVideoFrame needs to be marked serializable w3c/webrtc-encoded-transform#181 (1 comment by @dontcallmedom-bot)
-
Allow incoming encoded frames to be forwarded to one or more senders on other PeerConnections w3c/webrtc-encoded-transform#160 (1 comment by @dontcallmedom-bot)
-
Add a clone operator to RTCEncodedVideoFrame w3c/webrtc-encoded-transform#161 (1 comment by @alvestrand)
-
-
3 pull requests opened.
-
Move RTP timestamp members to Metadata objects w3c/webrtc-encoded-transform#204, by @tonyherre.
-
IDL changes for setMetadata for 3.2.2 webrtc nv use case w3c/webrtc-encoded-transform#202, by @palak8669.
-
Remove restriction on streams being limited to only one PC w3c/webrtc-encoded-transform#201, by @palak8669.
-
-
1 pull request merged.
-
Add Serializable attributes to encoded video frames w3c/webrtc-encoded-transform#182.
-
-
4 pull requests received 22 new comments.
-
Add Serializable attributes to encoded video frames w3c/webrtc-encoded-transform#182 (11 comments by @alvestrand, @dontcallmedom-bot, @henbos, @jan-ivar, @youennf)
-
Move RTP timestamp members to Metadata objects w3c/webrtc-encoded-transform#204 (5 comments by @alvestrand, @fippo, @tonyherre)
-
Remove restriction on streams being limited to only one PC w3c/webrtc-encoded-transform#201 (4 comments by @alvestrand, @dontcallmedom-bot, @youennf)
-
IDL changes for setMetadata for 3.2.2 webrtc nv use case w3c/webrtc-encoded-transform#202 (2 comments by @dontcallmedom-bot, @youennf)
-
w3c/mediacapture-extensions
-
6 issues opened.
-
[Track Stats API] When to initialize frame counting w3c/mediacapture-extensions#116, by @henbos.
-
[Track Stats API] SameObject is a confusing API shape w3c/mediacapture-extensions#112, by @henbos.
-
[Track Stats API] Rename deliveredFrames to deliverableFrames w3c/mediacapture-extensions#109, by @henbos.
-
[Track Stats API] Rephrase sentence on when to update internal slots w3c/mediacapture-extensions#108, by @henbos.
-
[Track Stats API] Rename "videoStats" to "stats" w3c/mediacapture-extensions#107, by @henbos.
-
[Track Stats API] The stats API should be synchronous w3c/mediacapture-extensions#105, by @henbos.
-
-
7 issues closed.
-
[Track Stats API] track.getFrameStats() allocates memory, adding to the GC pile w3c/mediacapture-extensions#98.
-
[Track Stats API] Rename deliveredFrames to deliverableFrames w3c/mediacapture-extensions#109.
-
[Track Stats API] SameObject is a confusing API shape w3c/mediacapture-extensions#112.
-
[Track Stats API] Rename "videoStats" to "stats" w3c/mediacapture-extensions#107.
-
[Track Stats API] The stats API should be synchronous w3c/mediacapture-extensions#105.
-
[Track Stats API] Feature detection of audio vs video stats w3c/mediacapture-extensions#101.
-
[Track Stats API] Remove `timestamp` w3c/mediacapture-extensions#103.
-
-
12 issues received 40 new comments.
-
[Track Stats API] SameObject is a confusing API shape w3c/mediacapture-extensions#112 (23 comments by @bradisbell, @henbos, @jan-ivar, @padenot, @youennf)
-
[Track Stats API] track.getFrameStats() allocates memory, adding to the GC pile w3c/mediacapture-extensions#98 (4 comments by @dontcallmedom-bot, @henbos, @jan-ivar)
-
[Track Stats API] Rephrase sentence on when to update internal slots w3c/mediacapture-extensions#108 (3 comments by @henbos)
-
[Track Stats API] Rename deliveredFrames to deliverableFrames w3c/mediacapture-extensions#109 (2 comments by @henbos)
-
Migrate capture metrics from RTCAudioSourceStats to MediaStreamTrack method w3c/mediacapture-extensions#96 (1 comment by @henbos)
-
[Track Stats API] Support all types of MediaStreamTrack w3c/mediacapture-extensions#102 (1 comment by @henbos)
-
[Track Stats API] When to initialize frame counting w3c/mediacapture-extensions#116 (1 comment by @henbos)
-
[Track Stats API] The stats API should be synchronous w3c/mediacapture-extensions#105 (1 comment by @dontcallmedom-bot)
-
[Track Stats API] Rename "videoStats" to "stats" w3c/mediacapture-extensions#107 (1 comment by @henbos)
-
[Track Stats API] Feature detection of audio vs video stats w3c/mediacapture-extensions#101 (1 comment by @henbos)
-
How to avoid wide-lens backfacing camera on new phones? w3c/mediacapture-extensions#20 (1 comment by @polaroidkidd)
-
-
8 pull requests opened.
-
Add MediaStreamTrackAudioStats interface w3c/mediacapture-extensions#117, by @henbos.
-
Add MediaStreamTrackVideoStats.toJSON method w3c/mediacapture-extensions#115, by @henbos.
-
Change MediaStreamTrackVideoStats into a dictionary (#112 Proposal B) w3c/mediacapture-extensions#114, by @henbos.
-
Move stats counters into MediaStreamTrack (#112 Proposal A) w3c/mediacapture-extensions#113, by @henbos.
-
Rename deliveredFrames to deliverableFrames w3c/mediacapture-extensions#111, by @henbos.
-
Rename track.videoStats to track.stats w3c/mediacapture-extensions#110, by @henbos.
-
Change the track stats API to be synchronous w3c/mediacapture-extensions#106, by @henbos.
-
Delete MediaTrackFrameStats.timestamp w3c/mediacapture-extensions#104, by @henbos.
-
-
4 pull requests merged.
-
Add MediaStreamTrackVideoStats.toJSON method w3c/mediacapture-extensions#115.
-
Rename track.videoStats to track.stats w3c/mediacapture-extensions#110.
-
Change the track stats API to be synchronous w3c/mediacapture-extensions#106.
-
Delete MediaTrackFrameStats.timestamp w3c/mediacapture-extensions#104.
-
-
4 pull requests closed.
-
Add audio capture stats, rename method to getStats. w3c/mediacapture-extensions#97.
-
Rename deliveredFrames to deliverableFrames w3c/mediacapture-extensions#111.
-
Move stats counters into MediaStreamTrack (#112 Proposal A) w3c/mediacapture-extensions#113.
-
Change MediaStreamTrackVideoStats into a dictionary (#112 Proposal B) w3c/mediacapture-extensions#114.
-
-
9 pull requests received 25 new comments.
-
Change the track stats API to be synchronous w3c/mediacapture-extensions#106 (13 comments by @dontcallmedom-bot, @henbos, @jan-ivar, @vr000m)
-
Add audio capture stats, rename method to getStats. w3c/mediacapture-extensions#97 (2 comments by @henbos)
-
Move stats counters into MediaStreamTrack (#112 Proposal A) w3c/mediacapture-extensions#113 (1 comment by @henbos)
-
Change MediaStreamTrackVideoStats into a dictionary (#112 Proposal B) w3c/mediacapture-extensions#114 (1 comment by @henbos)
-
w3c/mediacapture-output
-
2 issues received 8 new comments.
-
Undesirable prompt from selectAudioOutput({deviceId}) if valid device removed w3c/mediacapture-output#137 (7 comments by @alvestrand, @dontcallmedom-bot, @karlt, @youennf)
-
Controlling 3rd party iframe audio output on a page? w3c/mediacapture-output#63 (1 comment by @kenzkiran)
-
w3c/webrtc-nv-use-cases
-
1 issue closed.
-
Section 3.2.1: Improvements for game pad input w3c/webrtc-nv-use-cases#94.
-
-
8 issues received 11 new comments.
-
Access to raw audio data w3c/webrtc-nv-use-cases#80 (3 comments by @aboba, @alvestrand, @dontcallmedom-bot)
-
Section 3.2: Feedback related to WebRTC-NV Low Latency Streaming Use Case w3c/webrtc-nv-use-cases#103 (2 comments by @aboba, @dontcallmedom-bot)
-
Low Latency Streaming: Review of requirements w3c/webrtc-nv-use-cases#95 (1 comment by @dontcallmedom-bot)
-
Section 3.2.1: Improvements for game pad input w3c/webrtc-nv-use-cases#94 (1 comment by @dontcallmedom-bot)
-
N15 latency control should be formulated in a technology-agnostic way w3c/webrtc-nv-use-cases#91 (1 comment by @dontcallmedom-bot)
-
Is the DRM requirement in the Low latency Broadcast with Fanout use case satisfied by data channels? w3c/webrtc-nv-use-cases#86 (1 comment by @dontcallmedom-bot)
-
What is a "node" in the Low latency Broadcast with Fanout use case? w3c/webrtc-nv-use-cases#85 (1 comment by @dontcallmedom-bot)
-
-
1 pull request opened.
-
Section 3.2.2: Clarify Use Case w3c/webrtc-nv-use-cases#123, by @aboba.
-
-
3 pull requests closed.
-
Section 3.2.1: Update Requirement N37 w3c/webrtc-nv-use-cases#117.
-
Section 3.2.2: Add requirements N13 and N16 w3c/webrtc-nv-use-cases#120.
-
Section 3.2.2: Clarify meaning of "low latency" w3c/webrtc-nv-use-cases#121.
-
-
5 pull requests received 13 new comments.
-
Section 3.2.2: Clarify Use Case w3c/webrtc-nv-use-cases#123 (7 comments by @aboba, @alvestrand, @dontcallmedom-bot, @youennf)
-
Section 3.2.2: Add requirements N13 and N16 w3c/webrtc-nv-use-cases#120 (3 comments by @aboba, @dontcallmedom-bot, @youennf)
-
Section 3.2.1: Add N48 - bandwidth feedback speed w3c/webrtc-nv-use-cases#118 (1 comment by @dontcallmedom-bot)
-
w3c/webrtc-extensions
-
1 issue closed.
-
ICE improvements: prevent candidate pair removal w3c/webrtc-extensions#166.
-
-
2 issues received 5 new comments.
-
Exposing decode errors / SW fallback as an event w3c/webrtc-extensions#146 (4 comments by @aboba, @dontcallmedom-bot, @fippo)
-
ICE improvements: select a candidate pair w3c/webrtc-extensions#171 (1 comment by @dontcallmedom-bot)
-
-
2 pull requests opened.
-
Add RTCIceTransport method to remove candidate pairs w3c/webrtc-extensions#175, by @sam-vi.
-
Extend RTCIceTransport to allow changing the selected candidate pair w3c/webrtc-extensions#174, by @sam-vi.
-
-
1 pull request merged.
-
Prevent candidate pair removal w3c/webrtc-extensions#168.
-
-
3 pull requests received 5 new comments.
-
Prevent candidate pair removal w3c/webrtc-extensions#168 (3 comments by @alvestrand, @dontcallmedom-bot, @sam-vi)
-
Add RTCIceTransport method to remove candidate pairs w3c/webrtc-extensions#175 (1 comment by @dontcallmedom-bot)
-
Extend RTCIceTransport to allow changing the selected candidate pair w3c/webrtc-extensions#174 (1 comment by @dontcallmedom-bot)
-
w3c/webrtc-pc
-
3 issues received 12 new comments.
-
No way to observe DataChannel-only transport events in initial negotiation w3c/webrtc-pc#2899 (10 comments by @alvestrand, @dontcallmedom-bot, @jan-ivar, @lgrahl, @steely-glint)
-
-
1 pull request opened.
-
Update to ReSpec version 34.1.8 w3c/webrtc-pc#2901, by @dontcallmedom.
-
-
1 pull request merged.
-
Update to ReSpec version 34.1.8 w3c/webrtc-pc#2901.
-
w3c/mst-content-hint
-
1 issue received 1 new comment.
w3c/mediacapture-record
-
1 issue received 1 new comment.
TR publications
-
7 documents published.
-
Audio Output Devices API published as a Candidate Recommendation Draft. History of Audio Output Devices API
-
Media Capture and Streams published as a Candidate Recommendation Draft. History of Media Capture and Streams
-
Identifiers for WebRTC's Statistics API published twice as a Candidate Recommendation Draft. History of Identifiers for WebRTC's Statistics API
-
Screen Capture published as a Working Draft. History of Screen Capture
-
WebRTC Extended Use Cases published twice as a Draft Note. History of WebRTC Extended Use Cases
-
GitHub
w3c/mediacapture-screen-share
-
1 issue closed.
-
Allow apps to avoid riskier display-surface types w3c/mediacapture-screen-share#261.
-
-
1 issue received 2 new comments.
-
Allow apps to avoid riskier display-surface types w3c/mediacapture-screen-share#261 (2 comments by @youennf)
-
-
1 pull request opened.
-
Define monitorTypeSurfaces w3c/mediacapture-screen-share#274, by @eladalon1983.
-
-
1 pull request merged.
-
Define monitorTypeSurfaces w3c/mediacapture-screen-share#274.
-
-
1 pull request received 2 new comments.
-
Define monitorTypeSurfaces w3c/mediacapture-screen-share#274 (2 comments by @eladalon1983, @jan-ivar)
-
w3c/mediacapture-output
-
2 issues opened.
-
Broken references in Audio Output Devices API w3c/mediacapture-output#140, by @dontcallmedom-bot.
-
Permission to "all devices of that class" semantics don't work in selectAudioOutput model w3c/mediacapture-output#138, by @jan-ivar.
-
-
2 issues closed.
-
Permission to "all devices of that class" semantics don't work in selectAudioOutput model w3c/mediacapture-output#138.
-
Broken references in Audio Output Devices API w3c/mediacapture-output#140.
-
-
1 pull request opened.
-
Remove deviceId from permission, and make granted = any w3c/mediacapture-output#139, by @jan-ivar.
-
-
1 pull request merged.
-
Remove deviceId from permission, and make granted = any w3c/mediacapture-output#139.
-
w3c/webrtc-encoded-transform
-
1 issue opened.
-
SDP mangling: control encoding or control packetization? w3c/webrtc-encoded-transform#199, by @alvestrand.
-
-
3 issues received 4 new comments.
-
Add a metadata modifying method to RTCEncodedFrame w3c/webrtc-encoded-transform#162 (2 comments by @alvestrand, @dontcallmedom-bot)
-
Does Chromium require anything in SDP or RTP Header to make this work? w3c/webrtc-encoded-transform#37 (1 comment by @asineth0)
-
Clarify why the writable stream backpressure should be disabled w3c/webrtc-encoded-transform#188 (1 comment by @dontcallmedom-bot)
-
-
1 pull request opened.
-
Update encoded explainer to include sample code for relay P2Ps w3c/webrtc-encoded-transform#198, by @palak8669.
-
-
1 pull request closed.
-
Add clone() method w3c/webrtc-encoded-transform#163.
-
-
4 pull requests received 31 new comments.
-
Add description of an API for controlling SDP codec negotiation w3c/webrtc-encoded-transform#186 (28 comments by @alvestrand, @jan-ivar)
-
Add Serializable attributes to encoded video frames w3c/webrtc-encoded-transform#182 (1 comment by @alvestrand)
-
Update encoded explainer to include sample code for relay P2Ps w3c/webrtc-encoded-transform#198 (1 comment by @palak8669)
-
w3c/webrtc-extensions
-
1 issue closed.
-
Suggest API for generating a Stream rather than a MediaStreamTrack from incoming media w3c/webrtc-extensions#85.
-
-
3 issues received 3 new comments.
-
Suggest API for generating a Stream rather than a MediaStreamTrack from incoming media w3c/webrtc-extensions#85 (1 comment by @alvestrand)
-
Exposing decode errors / SW fallback as an event w3c/webrtc-extensions#146 (1 comment by @dontcallmedom-bot)
-
ICE improvements: select a candidate pair w3c/webrtc-extensions#171 (1 comment by @dontcallmedom-bot)
-
-
1 pull request closed.
-
Remove JSEP Modifications w3c/webrtc-extensions#164.
-
w3c/mediacapture-extensions
-
3 issues opened.
-
[Track Stats API] Remove `timestamp` w3c/mediacapture-extensions#103, by @henbos.
-
[Track Stats API] Support all types of MediaStreamTrack w3c/mediacapture-extensions#102, by @henbos.
-
[Track Stats API] Feature detection of audio vs video stats w3c/mediacapture-extensions#101, by @henbos.
-
-
4 issues received 4 new comments.
-
How to avoid wide-lens backfacing camera on new phones? w3c/mediacapture-extensions#20 (1 comment by @piechoo)
-
[Track Stats API] Support all types of MediaStreamTrack w3c/mediacapture-extensions#102 (1 comment by @henbos)
-
[Track Stats API] Feature detection of audio vs video stats w3c/mediacapture-extensions#101 (1 comment by @henbos)
-
w3c/webrtc-pc
-
9 issues opened.
-
No way to observe DataChannel-only transport events in initial negotiation w3c/webrtc-pc#2899, by @jan-ivar.
-
binaryType setter requirements are wrong w3c/webrtc-pc#2897, by @annevk.
-
Put a=end-of-candidates into description(s) w3c/webrtc-pc#2896, by @jan-ivar.
-
What to do if a RTCPeerConnection gets closed inside a task that fires multiple events? w3c/webrtc-pc#2895, by @youennf.
-
ICE finished gathering algorithm touches state after firing an event w3c/webrtc-pc#2893, by @jan-ivar.
-
Redundant queuing in gathering state computation risks eliding events w3c/webrtc-pc#2892, by @jan-ivar.
-
Editorial mistakes in iceServers limit w3c/webrtc-pc#2889, by @jan-ivar.
-
setCodecPreferences vs unidirectional codecs w3c/webrtc-pc#2888, by @fippo.
-
-
1 issue closed.
-
Editorial mistakes in iceServers limit w3c/webrtc-pc#2889.
-
-
1 issue reopened.
-
data channel default binaryType value is 'blob' w3c/webrtc-pc#2170, by @youennf.
-
-
5 issues received 18 new comments.
-
data channel default binaryType value is 'blob' w3c/webrtc-pc#2170 (8 comments by @alvestrand, @annevk, @fippo, @jan-ivar, @lgrahl, @youennf)
-
No way to observe DataChannel-only transport events in initial negotiation w3c/webrtc-pc#2899 (3 comments by @jan-ivar, @lgrahl)
-
setCodecPreferences vs unidirectional codecs w3c/webrtc-pc#2888 (3 comments by @alvestrand, @henbos, @steely-glint)
-
-
3 pull requests opened.
-
Export symbols needed by encoded-transform w3c/webrtc-pc#2891, by @alvestrand.
-
Move iceServers limit to setConfiguration steps. w3c/webrtc-pc#2890, by @jan-ivar.
-
3 pull requests merged.
-
Move iceServers limit to setConfiguration steps. w3c/webrtc-pc#2890.
-
Export symbols needed by encoded-transform w3c/webrtc-pc#2891.
-
editorial: fix setParameterOptions usage in table of contents w3c/webrtc-pc#2887.
-
-
3 pull requests received 9 new comments.
-
Queue two tasks upon finishing ICE gathering, and fire gatheringstatechange & icegatheringstatechange in same task w3c/webrtc-pc#2894 (6 comments by @alvestrand, @docfaraday, @jan-ivar)
-
Move iceServers limit to setConfiguration steps. w3c/webrtc-pc#2890 (2 comments by @alvestrand, @jan-ivar)
-
w3c/mediacapture-image
-
1 issue opened.
-
Broken references in MediaStream Image Capture w3c/mediacapture-image#302, by @dontcallmedom-bot.
-
-
1 pull request opened.
-
Remove usage of no-longer defined DevicePermissionDescriptor/deviceId w3c/mediacapture-image#303, by @dontcallmedom.
-
w3c/mediacapture-main
-
2 issues closed.
-
get video input with torch w3c/mediacapture-main#886.
-
deviceId in permissions.query() is unimplemented fingerprinting surface w3c/mediacapture-main#965.
-
-
2 issues received 2 new comments.
-
deviceId in permissions.query() is unimplemented fingerprinting surface w3c/mediacapture-main#965 (1 comment by @dontcallmedom-bot)
-
2 pull requests merged.
-
Remove DevicePermissionDescriptor deviceId. w3c/mediacapture-main#968.
-
Add caniuse link. w3c/mediacapture-main#964.
-
-
1 pull request received 3 new comments.
-
Remove DevicePermissionDescriptor deviceId. w3c/mediacapture-main#968 (3 comments by @alvestrand, @jan-ivar)
-
w3c/webrtc-nv-use-cases
-
1 issue opened.
-
setMetadata for redundant relay PCs w3c/webrtc-nv-use-cases#122, by @palak8669.
-
-
4 issues received 5 new comments.
-
Is the DRM requirement in the Low latency Broadcast with Fanout use case satisfied by data channels? w3c/webrtc-nv-use-cases#86 (1 comment by @vitaly-castLabs)
-
Section 3.2: Feedback related to WebRTC-NV Low Latency Streaming Use Case w3c/webrtc-nv-use-cases#103 (1 comment by @dontcallmedom-bot)
-
Section 3.2.1: Improvements for game pad input w3c/webrtc-nv-use-cases#94 (1 comment by @dontcallmedom-bot)
-
6 pull requests received 7 new comments.
-
Section 3.2.1: Update Requirement N37 w3c/webrtc-nv-use-cases#117 (2 comments by @alvestrand, @dontcallmedom-bot)
-
Section 3.2.1: Add N48 - bandwidth feedback speed w3c/webrtc-nv-use-cases#118 (1 comment by @dontcallmedom-bot)
-
Section 3.2: Streaming should not require user prompts without sending media w3c/webrtc-nv-use-cases#119 (1 comment by @dontcallmedom-bot)
-
Section 3.2.2: Clarify meaning of "low latency" w3c/webrtc-nv-use-cases#121 (1 comment by @dontcallmedom-bot)
-
Section 3.2.2: Add requirements N13 and N16 w3c/webrtc-nv-use-cases#120 (1 comment by @dontcallmedom-bot)
-
Req N22: Remove specific hardware reference (GPU) w3c/webrtc-nv-use-cases#116 (1 comment by @dontcallmedom-bot)
-
w3c/mediacapture-record
-
1 issue received 1 new comment.
-
ignoreMutedMedia on a combination of muted and unmuted tracks? w3c/mediacapture-record#99 (1 comment by @marcusx2)
-
w3c/webrtc-stats
-
1 issue opened.
-
Stats example uses confusing variable names w3c/webrtc-stats#768, by @henbos.
-
-
3 issues closed.
-
Delete "Retiring stats objects" section w3c/webrtc-stats#729.
-
RTX and FEC stats are incomplete. w3c/webrtc-stats#751.
-
Redundant field `kind` in RTCInboundRtpStreamStats w3c/webrtc-stats#690.
-
-
1 issue received 2 new comments.
-
Conformance criteria incompatible with standards-track w3c/webrtc-stats#749 (2 comments by @dontcallmedom, @fippo)
-
-
1 pull request opened.
-
Remove duplicate definition of RTCInboundRtpStreamStats kind w3c/webrtc-stats#767, by @fippo.
-
-
4 pull requests merged.
-
Remove duplicate definition of RTCInboundRtpStreamStats kind w3c/webrtc-stats#767.
-
Delete 'retiring stats objects' section. w3c/webrtc-stats#763.
-
add rtxSsrc to inbound-rtp and outbound-rtp stats and fecSsrc to inbound-rtp w3c/webrtc-stats#765.
-
Remove duplicate RTCInboundRtpStreamStats `kind` w3c/webrtc-stats#766.
-
-
1 pull request received 1 new comment.
w3c/webrtc-provisional-stats
-
1 pull request opened.
-
Remove rtxSsrc which was moved to webrtc-stats w3c/webrtc-provisional-stats#42, by @fippo.
-
-
1 pull request merged.
-
Remove rtxSsrc which was moved to webrtc-stats w3c/webrtc-provisional-stats#42.
-
-
1 pull request received 1 new comment.
-
Remove rtxSsrc which was moved to webrtc-stats w3c/webrtc-provisional-stats#42 (1 comment by @vr000m)
-
TR publications
-
8 documents published.
-
Identifiers for WebRTC's Statistics API published as a Candidate Recommendation Draft. History of Identifiers for WebRTC's Statistics API
-
WebRTC Encoded Transform published twice as a Working Draft. History of WebRTC Encoded Transform
-
Region Capture published as a Working Draft. History of Region Capture
-
Screen Capture published as a Working Draft. History of Screen Capture
-
WebRTC Extended Use Cases published 3 times as a Draft Note. History of WebRTC Extended Use Cases
-
Past meetings
-
1 meeting.
Participants
-
3 participants joined.
-
Stefan Holmer (Google LLC) joined.
-
Bhavani Gopalakrishna Rao (NVIDIA) joined.
-
Alfred Heggestad (NVIDIA) joined.
-
-
1 participant left.
-
Stefan Håkansson (ERICSSON) left.
-
GitHub
w3c/mediacapture-main
-
2 issues opened.
-
Should devicechange fire when the device info changes? w3c/mediacapture-main#966, by @chrisguttandin.
-
deviceId in permissions.query() is unimplemented fingerprinting surface w3c/mediacapture-main#965, by @jan-ivar.
-
-
1 issue received 2 new comments.
-
Should devicechange fire when the device info changes? w3c/mediacapture-main#966 (2 comments by @guidou, @youennf)
-
-
3 pull requests opened.
-
Remove DevicePermissionDescriptor deviceId. w3c/mediacapture-main#968, by @jan-ivar.
-
Update to latest ReSpec version 34.1.6 w3c/mediacapture-main#967, by @dontcallmedom.
-
Add caniuse link. w3c/mediacapture-main#964, by @jan-ivar.
-
-
1 pull request merged.
-
Update to latest ReSpec version 34.1.6 w3c/mediacapture-main#967.
-
-
1 pull request received 4 new comments.
-
Remove DevicePermissionDescriptor deviceId. w3c/mediacapture-main#968 (4 comments by @jan-ivar, @youennf)
-
w3c/webrtc-pc
-
1 issue closed.
-
3 pull requests opened.
-
editorial: fix setParameterOptions usage in table of contents w3c/webrtc-pc#2887, by @fippo.
-
Update to ReSpec version 34.1.6 w3c/webrtc-pc#2886, by @dontcallmedom.
-
Add empty RTCSetParameterOptions dict as argument to setParameters w3c/webrtc-pc#2885, by @fippo.
-
-
3 pull requests merged.
-
Update to ReSpec version 34.1.6 w3c/webrtc-pc#2886.
-
Add empty RTCSetParameterOptions dict as argument to setParameters w3c/webrtc-pc#2885.
-
Don't fire connectionstatechange on pc.close(). w3c/webrtc-pc#2876.
-
-
1 pull request received 10 new comments.
-
Add empty RTCSetParameterOptions dict as argument to setParameters w3c/webrtc-pc#2885 (10 comments by @dontcallmedom, @fippo, @jan-ivar, @Orphis)
-
w3c/webrtc-extensions
-
1 issue closed.
-
When are keyframes generated? w3c/webrtc-extensions#158.
-
-
1 issue received 1 new comment.
-
1 pull request opened.
-
editorial: fix respec / validation woes w3c/webrtc-extensions#173, by @fippo.
-
-
2 pull requests merged.
-
editorial: fix respec / validation woes w3c/webrtc-extensions#173.
-
Request keyframe via setParameters w3c/webrtc-extensions#167.
-
-
4 pull requests received 29 new comments.
-
Request keyframe via setParameters w3c/webrtc-extensions#167 (23 comments by @aboba, @dontcallmedom, @fippo, @henbos, @jan-ivar)
-
w3c/webrtc-nv-use-cases
-
3 issues closed.
-
Requirement N22 is hardware specific w3c/webrtc-nv-use-cases#115.
-
Section 3.2: Clarify Cloud Gaming Requirements w3c/webrtc-nv-use-cases#114.
-
Removing Section 3.9: Reduced Complexity Signaling w3c/webrtc-nv-use-cases#109.
-
-
1 issue reopened.
-
Section 3.2.1: Improvements for game pad input w3c/webrtc-nv-use-cases#94, by @aboba.
-
-
1 issue received 2 new comments.
-
Section 3.2: Clarify Cloud Gaming Requirements w3c/webrtc-nv-use-cases#114 (2 comments by @aboba, @xingri)
-
-
5 pull requests opened.
-
Section 3.2.2: Clarify meaning of "low latency" w3c/webrtc-nv-use-cases#121, by @aboba.
-
Section 3.2.2: Add requirements N13 and N16 w3c/webrtc-nv-use-cases#120, by @aboba.
-
Section 3.2: Streaming should not require user prompts without sending media w3c/webrtc-nv-use-cases#119, by @xingri.
-
Section 3.2.1: Add N48 - bandwidth feedback speed w3c/webrtc-nv-use-cases#118, by @xingri.
-
Section 3.2.1: Update Requirement N37 w3c/webrtc-nv-use-cases#117, by @aboba.
-
-
3 pull requests merged.
-
Section 3.2: Streaming should not require user prompts without sending media w3c/webrtc-nv-use-cases#119.
-
Req N22: Remove specific hardware reference (GPU) w3c/webrtc-nv-use-cases#116.
-
Remove Section 3.9: Reduced Complexity Signaling w3c/webrtc-nv-use-cases#112.
-
-
1 pull request reopened.
-
Section 3.2.1: Add N48 - bandwidth feedback speed w3c/webrtc-nv-use-cases#118, by @xingri.
-
-
5 pull requests received 23 new comments.
-
Section 3.2: Streaming should not require user prompts without sending media w3c/webrtc-nv-use-cases#119 (11 comments by @aboba, @alvestrand, @henbos, @jan-ivar, @xingri)
-
Section 3.2.1: Add N48 - bandwidth feedback speed w3c/webrtc-nv-use-cases#118 (6 comments by @aboba, @henbos, @steely-glint, @xingri)
-
N29: A way to obtain user consent for one-way media and data use cases w3c/webrtc-nv-use-cases#14 (3 comments by @steely-glint, @youennf)
-
Section 3.2.2: Clarify meaning of "low latency" w3c/webrtc-nv-use-cases#121 (2 comments by @aboba, @steely-glint)
-
w3c/webrtc-encoded-transform
-
1 issue opened.
-
Introduction: Add figure and discussion of limitations w3c/webrtc-encoded-transform#197, by @aboba.
-
-
2 issues closed.
-
Clarify why the writable stream backpressure should be disabled w3c/webrtc-encoded-transform#188.
-
shouldTriggerKeyFrame flag is set backwards w3c/webrtc-encoded-transform#183.
-
-
4 issues received 4 new comments.
-
Clarify why the writable stream backpressure should be disabled w3c/webrtc-encoded-transform#188 (1 comment by @alvestrand)
-
shouldTriggerKeyFrame flag is set backwards w3c/webrtc-encoded-transform#183 (1 comment by @youennf)
-
Promises in [[pendingKeyFrameTasks]] are not settled when the encoder is destroyed, or a simulcast encoding goes away w3c/webrtc-encoded-transform#184 (1 comment by @youennf)
-
Writing chunks other than frames to RTCRtpScriptTransformer should fail w3c/webrtc-encoded-transform#191 (1 comment by @youennf)
-
-
3 pull requests opened.
-
shouldTriggerKeyFrame flag is set backwards. w3c/webrtc-encoded-transform#196, by @youennf.
-
Use Infinity as highWaterMark value instead of having the sizeAlgorithm returning zero w3c/webrtc-encoded-transform#195, by @youennf.
-
Make use of the pullAlgorithm by rewriting readEncodedData to return a promise w3c/webrtc-encoded-transform#194, by @youennf.
-
-
2 pull requests merged.
-
Use Infinity as highWaterMark value instead of having the sizeAlgorithm returning zero w3c/webrtc-encoded-transform#195.
-
shouldTriggerKeyFrame flag is set backwards. w3c/webrtc-encoded-transform#196.
-
-
1 pull request received 3 new comments.
-
Use Infinity as highWaterMark value instead of having the sizeAlgorithm returning zero w3c/webrtc-encoded-transform#195 (3 comments by @jan-ivar)
-
w3c/mediacapture-surface-control
-
1 issue opened.
-
What value should `Event.isTrusted` have? w3c/mediacapture-surface-control#1, by @rowan-m.
-
w3c/webrtc-stats
-
1 issue reopened.
-
RTX and FEC stats are incomplete. w3c/webrtc-stats#751, by @alvestrand.
-
-
1 issue received 3 new comments.
-
3 pull requests opened.
-
Remove duplicate RTCInboundRtpStreamStats `kind` w3c/webrtc-stats#766, by @fippo.
-
add rtxSsrc to inbound-rtp and outbound-rtp stats and fecSsrc to inbound-rtp w3c/webrtc-stats#765, by @fippo.
-
editorial: replace some lower-case `ssrc` with uppercase `SSRC` w3c/webrtc-stats#764, by @fippo.
-
-
1 pull request merged.
-
editorial: replace some lower-case `ssrc` with uppercase `SSRC` w3c/webrtc-stats#764.
-
-
1 pull request received 5 new comments.
-
add rtxSsrc to inbound-rtp and outbound-rtp stats and fecSsrc to inbound-rtp w3c/webrtc-stats#765 (5 comments by @fippo, @henbos)
-
w3c/mediacapture-output
-
1 issue opened.
-
Undesirable prompt from selectAudioOutput({deviceId}) if valid device removed w3c/mediacapture-output#137, by @jan-ivar.
-
w3c/mediacapture-screen-share
-
1 issue opened.
-
Should we deprecate `no-focus-change`? w3c/mediacapture-screen-share#271, by @youennf.
-
-
3 issues received 7 new comments.
-
Allow apps to avoid riskier display-surface types w3c/mediacapture-screen-share#261 (3 comments by @eladalon1983, @youennf)
-
Should we deprecate `no-focus-change`? w3c/mediacapture-screen-share#271 (3 comments by @eladalon1983, @youennf)
-
-
2 pull requests opened.
-
Reflow with tidy w3c/mediacapture-screen-share#273, by @dontcallmedom.
-
Add [=this=] to mean controller and clean up in parallel controller.[[FocusBehavior]] access. w3c/mediacapture-screen-share#272, by @jan-ivar.
-
-
1 pull request merged.
-
Add [=this=] to mean controller and clean up in parallel controller.[[FocusBehavior]] access. w3c/mediacapture-screen-share#272.
-
-
1 pull request closed.
-
Reflow with tidy w3c/mediacapture-screen-share#266.
-
-
4 pull requests received 13 new comments.
-
Update how FocusChangeDisabled is set to true in case of change of focus w3c/mediacapture-screen-share#264 (8 comments by @eladalon1983, @jan-ivar, @youennf)
-
Add [=this=] to mean controller and clean up in parallel controller.[[FocusBehavior]] access. w3c/mediacapture-screen-share#272 (2 comments by @eladalon1983)
-
w3c/mediacapture-region
-
2 pull requests opened.
-
Properly define the [[Element]] internal slot w3c/mediacapture-region#79, by @eladalon1983.
-
Run formatter w3c/mediacapture-region#78, by @eladalon1983.
-
-
2 pull requests merged.
-
Properly define the [[Element]] internal slot w3c/mediacapture-region#79.
-
Run formatter w3c/mediacapture-region#78.
-
-
1 pull request received 1 new comment.
-
Properly define the [[Element]] internal slot w3c/mediacapture-region#79 (1 comment by @eladalon1983)
-
w3c/mediacapture-extensions
-
1 issue received 11 new comments.
-
[Track Stats API] track.getFrameStats() allocates memory, adding to the GC pile w3c/mediacapture-extensions#98 (11 comments by @henbos, @padenot, @youennf)
-
TR publications
-
8 documents published.
-
Media Capture and Streams published as a Candidate Recommendation Draft. History of Media Capture and Streams
-
Identifiers for WebRTC's Statistics API published as a Candidate Recommendation Draft. History of Identifiers for WebRTC's Statistics API
-
Screen Capture published as a Working Draft. History of Screen Capture
-
WebRTC Encoded Transform published twice as a Working Draft. History of WebRTC Encoded Transform
-
WebRTC Extended Use Cases published 3 times as a Draft Note. History of WebRTC Extended Use Cases
-
Past meetings
-
1 meeting.
Participants
-
1 participant joined.
-
Frédéric Wang Nélar (Igalia) joined.
-
-
3 participants left.
-
Ben Schwartz (Google LLC) left.
-
Eric Rescorla (Mozilla Foundation) left.
-
Dag-Inge Aas (Daily, Co) left.
-
GitHub
w3c/mediacapture-screen-share
-
2 issues closed.
-
no-focus-change is misleading w3c/mediacapture-screen-share#263.
-
Proposal: Make CaptureController inherit from EventTarget w3c/mediacapture-screen-share#268.
-
-
3 issues received 12 new comments.
-
Allow apps to avoid riskier display-surface types w3c/mediacapture-screen-share#261 (10 comments by @Coread, @dontcallmedom-bot, @eladalon1983, @jan-ivar, @steely-glint, @youennf)
-
Proposal: Make CaptureController inherit from EventTarget w3c/mediacapture-screen-share#268 (1 comment by @dontcallmedom-bot)
-
-
1 pull request opened.
-
Define "focus-capturing-application" w3c/mediacapture-screen-share#270, by @eladalon1983.
-
-
2 pull requests merged.
-
Define "focus-capturing-application" w3c/mediacapture-screen-share#270.
-
Make CaptureController inherit from EventTarget w3c/mediacapture-screen-share#269.
-
-
1 pull request received 7 new comments.
-
Make CaptureController inherit from EventTarget w3c/mediacapture-screen-share#269 (7 comments by @eladalon1983, @fred-wang, @jan-ivar, @youennf)
-
w3c/webrtc-nv-use-cases
-
2 issues opened.
-
Requirement N22 is hardware specific w3c/webrtc-nv-use-cases#115, by @aboba.
-
Section 3.2: Clarify Cloud Gaming Requirements w3c/webrtc-nv-use-cases#114, by @xingri.
-
-
3 issues closed.
-
Removing Section 3.7: Machine Learning w3c/webrtc-nv-use-cases#110.
-
API for codec performance w3c/webrtc-nv-use-cases#41.
-
Send transferable data w3c/webrtc-nv-use-cases#42.
-
-
6 issues received 15 new comments.
-
Section 3.2: Clarify Cloud Gaming Requirements w3c/webrtc-nv-use-cases#114 (10 comments by @aboba, @xingri)
-
Section 3.2: Feedback related to WebRTC-NV Low Latency Streaming Use Case w3c/webrtc-nv-use-cases#103 (1 comment by @aboba)
-
-
4 pull requests opened.
-
Req N22: Remove specific hardware reference (GPU) w3c/webrtc-nv-use-cases#116, by @aboba.
-
Remove Machine Learning Use Case (Section 3.7) w3c/webrtc-nv-use-cases#113, by @aboba.
-
Remove Section 3.9: Reduced Complexity Signaling w3c/webrtc-nv-use-cases#112, by @aboba.
-
Update Cloud Game Providers information w3c/webrtc-nv-use-cases#111, by @xingri.
-
-
2 pull requests merged.
-
Remove Machine Learning Use Case (Section 3.7) w3c/webrtc-nv-use-cases#113.
-
Update Cloud Game Providers information w3c/webrtc-nv-use-cases#111.
-
-
3 pull requests received 6 new comments.
-
Remove Section 3.9: Reduced Complexity Signaling w3c/webrtc-nv-use-cases#112 (3 comments by @aboba, @dontcallmedom-bot)
-
Remove Machine Learning Use Case (Section 3.7) w3c/webrtc-nv-use-cases#113 (2 comments by @aboba, @dontcallmedom-bot)
-
w3c/webrtc-encoded-transform
-
9 issues opened.
-
Underspecified rid checking in sender.generateKeyFrame(["x"]); shouldn't throw NotAllowedError w3c/webrtc-encoded-transform#192, by @jan-ivar.
-
Writing chunks other than frames to RTCRtpScriptTransformer should fail w3c/webrtc-encoded-transform#191, by @docfaraday.
-
What should happen if RTCRtpSender/Receiver.transform is set with the same transform that is already set? w3c/webrtc-encoded-transform#189, by @docfaraday.
-
Clarify why the writable stream backpressure should be disabled w3c/webrtc-encoded-transform#188, by @saschanaz.
-
Pass `pullAlgorithm` while initializing `[[readable]]`? w3c/webrtc-encoded-transform#187, by @saschanaz.
-
What does sender.generateKeyFrame() do when sender.track is null, ended or disabled? w3c/webrtc-encoded-transform#185, by @jan-ivar.
-
Promises in [[pendingKeyFrameTasks]] are not settled when the encoder is destroyed, or a simulcast encoding goes away w3c/webrtc-encoded-transform#184, by @docfaraday.
-
shouldTriggerKeyFrame flag is set backwards w3c/webrtc-encoded-transform#183, by @docfaraday.
-
EncodedVideoFrame needs to be marked serializable w3c/webrtc-encoded-transform#181, by @alvestrand.
-
-
1 issue closed.
-
Underspecified rid checking in sender.generateKeyFrame(["x"]); shouldn't throw NotAllowedError w3c/webrtc-encoded-transform#192.
-
-
8 issues received 16 new comments.
-
What does sender.generateKeyFrame() do when sender.track is null, ended or disabled? w3c/webrtc-encoded-transform#185 (5 comments by @fippo, @jan-ivar, @youennf)
-
EncodedVideoFrame needs to be marked serializable w3c/webrtc-encoded-transform#181 (3 comments by @jan-ivar, @youennf)
-
Underspecified rid checking in sender.generateKeyFrame(["x"]); shouldn't throw NotAllowedError w3c/webrtc-encoded-transform#192 (2 comments by @jan-ivar)
-
Pass `pullAlgorithm` while initializing `[[readable]]`? w3c/webrtc-encoded-transform#187 (2 comments by @saschanaz, @youennf)
-
Tell SDP negotiation to negotiate support for non-standard codecs w3c/webrtc-encoded-transform#172 (1 comment by @dontcallmedom-bot)
-
Clarify why the writable stream backpressure should be disabled w3c/webrtc-encoded-transform#188 (1 comment by @youennf)
-
What should happen if RTCRtpSender/Receiver.transform is set with the same transform that is already set? w3c/webrtc-encoded-transform#189 (1 comment by @youennf)
-
Add a metadata modifying method to RTCEncodedFrame w3c/webrtc-encoded-transform#162 (1 comment by @jan-ivar)
-
-
4 pull requests opened.
-
s/NotAllowedError/TypeError for invalid rid & reference RFC8851. w3c/webrtc-encoded-transform#193, by @jan-ivar.
-
Editorial: Use AbortController/signal to access controller's signal w3c/webrtc-encoded-transform#190, by @shaseley.
-
Add description of an API for controlling SDP codec negotiation w3c/webrtc-encoded-transform#186, by @alvestrand.
-
Add Serializable attributes to encoded video frames w3c/webrtc-encoded-transform#182, by @alvestrand.
-
-
1 pull request merged.
-
s/NotAllowedError/TypeError for invalid rid & reference RFC8851. w3c/webrtc-encoded-transform#193.
-
-
3 pull requests received 18 new comments.
-
Add description of an API for controlling SDP codec negotiation w3c/webrtc-encoded-transform#186 (12 comments by @aboba, @alvestrand, @dontcallmedom-bot, @fippo, @henbos, @jtsiskin)
-
s/NotAllowedError/TypeError for invalid rid & reference RFC8851. w3c/webrtc-encoded-transform#193 (2 comments by @jan-ivar, @youennf)
-
w3c/webrtc-pc
-
4 issues opened.
-
Need to mark codec-related definitions for export w3c/webrtc-pc#2881, by @alvestrand.
-
Clarify unmute event must fire on receiver.track AFTER sRD(offer) succeeds w3c/webrtc-pc#2880, by @jan-ivar.
-
What is the state of a connection with only administratively prohibited candidates? w3c/webrtc-pc#2879, by @alvestrand.
-
iceConnectionState "checking" can happen without adding remote candidates w3c/webrtc-pc#2878, by @fippo.
-
-
3 issues closed.
-
iceConnectionState "checking" can happen without adding remote candidates w3c/webrtc-pc#2878.
-
Maybe removeTrack should be a no-op on [[Stopping]] as well as [[Stopped]]? w3c/webrtc-pc#2874.
-
Unclear how URLs are processed w3c/webrtc-pc#2660.
-
-
6 issues received 10 new comments.
-
Add support for WebRTC Data Channel in Workers w3c/webrtc-pc#230 (4 comments by @aboba, @Diego-Perez-Botero, @SahilAggarwal2004)
-
The steps in "Update the connection state" say to fire connectionstatechange when [[IsClosed]] is set to true w3c/webrtc-pc#2865 (2 comments by @jan-ivar)
-
iceConnectionState "checking" can happen without adding remote candidates w3c/webrtc-pc#2878 (1 comment by @alvestrand)
-
addIceCandidate may not need to throw an error when no remoteDescription w3c/webrtc-pc#2519 (1 comment by @fbarbat)
-
need more clarifying? about example in MDN WebRTC perfect negotiation pattern w3c/webrtc-pc#2806 (1 comment by @Adamkaram)
-
What is the state of a connection with only administratively prohibited candidates? w3c/webrtc-pc#2879 (1 comment by @fippo)
-
-
5 pull requests opened.
-
Clarify description of "checking" iceConnectionState w3c/webrtc-pc#2884, by @fippo.
-
Update to ReSpec version 34.1.4 w3c/webrtc-pc#2883, by @dontcallmedom.
-
Update to ReSpec version 34.1.3 w3c/webrtc-pc#2882, by @dontcallmedom.
-
Update to ReSpec version 34.1.2 w3c/webrtc-pc#2877, by @dontcallmedom.
-
Don't fire connectionstatechange on pc.close(). w3c/webrtc-pc#2876, by @jan-ivar.
-
-
7 pull requests merged.
-
Clarify description of "checking" iceConnectionState w3c/webrtc-pc#2884.
-
Update to ReSpec version 34.1.4 w3c/webrtc-pc#2883.
-
Update to ReSpec version 34.1.3 w3c/webrtc-pc#2882.
-
Make removeTrack() a no-op after transceiver.stop() w3c/webrtc-pc#2875.
-
Update to ReSpec version 34.1.2 w3c/webrtc-pc#2877.
-
Use the url spec to parse ice server urls (Take 2). w3c/webrtc-pc#2853.
-
editorial: export RTCRtpTransceiver "transceiver kind" w3c/webrtc-pc#2872.
-
-
1 pull request closed.
-
Add RTCPeerConnection.getDataChannels() w3c/webrtc-pc#2770.
-
-
4 pull requests received 11 new comments.
-
Don't fire connectionstatechange on pc.close(). w3c/webrtc-pc#2876 (5 comments by @alvestrand, @dontcallmedom, @jan-ivar)
-
Make removeTrack() a no-op after transceiver.stop() w3c/webrtc-pc#2875 (3 comments by @henbos, @jan-ivar, @youennf)
-
Clarify description of "checking" iceConnectionState w3c/webrtc-pc#2884 (2 comments by @dontcallmedom, @fippo)
-
w3c/webrtc-extensions
-
3 issues opened.
-
Extensions have different level of maturity. How se should we clarify this for spec readers? w3c/webrtc-extensions#172, by @youennf.
-
ICE improvements: select a candidate pair w3c/webrtc-extensions#171, by @sam-vi.
-
ICE improvements: remove candidate pairs w3c/webrtc-extensions#170, by @sam-vi.
-
-
4 issues received 6 new comments.
-
ICE improvements: select a candidate pair w3c/webrtc-extensions#171 (3 comments by @dontcallmedom-bot, @jan-ivar, @oanguenot)
-
Extensions have different level of maturity. How se should we clarify this for spec readers? w3c/webrtc-extensions#172 (1 comment by @henbos)
-
ICE improvements: remove candidate pairs w3c/webrtc-extensions#170 (1 comment by @dontcallmedom-bot)
-
ICE improvements: prevent candidate pair removal w3c/webrtc-extensions#166 (1 comment by @dontcallmedom-bot)
-
-
1 pull request opened.
-
Fix mistake in internal slot assignment for NegotiatedHeaderExtensions w3c/webrtc-extensions#169, by @alvestrand.
-
-
1 pull request merged.
-
Fix mistake in internal slot assignment for NegotiatedHeaderExtensions w3c/webrtc-extensions#169.
-
-
3 pull requests received 20 new comments.
-
Prevent candidate pair removal w3c/webrtc-extensions#168 (13 comments by @dontcallmedom-bot, @henbos, @jan-ivar, @pthatcher, @sam-vi, @youennf)
-
Request keyframe via setParameters w3c/webrtc-extensions#167 (6 comments by @dontcallmedom, @dontcallmedom-bot, @fippo)
-
Add RTCRtpEncodingParameters.codec to change the active codec w3c/webrtc-extensions#147 (1 comment by @dontcallmedom-bot)
-
w3c/mediacapture-extensions
-
1 issue opened.
-
Extensions have different level of maturity. How se should we clarify this for spec readers? w3c/mediacapture-extensions#100, by @youennf.
-
-
1 issue received 10 new comments.
-
[Track Stats API] track.getFrameStats() allocates memory, adding to the GC pile w3c/mediacapture-extensions#98 (10 comments by @henbos, @jan-ivar, @youennf)
-
w3c/mediacapture-screen-share-extensions
-
2 issues received 6 new comments.
-
Capturing audio-only w3c/mediacapture-screen-share-extensions#12 (4 comments by @chrisguttandin, @eladalon1983, @schreibmachine)
-
Auto-pause capture when user switches captured content w3c/mediacapture-screen-share-extensions#4 (2 comments by @dontcallmedom-bot, @eladalon1983)
-
w3c/mediacapture-main
-
2 issues received 3 new comments.
-
enabled=false MediaStreamTrack handling for HTMLVideoElement w3c/mediacapture-main#961 (2 comments by @jan-ivar, @youennf)
-
'label' needs direction and language metadata w3c/mediacapture-main#665 (1 comment by @dontcallmedom)
-
-
2 pull requests opened.
-
Update to latest ReSpec version 34.1.4 w3c/mediacapture-main#963, by @dontcallmedom.
-
Update to latest ReSpec version 34.1.3 w3c/mediacapture-main#962, by @dontcallmedom.
-
-
2 pull requests merged.
-
Update to latest ReSpec version 34.1.4 w3c/mediacapture-main#963.
-
Update to latest ReSpec version 34.1.3 w3c/mediacapture-main#962.
-
w3c/webrtc-stats
-
2 issues closed.
-
Clarify FlexFEC stats w3c/webrtc-stats#555.
-
add framesInput stats to rtcoutboundrtpstreamstats w3c/webrtc-stats#761.
-
-
5 issues received 11 new comments.
-
add framesInput stats to rtcoutboundrtpstreamstats w3c/webrtc-stats#761 (5 comments by @bdrtc, @henbos)
-
-
2 pull requests opened.
-
Delete 'retiring stats objects' section. w3c/webrtc-stats#763, by @henbos.
-
Specify fecBytesReceived w3c/webrtc-stats#762, by @fippo.
-
-
1 pull request merged.
-
Specify fecBytesReceived w3c/webrtc-stats#762.
-
-
1 pull request received 11 new comments.
w3c/webrtc-ice
-
1 issue reopened.
-
https://github.com/dotnet/docs/issues?q=is%3Apr+is%3Aclosed+mentions%3Asoon2849 w3c/webrtc-ice#46, by @soon2849.
-
w3c/mediacapture-viewport
-
1 pull request merged.
-
Add Tove to the list of editors w3c/mediacapture-viewport#24.
-
-
1 pull request received 3 new comments.
-
Add Tove to the list of editors w3c/mediacapture-viewport#24 (3 comments by @henbos, @jan-ivar, @tovepet)
-
w3c/mediacapture-record
-
1 issue received 1 new comment.
w3c/webrtc-svc
-
1 issue closed.
-
What's the default behaviour when user not specify scalabilityMode? w3c/webrtc-svc#94.
-
-
1 issue received 1 new comment.
-
What's the default behaviour when user not specify scalabilityMode? w3c/webrtc-svc#94 (1 comment by @bdrtc)
-
TR publications
-
4 documents published.
-
Identifiers for WebRTC's Statistics API published as a Candidate Recommendation Draft. History of Identifiers for WebRTC's Statistics API
-
Audio Output Devices API published as a Candidate Recommendation Draft. History of Audio Output Devices API
-
Media Capture and Streams published as a Candidate Recommendation Draft. History of Media Capture and Streams
-
MediaStream Recording published as a Working Draft. History of MediaStream Recording
-
Past meetings
-
1 meeting.
GitHub
w3c/webrtc-pc
-
5 issues opened.
-
Maybe removeTrack should be a no-op on [[Stopping]] as well as [[Stopped]]? w3c/webrtc-pc#2874, by @jan-ivar.
-
scaleResolutionDownBy validation steps are inconsistent, browser interop issues w3c/webrtc-pc#2873, by @henbos.
-
Why clear [[LastCreatedOffer]] and [[LastCreatedAnswer]] when going to "stable"? w3c/webrtc-pc#2869, by @jan-ivar.
-
Remote tracks width and height settings in case of rotated video w3c/webrtc-pc#2867, by @youennf.
-
-
2 issues closed.
-
Steps for updating RTCPeerConnection.[[IceConnectionState]] are missing? w3c/webrtc-pc#2858.
-
-
9 issues received 21 new comments.
-
scaleResolutionDownBy validation steps are inconsistent, browser interop issues w3c/webrtc-pc#2873 (5 comments by @henbos, @jan-ivar)
-
Maybe removeTrack should be a no-op on [[Stopping]] as well as [[Stopped]]? w3c/webrtc-pc#2874 (3 comments by @jan-ivar)
-
Why clear [[LastCreatedOffer]] and [[LastCreatedAnswer]] when going to "stable"? w3c/webrtc-pc#2869 (1 comment by @jan-ivar)
-
Handling of duplicate rids in sRD seems underspecified w3c/webrtc-pc#2780 (1 comment by @dontcallmedom-bot)
-
Hard to tell if there are state gaps in connectionState algorithm w3c/webrtc-pc#2827 (1 comment by @dontcallmedom-bot)
-
Maybe setParameters/insertDtmf/replaceTrack should reject on [[Stopping]] as well as [[Stopped]]? w3c/webrtc-pc#2820 (1 comment by @dontcallmedom-bot)
-
Why is RTCIceCandidatePairStats.totalRoundTripTime mandatory to implement, but not responsesReceived? w3c/webrtc-pc#2819 (1 comment by @dontcallmedom-bot)
-
5 pull requests opened.
-
Make removeTrack() a no-op after transceiver.stop() w3c/webrtc-pc#2875, by @jan-ivar.
-
editorial: export RTCRtpTransceiver "transceiver kind" w3c/webrtc-pc#2872, by @fippo.
-
Reorder RTCIceTransportState enum to match RTCIceConnectionState enum. w3c/webrtc-pc#2870, by @jan-ivar.
-
Update to ReSpec version 34.1.1 w3c/webrtc-pc#2868, by @dontcallmedom.
-
Update to ReSpec version 34.1.0 w3c/webrtc-pc#2866, by @dontcallmedom.
-
-
5 pull requests merged.
-
Reorder RTCIceTransportState enum to match RTCIceConnectionState enum. w3c/webrtc-pc#2870.
-
Fix connectionState to return [[ConnectionState]]. w3c/webrtc-pc#2859.
-
Update to ReSpec version 34.1.1 w3c/webrtc-pc#2868.
-
Use markup conventions for algorithms w3c/webrtc-pc#2818.
-
Update to ReSpec version 34.1.0 w3c/webrtc-pc#2866.
-
-
9 pull requests received 11 new comments.
-
Prune createAnswer()'s encodings and [[SendEncodings]] in sLD(answer). w3c/webrtc-pc#2801 (2 comments by @dontcallmedom-bot)
-
Reorder RTCIceTransportState enum to match RTCIceConnectionState enum. w3c/webrtc-pc#2870 (1 comment by @jan-ivar)
-
Don't let offers to receive simulcast overwrite existing [[SendEncodings]] w3c/webrtc-pc#2758 (1 comment by @dontcallmedom-bot)
-
Remove duplicate rids in proposedSendEncodings. w3c/webrtc-pc#2800 (1 comment by @dontcallmedom-bot)
-
Express RTCPeerConnectionState values using [[IceConnectionState]], and reduce complexity w3c/webrtc-pc#2828 (1 comment by @dontcallmedom-bot)
-
setParameters(), replaceTrack(), & insertDTMF() reject after stop(). w3c/webrtc-pc#2829 (1 comment by @dontcallmedom-bot)
w3c/webrtc-svc
-
3 issues opened.
-
What's the default behaviour when user not specify scalabilityMode? w3c/webrtc-svc#94, by @bdrtc.
-
Align exposing `scalabilityMode` with the WebRTC "hardware capabilities" check w3c/webrtc-svc#92, by @pes10k.
-
Nit: Typos in Privacy Considerations section w3c/webrtc-svc#91, by @pes10k.
-
-
1 issue closed.
-
SVC getCapabilities() is redundant with Media Capabilities query w3c/webrtc-svc#49.
-
-
3 issues received 9 new comments.
-
Align exposing `scalabilityMode` with the WebRTC "hardware capabilities" check w3c/webrtc-svc#92 (6 comments by @aboba, @henbos, @pes10k)
-
What's the default behaviour when user not specify scalabilityMode? w3c/webrtc-svc#94 (2 comments by @aboba, @Orphis)
-
-
1 pull request opened.
-
Clarification of privacy considerations w3c/webrtc-svc#93, by @aboba.
-
-
1 pull request closed.
-
Clarification of privacy considerations w3c/webrtc-svc#93.
-
-
2 pull requests received 4 new comments.
w3c/webrtc-stats
-
5 issues opened.
-
add framesInput stats to rtcoutboundrtpstreamstats w3c/webrtc-stats#761, by @bdrtc.
-
Improve test coverage w3c/webrtc-stats#760, by @henbos.
-
Delete the obsolete section, "track" and "stream" stats - they don't exist anymore w3c/webrtc-stats#758, by @henbos.
-
RTCAudioSourceStats.audioLevel - what algorithm described in totalAudioEnergy? w3c/webrtc-stats#757, by @hamishwillee.
-
Add clarification that inbound-rtp.bytesReceived includes retransmissions. w3c/webrtc-stats#755, by @henbos.
-
-
10 issues closed.
-
Map out implementation status of getStats and make a plan w3c/webrtc-stats#595.
-
Move obsolete section to provisional spec w3c/webrtc-stats#723.
-
scalabilityMode: Same as in getParameters() or not? w3c/webrtc-stats#731.
-
What is the relationship between WebRTC stats and the Working Group? w3c/webrtc-stats#746.
-
The HW exposure check does not solve Cloud Gaming use cases w3c/webrtc-stats#730.
-
Should we flatten the hierarchy? w3c/webrtc-stats#752.
-
RTCAudioSourceStats.audioLevel - what algorithm described in totalAudioEnergy? w3c/webrtc-stats#757.
-
availableOutgoingBitrate is also available when send-side BWE is not used w3c/webrtc-stats#740.
-
Add clarification that inbound-rtp.bytesReceived includes retransmissions. w3c/webrtc-stats#755.
-
Delete the obsolete section, "track" and "stream" stats - they don't exist anymore w3c/webrtc-stats#758.
-
-
14 issues received 26 new comments.
-
Add clarification that inbound-rtp.bytesReceived includes retransmissions. w3c/webrtc-stats#755 (6 comments by @fippo, @henbos)
-
RTCAudioSourceStats.audioLevel - what algorithm described in totalAudioEnergy? w3c/webrtc-stats#757 (3 comments by @hamishwillee, @henbos)
-
Delete the obsolete section, "track" and "stream" stats - they don't exist anymore w3c/webrtc-stats#758 (3 comments by @henbos)
-
Conformance criteria incompatible with standards-track w3c/webrtc-stats#749 (2 comments by @alvestrand, @henbos)
-
The HW exposure check does not solve Cloud Gaming use cases w3c/webrtc-stats#730 (2 comments by @dontcallmedom-bot, @henbos)
-
Map out implementation status of getStats and make a plan w3c/webrtc-stats#595 (1 comment by @henbos)
-
What is the relationship between WebRTC stats and the Working Group? w3c/webrtc-stats#746 (1 comment by @henbos)
-
-
2 pull requests opened.
-
Delete the obsolete section, "track" and "stream" stats - they don't exist anymore w3c/webrtc-stats#759, by @henbos.
-
Clarify inbound-rtp RTX handling w3c/webrtc-stats#756, by @fippo.
-
-
3 pull requests merged.
-
Clarify when the candidate pair bandwidth estimation(s) exists w3c/webrtc-stats#743.
-
Clarify inbound-rtp RTX handling w3c/webrtc-stats#756.
-
Delete the obsolete section, "track" and "stream" stats - they don't exist anymore w3c/webrtc-stats#759.
-
-
1 pull request closed.
-
Expose powerEfficientEncoder/Decoder if MediaCapabilities allows it w3c/webrtc-stats#732.
-
-
4 pull requests received 10 new comments.
-
Clarify when the candidate pair bandwidth estimation(s) exists w3c/webrtc-stats#743 (4 comments by @jan-ivar)
-
Expose powerEfficientEncoder/Decoder if MediaCapabilities allows it w3c/webrtc-stats#732 (2 comments by @dontcallmedom-bot, @henbos)
-
Document recently added audio metrics as features at risk w3c/webrtc-stats#750 (1 comment by @vr000m)
-
w3c/mediacapture-extensions
-
1 issue opened.
-
mediastream cannot handle webcam data stream in yuv pixel format correctly w3c/mediacapture-extensions#99, by @Danjuanlab.
-
-
6 issues received 36 new comments.
-
[Track Stats API] track.getFrameStats() allocates memory, adding to the GC pile w3c/mediacapture-extensions#98 (30 comments by @alvestrand, @dontcallmedom-bot, @henbos, @jan-ivar, @padenot, @youennf)
-
MediaStreamTrack resizeMode constraint is too vague to request specific strategy w3c/mediacapture-extensions#7 (2 comments by @alvestrand, @anthmFS)
-
Face Detection: Variance of Results w3c/mediacapture-extensions#85 (1 comment by @dontcallmedom-bot)
-
Face Detection: Segmentation metadata w3c/mediacapture-extensions#79 (1 comment by @dontcallmedom-bot)
-
Face Detection: Scope of Applicability w3c/mediacapture-extensions#84 (1 comment by @dontcallmedom-bot)
-
Solve user agent camera/microphone double-mute w3c/mediacapture-extensions#39 (1 comment by @jan-ivar)
-
-
1 pull request merged.
-
Add face detection constraints and VideoFrameMetadata members w3c/mediacapture-extensions#78.
-
-
5 pull requests received 6 new comments.
-
Add changes to configurationchange MediaStreamTrack event w3c/mediacapture-extensions#83 (2 comments by @dontcallmedom-bot)
-
w3c/mediacapture-viewport
-
1 pull request opened.
-
Add Tove to the list of editors w3c/mediacapture-viewport#24, by @eladalon1983.
-
w3c/webrtc-encoded-transform
-
1 issue closed.
-
SFrameTransform should inherit from EventTarget w3c/webrtc-encoded-transform#175.
-
-
3 pull requests opened.
-
Fix README formatting w3c/webrtc-encoded-transform#180, by @alvestrand.
-
Make SFrameTransform inherit from EventTarget w3c/webrtc-encoded-transform#179, by @tidoust.
-
Editorial: Call AbortController's "signal abort" instead of AbortSignal's w3c/webrtc-encoded-transform#178, by @shaseley.
-
-
2 pull requests merged.
-
Editorial: Call AbortController's "signal abort" instead of AbortSignal's w3c/webrtc-encoded-transform#178.
-
Make SFrameTransform inherit from EventTarget w3c/webrtc-encoded-transform#179.
-
-
1 pull request closed.
-
Fix README formatting w3c/webrtc-encoded-transform#180.
-
-
3 pull requests received 3 new comments.
-
make generateKeyFrame take a list of rids and return a promise<undefined> w3c/webrtc-encoded-transform#165 (1 comment by @dontcallmedom-bot)
-
Add explainer for encoded frame creation w3c/webrtc-encoded-transform#164 (1 comment by @dontcallmedom-bot)
w3c/mediacapture-screen-share
-
2 issues opened.
-
Proposal: Make CaptureController inherit from EventTarget w3c/mediacapture-screen-share#268, by @eladalon1983.
-
SystemCursorEvent and cursor customization cursor w3c/mediacapture-screen-share#267, by @jozefchutka.
-
-
1 issue closed.
-
SystemCursorEvent and cursor customization cursor w3c/mediacapture-screen-share#267.
-
-
5 issues received 8 new comments.
-
no-focus-change is misleading w3c/mediacapture-screen-share#263 (3 comments by @eladalon1983, @youennf)
-
Inconsistent formatting in doc w3c/mediacapture-screen-share#234 (2 comments by @dontcallmedom, @eladalon1983)
-
Allow apps to avoid riskier display-surface types w3c/mediacapture-screen-share#261 (1 comment by @eladalon1983)
-
Proposal: Make CaptureController inherit from EventTarget w3c/mediacapture-screen-share#268 (1 comment by @fred-wang)
-
SystemCursorEvent and cursor customization cursor w3c/mediacapture-screen-share#267 (1 comment by @eladalon1983)
-
-
2 pull requests opened.
-
Make CaptureController inherit from EventTarget w3c/mediacapture-screen-share#269, by @eladalon1983.
-
Reflow with tidy w3c/mediacapture-screen-share#266, by @dontcallmedom.
-
-
1 pull request received 2 new comments.
-
Make CaptureController inherit from EventTarget w3c/mediacapture-screen-share#269 (2 comments by @eladalon1983, @youennf)
-
w3c/webrtc-extensions
-
2 issues opened.
-
ICE improvements: prevent candidate pair removal w3c/webrtc-extensions#166, by @sam-vi.
-
Enabling RTCP XR(RRTR/DLRR) support for non-senders w3c/webrtc-extensions#165, by @bdrtc.
-
-
15 issues received 23 new comments.
-
Exposing decode errors / SW fallback as an event w3c/webrtc-extensions#146 (6 comments by @aboba, @xingri)
-
Should setOfferedHeaderExtensions be allowed to restart stopped extensions? w3c/webrtc-extensions#134 (2 comments by @aboba, @dontcallmedom-bot)
-
ICE improvements: prevent candidate pair removal w3c/webrtc-extensions#166 (2 comments by @dontcallmedom-bot, @sam-vi)
-
Potential web compat issue with setOfferedRtpHeaderExtensions w3c/webrtc-extensions#130 (2 comments by @dontcallmedom-bot)
-
Do we need a control API for RTCP feedback mechanisms? w3c/webrtc-extensions#143 (1 comment by @dontcallmedom-bot)
-
RTCRtpEncodingParameters: scaleResolutionDownTo w3c/webrtc-extensions#159 (1 comment by @dontcallmedom-bot)
-
How to deal with encoder errors / codec availability errors? w3c/webrtc-extensions#127 (1 comment by @dontcallmedom-bot)
-
Negotiationless codec selection and per-encoding layer codec configuration w3c/webrtc-extensions#126 (1 comment by @dontcallmedom-bot)
-
headerExtensionsToOffer fails to freeze array w3c/webrtc-extensions#135 (1 comment by @dontcallmedom-bot)
-
headerExtensionsToOffer entries are mutable which is surprising w3c/webrtc-extensions#136 (1 comment by @dontcallmedom-bot)
-
FrozenArray on headerExtensionsToOffer a mistake, wrong semantics w3c/webrtc-extensions#137 (1 comment by @dontcallmedom-bot)
-
Suggestion: rename [[HeaderExtensionsToOffer]] to [[HeaderExtensionsSupported]] w3c/webrtc-extensions#132 (1 comment by @dontcallmedom-bot)
-
Header extension: direction woes and renames w3c/webrtc-extensions#141 (1 comment by @dontcallmedom-bot)
-
-
2 pull requests opened.
-
Prevent candidate pair removal w3c/webrtc-extensions#168, by @sam-vi.
-
Request keyframe via setParameters w3c/webrtc-extensions#167, by @fippo.
-
-
3 pull requests received 8 new comments.
-
Request keyframe via setParameters w3c/webrtc-extensions#167 (3 comments by @dontcallmedom-bot, @fippo)
-
w3c/webrtc-nv-use-cases
-
2 issues opened.
-
Removing Section 3.7: Machine Learning w3c/webrtc-nv-use-cases#110, by @aboba.
-
Removing Section 3.9: Reduced Complexity Signaling w3c/webrtc-nv-use-cases#109, by @aboba.
-
-
1 issue closed.
-
Low Latency Streaming: Review of requirements w3c/webrtc-nv-use-cases#95.
-
-
12 issues received 13 new comments.
-
Section 3.2: Feedback related to WebRTC-NV Low Latency Streaming Use Case w3c/webrtc-nv-use-cases#103 (2 comments by @aboba, @dontcallmedom-bot)
-
Section 3.10.3: Feedback related to decoding pre-encoded media use case w3c/webrtc-nv-use-cases#106 (1 comment by @dontcallmedom-bot)
-
Section 3.10.2: Feedback related to Transmitting stored encoded media use case w3c/webrtc-nv-use-cases#105 (1 comment by @dontcallmedom-bot)
-
Section 3.10.2: Introducing app content-decisions at the encoded video level isn't webby w3c/webrtc-nv-use-cases#101 (1 comment by @dontcallmedom-bot)
-
Section 3.10.1: Feedback related to Live encoded non-WebRTC media use case w3c/webrtc-nv-use-cases#104 (1 comment by @dontcallmedom-bot)
-
Section 3.10.1: Live encoded non-WebRTC media use case not compelling w3c/webrtc-nv-use-cases#100 (1 comment by @dontcallmedom-bot)
-
Section 3.10: "(outgoing/incoming) WebRTC connection" not defined w3c/webrtc-nv-use-cases#102 (1 comment by @dontcallmedom-bot)
-
Sections 3.10.1, 3.10.2 and 3.10.3: Control of packetization/depacketization w3c/webrtc-nv-use-cases#96 (1 comment by @dontcallmedom-bot)
-
Section 3.10: A little thought about the one way media use case w3c/webrtc-nv-use-cases#93 (1 comment by @dontcallmedom-bot)
-
Section 3.2.1: Improvements for game pad input w3c/webrtc-nv-use-cases#94 (1 comment by @dontcallmedom-bot)
-
-
1 pull request received 1 new comment.
-
Use case: Low Latency Broadcast with fanout w3c/webrtc-nv-use-cases#79 (1 comment by @dontcallmedom-bot)
-
w3c/mediacapture-screen-share-extensions
-
2 issues received 4 new comments.
-
Exposing mouse events from captured surfaces w3c/mediacapture-screen-share-extensions#2 (3 comments by @eladalon1983, @jozefchutka, @youennf)
-
Auto-pause capture when user switches captured content w3c/mediacapture-screen-share-extensions#4 (1 comment by @dontcallmedom-bot)
-
w3c/mediacapture-main
-
1 issue opened.
-
enabled=false MediaStreamTrack handling for HTMLVideoElement w3c/mediacapture-main#961, by @youennf.
-
-
3 issues received 5 new comments.
-
'label' needs direction and language metadata w3c/mediacapture-main#665 (3 comments by @aphillips, @dontcallmedom, @fippo)
-
Web compat issue with permissions.query() in non-persistent permission models w3c/mediacapture-main#928 (1 comment by @dontcallmedom-bot)
-
Web compat issue with permissions.query() in per-camera/mic permission models w3c/mediacapture-main#927 (1 comment by @dontcallmedom-bot)
-
-
2 pull requests opened.
-
Update to latest ReSpec version 34.1.1 w3c/mediacapture-main#960, by @dontcallmedom.
-
Add mediaDevices arg to [=exposure decision algorithm for devices other than camera and microphone=]. w3c/mediacapture-main#959, by @jan-ivar.
-
-
4 pull requests merged.
-
Remove focus requirement on enumerateDevices, for real this time #912. w3c/mediacapture-main#937.
-
Remove focus from mute/unmute SHOULD prose to match #912 best practice. w3c/mediacapture-main#936.
-
Update to latest ReSpec version 34.1.1 w3c/mediacapture-main#960.
-
Add mediaDevices arg to [=exposure decision algorithm for devices other than camera and microphone=]. w3c/mediacapture-main#959.
-
-
1 pull request received 4 new comments.
-
Add note about deviceId and groupId inconsistency with other capabilities. w3c/mediacapture-main#942 (4 comments by @alvestrand, @jan-ivar)
-
w3c/mediacapture-record
-
1 issue closed.
-
What to do both videoKeyFrameIntervalDuration and videoKeyFrameIntervalCount are specified? w3c/mediacapture-record#219.
-
-
1 issue received 3 new comments.
-
What to do both videoKeyFrameIntervalDuration and videoKeyFrameIntervalCount are specified? w3c/mediacapture-record#219 (3 comments by @handellm, @Pehrsons, @youennf)
-
-
1 pull request opened.
-
Throw NotSupportedError if both videoKeyFrameIntervalDuration and videoKeyFrameIntervalCount are set w3c/mediacapture-record#220, by @youennf.
-
-
1 pull request merged.
-
Throw NotSupportedError if both videoKeyFrameIntervalDuration and videoKeyFrameIntervalCount are set w3c/mediacapture-record#220.
-
-
1 pull request received 1 new comment.
-
Throw NotSupportedError if both videoKeyFrameIntervalDuration and videoKeyFrameIntervalCount are set w3c/mediacapture-record#220 (1 comment by @handellm)
-
w3c/mediacapture-transform
-
1 issue opened.
-
VideoTrackGenerator should have an 'owning' WritableStream w3c/mediacapture-transform#89, by @youennf.
-
w3c/mediacapture-output
-
2 pull requests opened.
-
Use relevant settings objects. w3c/mediacapture-output#136, by @jan-ivar.
-
Use the [=creating a device info object=] algorithm. w3c/mediacapture-output#135, by @jan-ivar.
-
-
1 pull request merged.
-
Use the [=creating a device info object=] algorithm. w3c/mediacapture-output#135.
-
-
1 pull request received 1 new comment.
w3c/mediacapture-automation
-
1 issue closed.
-
Broken references in Media Capture Automation w3c/mediacapture-automation#2.
-
-
1 pull request merged.
-
Fix links with respec autolinks where possible w3c/mediacapture-automation#3.
-
TR publications
-
15 documents published.
-
Identifiers for WebRTC's Statistics API published twice as a Candidate Recommendation Draft. History of Identifiers for WebRTC's Statistics API
-
Media Capture and Streams published 3 times as a Candidate Recommendation Draft. History of Media Capture and Streams
-
WebRTC Encoded Transform published twice as a Working Draft. History of WebRTC Encoded Transform
-
MediaStream Recording published twice as a Working Draft. History of MediaStream Recording
-
Scalable Video Coding (SVC) Extension for WebRTC published 4 times as a Working Draft. History of Scalable Video Coding (SVC) Extension for WebRTC
-
Screen Capture published as a Working Draft. History of Screen Capture
-
WebRTC Extended Use Cases published as a Draft Note. History of WebRTC Extended Use Cases
-
Past meetings
-
1 meeting.
Participants
-
1 participant left.
-
Shachar Zohar (Peer5) left.
-
-
1 organization left.
-
Peer5 left.
-
GitHub
w3c/mediacapture-output
-
1 issue received 4 new comments.
-
Controlling 3rd party iframe audio output on a page? w3c/mediacapture-output#63 (4 comments by @dontcallmedom, @ErikDombi, @hoch, @MatanYemini)
-
w3c/webrtc-encoded-transform
-
2 issues received 3 new comments.
-
1 pull request opened.
-
fix RTCEncodedVideoFrameMeta contributingSources indent w3c/webrtc-encoded-transform#177, by @fippo.
-
-
2 pull requests merged.
-
Fix bikeshed-isms w3c/webrtc-encoded-transform#176.
-
Add presentationTimestamp to RTCEncodedVideoFrameMetadata w3c/webrtc-encoded-transform#173.
-
-
1 pull request closed.
-
fix RTCEncodedVideoFrameMeta contributingSources indent w3c/webrtc-encoded-transform#177.
-
-
3 pull requests received 18 new comments.
-
Add presentationTimestamp to RTCEncodedVideoFrameMetadata w3c/webrtc-encoded-transform#173 (16 comments by @aboba, @dontcallmedom-bot, @henbos, @jan-ivar, @tonyherre, @youennf)
-
fix RTCEncodedVideoFrameMeta contributingSources indent w3c/webrtc-encoded-transform#177 (1 comment by @fippo)
-
w3c/webrtc-pc
-
4 issues opened.
-
insertDTMF() can race with stopping or sender.replaceTrack(null) w3c/webrtc-pc#2860, by @jan-ivar.
-
Steps for updating RTCPeerConnection.[[IceConnectionState]] are missing? w3c/webrtc-pc#2858, by @docfaraday.
-
addTransceiver: 1 sendEncodings vs 0 sendEncodings w3c/webrtc-pc#2856, by @henbos.
-
3 issues closed.
-
insertDTMF() can race with stopping or sender.replaceTrack(null) w3c/webrtc-pc#2860.
-
Shouldn't call sender/receiver.getCapabilities() from other algorithms w3c/webrtc-pc#2849.
-
-
5 issues received 19 new comments.
-
addTransceiver: 1 sendEncodings vs 0 sendEncodings w3c/webrtc-pc#2856 (4 comments by @henbos, @Orphis)
-
addIceCandidate may not need to throw an error when no remoteDescription w3c/webrtc-pc#2519 (2 comments by @fippo, @Sean-Der)
-
insertDTMF() can race with stopping or sender.replaceTrack(null) w3c/webrtc-pc#2860 (2 comments by @jan-ivar)
-
Steps for updating RTCPeerConnection.[[IceConnectionState]] are missing? w3c/webrtc-pc#2858 (2 comments by @jan-ivar)
-
10 pull requests opened.
-
Export [[ReceiverTrack]]. w3c/webrtc-pc#2864, by @jan-ivar.
-
Add a proper definition to the "DTMF playout task steps" w3c/webrtc-pc#2863, by @jan-ivar.
-
Update to ReSpec version 34.0.1 w3c/webrtc-pc#2862, by @dontcallmedom.
-
Determine if DTMF can be sent inside queued playout task. w3c/webrtc-pc#2861, by @jan-ivar.
-
Fix connectionState to return [[ConnectionState]]. w3c/webrtc-pc#2859, by @jan-ivar.
-
Export "list of implemented send codecs" w3c/webrtc-pc#2857, by @Orphis.
-
Update to ReSpec version 33.0.1 w3c/webrtc-pc#2855, by @dontcallmedom.
-
Export links to addTransceiver/setParameters steps + unnumber some steps w3c/webrtc-pc#2854, by @jan-ivar.
-
Use the url spec to parse ice server urls (Take 2). w3c/webrtc-pc#2853, by @jan-ivar.
-
Update to ReSpec version 32.8.1 w3c/webrtc-pc#2852, by @dontcallmedom.
-
-
10 pull requests merged.
-
Add a proper definition to the "DTMF playout task steps" w3c/webrtc-pc#2863.
-
Determine if DTMF can be sent inside queued playout task. w3c/webrtc-pc#2861.
-
Update to ReSpec version 34.0.1 w3c/webrtc-pc#2862.
-
Export [[ReceiverTrack]]. w3c/webrtc-pc#2864.
-
Export "list of implemented send codecs" w3c/webrtc-pc#2857.
-
Update to ReSpec version 33.0.1 w3c/webrtc-pc#2855.
-
Export links to addTransceiver/setParameters steps + unnumber some steps w3c/webrtc-pc#2854.
-
Add sender/receiver.getCapabilities() algorithms (and use them in offer/answer) w3c/webrtc-pc#2850.
-
setParameters(), replaceTrack(), & insertDTMF() reject after stop(). w3c/webrtc-pc#2829.
-
Update to ReSpec version 32.8.1 w3c/webrtc-pc#2852.
-
-
1 pull request closed.
-
Use the url spec to parse ice server urls. w3c/webrtc-pc#2694.
-
-
6 pull requests received 17 new comments.
-
Add sender/receiver.getCapabilities() algorithms (and use them in offer/answer) w3c/webrtc-pc#2850 (6 comments by @jan-ivar)
-
Use the url spec to parse ice server urls (Take 2). w3c/webrtc-pc#2853 (5 comments by @alvestrand, @annevk, @jan-ivar)
-
setParameters(), replaceTrack(), & insertDTMF() reject after stop(). w3c/webrtc-pc#2829 (3 comments by @jan-ivar)
-
Export links to addTransceiver/setParameters steps + unnumber some steps w3c/webrtc-pc#2854 (1 comment by @jan-ivar)
-
w3c/mediacapture-extensions
-
3 issues opened.
-
[Track Stats API] track.getFrameStats() allocates memory, adding to the GC pile w3c/mediacapture-extensions#98, by @jan-ivar.
-
Migrate capture metrics from RTCAudioSourceStats to MediaStreamTrack method w3c/mediacapture-extensions#96, by @henbos.
-
Converge face detection metadata between shape detection API and VideoFrame w3c/mediacapture-extensions#95, by @youennf.
-
-
4 issues received 18 new comments.
-
Solve user agent camera/microphone double-mute w3c/mediacapture-extensions#39 (8 comments by @dontcallmedom-bot, @jan-ivar, @youennf)
-
[Track Stats API] track.getFrameStats() allocates memory, adding to the GC pile w3c/mediacapture-extensions#98 (7 comments by @henbos, @jan-ivar, @karlt, @padenot)
-
MediaStreamTrack audio delay/glitch capture stats w3c/mediacapture-extensions#93 (2 comments by @dontcallmedom-bot, @henbos)
-
Face Detection: How metadata should be tied to requestVideoFrameCallback w3c/mediacapture-extensions#71 (1 comment by @ttoivone)
-
-
1 pull request opened.
-
Add audio capture stats, rename method to getStats. w3c/mediacapture-extensions#97, by @henbos.
-
-
4 pull requests received 28 new comments.
-
Add face detection constraints and VideoFrameMetadata members w3c/mediacapture-extensions#78 (11 comments by @jan-ivar, @ttoivone, @youennf)
-
Add audio capture stats, rename method to getStats. w3c/mediacapture-extensions#97 (10 comments by @henbos, @jan-ivar)
-
Add changes to configurationchange MediaStreamTrack event w3c/mediacapture-extensions#83 (1 comment by @abhijeetk)
-
w3c/webrtc-extensions
-
5 issues opened.
-
RTCRtpEncodingParameters: scaleResolutionDownTo w3c/webrtc-extensions#159, by @henbos.
-
When are keyframes generated? w3c/webrtc-extensions#158, by @aboba.
-
Does playoutDelay of video affect jitter buffer of synced audio and vice versa? w3c/webrtc-extensions#157, by @jan-ivar.
-
Should we clarify playoutDelay value is jitter buffer depth? w3c/webrtc-extensions#156, by @jan-ivar.
-
playoutDelay should use milliseconds. w3c/webrtc-extensions#155, by @jan-ivar.
-
-
8 issues closed.
-
Testability of playoutDelayHint w3c/webrtc-extensions#12.
-
How does a developer decide on a value for `playoutDelay` ? w3c/webrtc-extensions#46.
-
RTCRtpReceiver.playoutDelay...Hint or no Hint? w3c/webrtc-extensions#123.
-
playoutDelay should use milliseconds. w3c/webrtc-extensions#155.
-
Does playoutDelay of video affect jitter buffer of synced audio and vice versa? w3c/webrtc-extensions#157.
-
Should we clarify playoutDelay value is jitter buffer depth? w3c/webrtc-extensions#156.
-
Negotiationless codec selection and per-encoding layer codec configuration w3c/webrtc-extensions#126.
-
Mixed-codec simulcast proposal w3c/webrtc-extensions#43.
-
-
10 issues received 49 new comments.
-
Testability of playoutDelayHint w3c/webrtc-extensions#12 (19 comments by @dontcallmedom-bot, @fippo, @henbos, @jan-ivar)
-
Should setOfferedHeaderExtensions be allowed to restart stopped extensions? w3c/webrtc-extensions#134 (6 comments by @aboba, @docfaraday, @ekr, @fippo, @henbos)
-
RTCRtpEncodingParameters: scaleResolutionDownTo w3c/webrtc-extensions#159 (6 comments by @fippo, @henbos, @Orphis)
-
Exposing decode errors / SW fallback as an event w3c/webrtc-extensions#146 (5 comments by @aboba, @dontcallmedom-bot, @henbos, @xingri)
-
RTCRtpReceiver.playoutDelay...Hint or no Hint? w3c/webrtc-extensions#123 (4 comments by @dontcallmedom-bot, @henbos, @jan-ivar)
-
Should we clarify playoutDelay value is jitter buffer depth? w3c/webrtc-extensions#156 (3 comments by @dontcallmedom-bot, @jan-ivar)
-
playoutDelay should use milliseconds. w3c/webrtc-extensions#155 (2 comments by @dontcallmedom-bot, @jan-ivar)
-
Does playoutDelay of video affect jitter buffer of synced audio and vice versa? w3c/webrtc-extensions#157 (2 comments by @bdrtc, @dontcallmedom-bot)
-
Do we need a control API for RTCP feedback mechanisms? w3c/webrtc-extensions#143 (1 comment by @aboba)
-
How does a developer decide on a value for `playoutDelay` ? w3c/webrtc-extensions#46 (1 comment by @dontcallmedom-bot)
-
-
5 pull requests opened.
-
Remove JSEP Modifications w3c/webrtc-extensions#164, by @aboba.
-
Removing JSEP modifications w3c/webrtc-extensions#163, by @aboba.
-
Revert "Change playoutDelay to jitterBufferTarget." w3c/webrtc-extensions#162, by @aboba.
-
Remove superfluous closing tag w3c/webrtc-extensions#161, by @chrisguttandin.
-
Change playoutDelay to jitterBufferTarget. w3c/webrtc-extensions#160, by @jan-ivar.
-
-
2 pull requests merged.
-
Change playoutDelay to jitterBufferTarget. w3c/webrtc-extensions#160.
-
Add RTCRtpEncodingParameters.codec to change the active codec w3c/webrtc-extensions#147.
-
-
3 pull requests closed.
-
Removing JSEP modifications w3c/webrtc-extensions#163.
-
Revert "Change playoutDelay to jitterBufferTarget." w3c/webrtc-extensions#162.
-
Remove superfluous closing tag w3c/webrtc-extensions#161.
-
-
5 pull requests received 37 new comments.
-
Change playoutDelay to jitterBufferTarget. w3c/webrtc-extensions#160 (22 comments by @aboba, @bdrtc, @fippo, @henbos, @jan-ivar, @murillo128)
-
Add RTCRtpEncodingParameters.codec to change the active codec w3c/webrtc-extensions#147 (9 comments by @aboba, @dontcallmedom-bot, @jan-ivar, @Orphis)
-
w3c/mediacapture-main
-
4 issues opened.
-
Mark sampleRate, sampleSize, latency as features at risk w3c/mediacapture-main#958, by @dontcallmedom.
-
Can devicechange fire prior to enumerateDevices? w3c/mediacapture-main#956, by @fippo.
-
aspectRatio range computation is undefined w3c/mediacapture-main#954, by @youennf.
-
ability to pass metadata on add track [Feature Request] w3c/mediacapture-main#952, by @JSmithOner.
-
-
5 issues closed.
-
ability to pass metadata on add track [Feature Request] w3c/mediacapture-main#952.
-
Clarify the type of Constrainable Properties w3c/mediacapture-main#945.
-
Settings are signed while constraints are unsigned w3c/mediacapture-main#944.
-
Avoid the word "legal" to describe input validation w3c/mediacapture-main#946.
-
Video with audio element pause after play during phone call w3c/mediacapture-main#869.
-
-
7 issues received 11 new comments.
-
ability to pass metadata on add track [Feature Request] w3c/mediacapture-main#952 (4 comments by @fippo, @JSmithOner)
-
'label' needs direction and language metadata w3c/mediacapture-main#665 (2 comments by @aphillips, @dontcallmedom)
-
Video with audio element pause after play during phone call w3c/mediacapture-main#869 (1 comment by @jan-ivar)
-
Restore the active/inactive events on MediaStream w3c/mediacapture-main#370 (1 comment by @matiaslopezd)
-
-
5 pull requests opened.
-
Improve markup of definitions and algorithms w3c/mediacapture-main#957, by @dontcallmedom.
-
Update to latest ReSpec version 34.0.1 w3c/mediacapture-main#955, by @dontcallmedom.
-
Update to latest ReSpec version 33.0.1 w3c/mediacapture-main#953, by @dontcallmedom.
-
Update Constrainable Properties prose (follow-up to #948) w3c/mediacapture-main#951, by @jan-ivar.
-
Update to latest ReSpec version 32.8.1 w3c/mediacapture-main#950, by @dontcallmedom.
-
-
8 pull requests merged.
-
Improve markup of definitions and algorithms w3c/mediacapture-main#957.
-
Update to latest ReSpec version 34.0.1 w3c/mediacapture-main#955.
-
Update Constrainable Properties prose (follow-up to #948) w3c/mediacapture-main#951.
-
Update to latest ReSpec version 33.0.1 w3c/mediacapture-main#953.
-
Replace Values with Type column in Constrainable Properties tables. w3c/mediacapture-main#948.
-
s/long/unsigned long/ in MediaTrackSettings. w3c/mediacapture-main#947.
-
s/legal/valid/ w3c/mediacapture-main#949.
-
Update to latest ReSpec version 32.8.1 w3c/mediacapture-main#950.
-
-
1 pull request received 2 new comments.
-
Update Constrainable Properties prose (follow-up to #948) w3c/mediacapture-main#951 (2 comments by @jan-ivar, @youennf)
-
w3c/mediacapture-record
-
2 issues opened.
-
What to do both videoKeyFrameIntervalDuration and videoKeyFrameIntervalCount are specified? w3c/mediacapture-record#219, by @henbos.
-
The changes in the canvas are not being recognized correctly. w3c/mediacapture-record#218, by @yoshi-pi.
-
-
1 issue closed.
-
Broken references in MediaStream Recording w3c/mediacapture-record#215.
-
-
1 issue received 2 new comments.
-
What to do both videoKeyFrameIntervalDuration and videoKeyFrameIntervalCount are specified? w3c/mediacapture-record#219 (2 comments by @foolip)
-
-
1 pull request opened.
-
Use autolinking where possible w3c/mediacapture-record#217, by @dontcallmedom.
-
-
2 pull requests merged.
-
Add keyframe interval support. w3c/mediacapture-record#216.
-
Use autolinking where possible w3c/mediacapture-record#217.
-
-
1 pull request received 18 new comments.
-
Add keyframe interval support. w3c/mediacapture-record#216 (18 comments by @handellm, @jan-ivar, @Pehrsons, @youennf)
-
w3c/webrtc-stats
-
2 issues opened.
-
Change playoutdelay to jitterbuffertarget w3c/webrtc-stats#753, by @bdrtc.
-
Should we flatten the hierarchy? w3c/webrtc-stats#752, by @henbos.
-
-
1 issue closed.
-
Change playoutdelay to jitterbuffertarget w3c/webrtc-stats#753.
-
-
2 issues reopened.
-
RTX and FEC stats are incomplete. w3c/webrtc-stats#751, by @henbos.
-
scalabilityMode: Same as in getParameters() or not? w3c/webrtc-stats#731, by @henbos.
-
-
8 issues received 20 new comments.
-
RTX and FEC stats are incomplete. w3c/webrtc-stats#751 (7 comments by @dontcallmedom-bot, @fippo, @henbos, @vr000m)
-
RTCOutboundRtpStreamStats.headerBytesSent/totalPacketSendDelay and RTX seems underspecified w3c/webrtc-stats#747 (3 comments by @fippo, @vr000m)
-
-
1 pull request opened.
-
Change playout delay to jitter buffer target w3c/webrtc-stats#754, by @bdrtc.
-
-
2 pull requests merged.
-
specifiy inbound-rtp RTX statistics w3c/webrtc-stats#735.
-
Change playout delay to jitter buffer target w3c/webrtc-stats#754.
-
-
2 pull requests received 3 new comments.
w3c/webrtc-nv-use-cases
-
1 issue closed.
-
Dropping "NV" from the document name w3c/webrtc-nv-use-cases#107.
-
-
1 issue received 3 new comments.
-
Section 3.2: Feedback related to WebRTC-NV Low Latency Streaming Use Case w3c/webrtc-nv-use-cases#103 (3 comments by @aboba, @steely-glint, @tonyherre)
-
-
1 pull request merged.
-
Rename "WebRTC-NV Use Cases" to "WebRTC Extended Use Cases" w3c/webrtc-nv-use-cases#108.
-
w3c/webrtc-svc
-
1 issue opened.
-
Layer Refresh w3c/webrtc-svc#88, by @aboba.
-
-
1 issue received 1 new comment.
-
2 pull requests opened.
-
Example: mixed codec simulcast + SVC w3c/webrtc-svc#90, by @aboba.
-
Refer to the addTransceiver and setParameters validation steps w3c/webrtc-svc#89, by @Orphis.
-
-
2 pull requests merged.
-
Example: mixed codec simulcast + SVC w3c/webrtc-svc#90.
-
Refer to the addTransceiver and setParameters validation steps w3c/webrtc-svc#89.
-
-
1 pull request received 14 new comments.
-
Refer to the addTransceiver and setParameters validation steps w3c/webrtc-svc#89 (14 comments by @aboba, @henbos, @jan-ivar, @Orphis)
-
w3c/mediacapture-screen-share
-
1 issue received 3 new comments.
-
no-focus-change is misleading w3c/mediacapture-screen-share#263 (3 comments by @dontcallmedom-bot, @eladalon1983, @youennf)
-
-
1 pull request opened.
-
List simple types in Constrainable Properties Type column. w3c/mediacapture-screen-share#265, by @jan-ivar.
-
-
1 pull request merged.
-
List simple types in Constrainable Properties Type column. w3c/mediacapture-screen-share#265.
-
-
1 pull request received 1 new comment.
-
Update how FocusChangeDisabled is set to true in case of change of focus w3c/mediacapture-screen-share#264 (1 comment by @jan-ivar)
-
TR publications
-
11 documents published.
-
WebRTC: Real-Time Communication in Browsers published twice as a Recommendation. History of WebRTC: Real-Time Communication in Browsers
-
Identifiers for WebRTC's Statistics API published 5 times as a Candidate Recommendation Draft. History of Identifiers for WebRTC's Statistics API
-
Media Capture and Streams published as a Candidate Recommendation Draft. History of Media Capture and Streams
-
Scalable Video Coding (SVC) Extension for WebRTC published as a Working Draft. History of Scalable Video Coding (SVC) Extension for WebRTC
-
MediaStream Image Capture published as a Working Draft. History of MediaStream Image Capture
-
Region Capture published as a Working Draft. History of Region Capture
-
Past meetings
-
1 meeting.
GitHub
w3c/mediacapture-screen-share
-
4 issues opened.
-
no-focus-change is misleading w3c/mediacapture-screen-share#263, by @youennf.
-
Update algorithms around setFocusBehavior to take into account OS level surface pickers w3c/mediacapture-screen-share#262, by @youennf.
-
Allow apps to avoid riskier display-surface types w3c/mediacapture-screen-share#261, by @eladalon1983.
-
getSupportedOptions() w3c/mediacapture-screen-share#260, by @eladalon1983.
-
-
3 issues received 30 new comments.
-
getSupportedOptions() w3c/mediacapture-screen-share#260 (20 comments by @Coread, @eladalon1983, @jan-ivar, @youennf)
-
no-focus-change is misleading w3c/mediacapture-screen-share#263 (8 comments by @eladalon1983, @youennf)
-
Update algorithms around setFocusBehavior to take into account OS level surface pickers w3c/mediacapture-screen-share#262 (2 comments by @eladalon1983, @youennf)
-
-
1 pull request opened.
-
Update how FocusChangeDisabled is set to true in case of change of focus w3c/mediacapture-screen-share#264, by @youennf.
-
-
1 pull request received 5 new comments.
-
Update how FocusChangeDisabled is set to true in case of change of focus w3c/mediacapture-screen-share#264 (5 comments by @eladalon1983, @youennf)
-
w3c/mediacapture-extensions
-
4 issues opened.
-
Face framing: Discuss privacy implications w3c/mediacapture-extensions#94, by @henbos.
-
MediaStreamTrack audio delay/glitch capture stats w3c/mediacapture-extensions#93, by @henbos.
-
Consider need for automatic single-shot face framing w3c/mediacapture-extensions#91, by @eehakkin.
-
polling of getSettings() on a muted track reveals OS blur changes, correlating user across origins w3c/mediacapture-extensions#90, by @jan-ivar.
-
-
1 issue closed.
-
Clarify which event loop task will be used for track in configuration change . w3c/mediacapture-extensions#86.
-
-
4 issues received 9 new comments.
-
MediaStreamTrack audio delay/glitch capture stats w3c/mediacapture-extensions#93 (5 comments by @henbos, @jan-ivar)
-
Detecting user-actionable camera issues (e.g., camera shutters) w3c/mediacapture-extensions#140 (2 comments by @eladalon1983, @guidou)
-
MediaStreamTrack resizeMode constraint is too vague to request specific strategy w3c/mediacapture-extensions#7 (1 comment by @anthmFS)
-
-
2 pull requests opened.
-
Update README.md w3c/mediacapture-extensions#92, by @eladalon1983.
-
Update configuration change section w3c/mediacapture-extensions#89, by @beaufortfrancois.
-
-
4 pull requests merged.
-
Face framing w3c/mediacapture-extensions#55.
-
Update README.md w3c/mediacapture-extensions#92.
-
Update configuration change section w3c/mediacapture-extensions#89.
-
Queue a task to fire configurationchange w3c/mediacapture-extensions#88.
-
-
1 pull request closed.
-
Restrict onconfigurationchange to background blur w3c/mediacapture-extensions#80.
-
-
7 pull requests received 73 new comments.
-
Add face detection constraints and VideoFrameMetadata members w3c/mediacapture-extensions#78 (37 comments by @ttoivone, @youennf)
-
Eye gaze correction w3c/mediacapture-extensions#56 (12 comments by @eehakkin, @henbos, @jan-ivar, @youennf)
-
Update configuration change section w3c/mediacapture-extensions#89 (11 comments by @beaufortfrancois, @eladalon1983, @jan-ivar)
-
Add changes to configurationchange MediaStreamTrack event w3c/mediacapture-extensions#83 (4 comments by @annevk, @beaufortfrancois, @jan-ivar, @youennf)
-
Restrict onconfigurationchange to background blur w3c/mediacapture-extensions#80 (2 comments by @beaufortfrancois, @youennf)
-
Queue a task to fire configurationchange w3c/mediacapture-extensions#88 (1 comment by @beaufortfrancois)
-
w3c/webrtc-extensions
-
3 issues opened.
-
Header extension API lets the remote end control the remote preferences w3c/webrtc-extensions#153, by @fippo.
-
Exposing decode errors / SW fallback as an event w3c/webrtc-extensions#146, by @henbos.
-
Why RTCRtpHeaderExtensionCapability URI field is not required? w3c/webrtc-extensions#144, by @youennf.
-
-
8 issues closed.
-
Header extension API lets the remote end control the remote preferences w3c/webrtc-extensions#153.
-
Why RTCRtpHeaderExtensionCapability URI field is not required? w3c/webrtc-extensions#144.
-
headerExtensionsToOffer fails to freeze array w3c/webrtc-extensions#135.
-
headerExtensionsToOffer entries are mutable which is surprising w3c/webrtc-extensions#136.
-
FrozenArray on headerExtensionsToOffer a mistake, wrong semantics w3c/webrtc-extensions#137.
-
Suggestion: rename [[HeaderExtensionsToOffer]] to [[HeaderExtensionsSupported]] w3c/webrtc-extensions#132.
-
Potential web compat issue with setOfferedRtpHeaderExtensions w3c/webrtc-extensions#130.
-
Header extension: direction woes and renames w3c/webrtc-extensions#141.
-
-
9 issues received 26 new comments.
-
Should setOfferedHeaderExtensions be allowed to restart stopped extensions? w3c/webrtc-extensions#134 (10 comments by @fippo, @henbos)
-
Exposing decode errors / SW fallback as an event w3c/webrtc-extensions#146 (8 comments by @aboba, @henbos, @tidoust, @youennf)
-
Why RTCRtpHeaderExtensionCapability URI field is not required? w3c/webrtc-extensions#144 (2 comments by @henbos)
-
Header extension API lets the remote end control the remote preferences w3c/webrtc-extensions#153 (1 comment by @henbos)
-
headerExtensionsToOffer entries are mutable which is surprising w3c/webrtc-extensions#136 (1 comment by @henbos)
-
FrozenArray on headerExtensionsToOffer a mistake, wrong semantics w3c/webrtc-extensions#137 (1 comment by @henbos)
-
Suggestion: rename [[HeaderExtensionsToOffer]] to [[HeaderExtensionsSupported]] w3c/webrtc-extensions#132 (1 comment by @henbos)
-
Potential web compat issue with setOfferedRtpHeaderExtensions w3c/webrtc-extensions#130 (1 comment by @henbos)
-
-
8 pull requests opened.
-
clean up audio rtp parameters extensions w3c/webrtc-extensions#154, by @fippo.
-
header extension control: Do not let remote control the local preferences w3c/webrtc-extensions#152, by @fippo.
-
Update data on [CRYPTEX] ref w3c/webrtc-extensions#151, by @dontcallmedom.
-
reorganise document into one-feature-per-section w3c/webrtc-extensions#150, by @fippo.
-
rename ext-respec-config.js to webrtc-extensions and update git branch w3c/webrtc-extensions#149, by @fippo.
-
Delete "Removed features" section w3c/webrtc-extensions#148, by @Orphis.
-
Add RTCRtpEncodingParameters.codec to change the active codec w3c/webrtc-extensions#147, by @Orphis.
-
Make RTCRtpHeaderExtensionCapability attributes required w3c/webrtc-extensions#145, by @henbos.
-
-
8 pull requests merged.
-
header extension control: Do not let remote control the local preferences w3c/webrtc-extensions#152.
-
clean up audio rtp parameters extensions w3c/webrtc-extensions#154.
-
Update data on [CRYPTEX] ref w3c/webrtc-extensions#151.
-
rename ext-respec-config.js to webrtc-extensions and update git branch w3c/webrtc-extensions#149.
-
reorganise document into one-feature-per-section w3c/webrtc-extensions#150.
-
Delete "Removed features" section w3c/webrtc-extensions#148.
-
Make RTCRtpHeaderExtensionCapability attributes required w3c/webrtc-extensions#145.
-
Update header extensions API to get-modify-set. w3c/webrtc-extensions#142.
-
-
1 pull request closed.
-
Per-encoding codec selection w3c/webrtc-extensions#139.
-
-
6 pull requests received 50 new comments.
-
Add RTCRtpEncodingParameters.codec to change the active codec w3c/webrtc-extensions#147 (36 comments by @aboba, @dontcallmedom, @dontcallmedom-bot, @fippo, @henbos, @jan-ivar, @Orphis, @youennf)
-
Delete "Removed features" section w3c/webrtc-extensions#148 (4 comments by @aboba, @dontcallmedom-bot, @fippo, @Orphis)
-
Make RTCRtpHeaderExtensionCapability attributes required w3c/webrtc-extensions#145 (4 comments by @henbos)
-
Update header extensions API to get-modify-set. w3c/webrtc-extensions#142 (4 comments by @henbos, @youennf)
-
rename ext-respec-config.js to webrtc-extensions and update git branch w3c/webrtc-extensions#149 (1 comment by @fippo)
-
w3c/webrtc-stats
-
9 issues opened.
-
RTX and FEC stats are incomplete. w3c/webrtc-stats#751, by @fippo.
-
Conformance criteria incompatible with standards-track w3c/webrtc-stats#749, by @jan-ivar.
-
RTCOutboundRtpStreamStats.headerBytesSent/totalPacketSendDelay and RTX seems underspecified w3c/webrtc-stats#747, by @docfaraday.
-
What is the relationship between WebRTC stats and the Working Group? w3c/webrtc-stats#746, by @henbos.
-
Assorted comments on `RTCAudioPlayoutStats` w3c/webrtc-stats#742, by @padenot.
-
Feedback on audio capture stats w3c/webrtc-stats#741, by @padenot.
-
availableOutgoingBitrate is also available when send-side BWE is not used w3c/webrtc-stats#740, by @fippo.
-
Confusing use of the terms defined and undefined w3c/webrtc-stats#737, by @jan-ivar.
-
Clarify that metrics are omitted when their value is not yet determined or unknown w3c/webrtc-stats#736, by @henbos.
-
-
4 issues closed.
-
Add RTCInboundRtpStreamStats:decoderFallback w3c/webrtc-stats#724.
-
Clarify that metrics are omitted when their value is not yet determined or unknown w3c/webrtc-stats#736.
-
totalInterFrameDelay, and totalSquaredInterFrameDelay are video only w3c/webrtc-stats#656.
-
Confusing use of the terms defined and undefined w3c/webrtc-stats#737.
-
-
11 issues received 69 new comments.
-
The HW exposure check does not solve Cloud Gaming use cases w3c/webrtc-stats#730 (17 comments by @aboba, @dontcallmedom-bot, @henbos, @pes10k, @xingri)
-
Assorted comments on `RTCAudioPlayoutStats` w3c/webrtc-stats#742 (15 comments by @alvestrand, @dontcallmedom-bot, @henbos, @jan-ivar, @padenot)
-
What is the relationship between WebRTC stats and the Working Group? w3c/webrtc-stats#746 (10 comments by @dontcallmedom, @henbos, @jan-ivar, @vr000m, @youennf)
-
Clarify that metrics are omitted when their value is not yet determined or unknown w3c/webrtc-stats#736 (7 comments by @fippo, @henbos, @jan-ivar)
-
scalabilityMode: Same as in getParameters() or not? w3c/webrtc-stats#731 (4 comments by @henbos, @Orphis)
-
RTCOutboundRtpStreamStats.headerBytesSent/totalPacketSendDelay and RTX seems underspecified w3c/webrtc-stats#747 (3 comments by @docfaraday, @henbos, @vr000m)
-
availableOutgoingBitrate is also available when send-side BWE is not used w3c/webrtc-stats#740 (1 comment by @bbaldino)
-
-
7 pull requests opened.
-
Document recently added audio metrics as features at risk w3c/webrtc-stats#750, by @henbos.
-
fix codec mimeType casing w3c/webrtc-stats#748, by @fippo.
-
Clarify that metrics are omitted when their value is not yet determined w3c/webrtc-stats#745, by @fippo.
-
Make RTCRtpSentRtpStreamStats.packetsSent unsigned long long w3c/webrtc-stats#744, by @fippo.
-
Clarify when the candidate pair bandwidth estimation(s) exists w3c/webrtc-stats#743, by @fippo.
-
Clarify "exists" and "only defined for" w3c/webrtc-stats#739, by @fippo.
-
Fix wrong html tag for mediaSourceId description w3c/webrtc-stats#738, by @fippo.
-
-
7 pull requests merged.
-
Document recently added audio metrics as features at risk w3c/webrtc-stats#750.
-
Clarify that metrics are omitted when their value is not yet determined w3c/webrtc-stats#745.
-
fix codec mimeType casing w3c/webrtc-stats#748.
-
Make RTCRtpSentRtpStreamStats.packetsSent unsigned long long w3c/webrtc-stats#744.
-
mark totalInterFrameDelay and totalSquaredInterFrameDelay as video-only w3c/webrtc-stats#733.
-
Clarify "exists" and "only defined for" w3c/webrtc-stats#739.
-
Fix wrong html tag for mediaSourceId description w3c/webrtc-stats#738.
-
-
1 pull request closed.
-
Add RTCInboundRtpStreamStats:decoderFallback w3c/webrtc-stats#725.
-
-
9 pull requests received 57 new comments.
-
Clarify "exists" and "only defined for" w3c/webrtc-stats#739 (15 comments by @fippo, @fuzzy-coats, @henbos, @vr000m)
-
Add RTCInboundRtpStreamStats:decoderFallback w3c/webrtc-stats#725 (13 comments by @dontcallmedom-bot, @henbos, @xingri)
-
Expose powerEfficientEncoder/Decoder if MediaCapabilities allows it w3c/webrtc-stats#732 (7 comments by @aboba, @henbos, @pes10k, @xingri)
-
Clarify when the candidate pair bandwidth estimation(s) exists w3c/webrtc-stats#743 (6 comments by @fippo, @vr000m)
-
Clarify that metrics are omitted when their value is not yet determined w3c/webrtc-stats#745 (5 comments by @fippo, @vr000m)
-
mark totalInterFrameDelay and totalSquaredInterFrameDelay as video-only w3c/webrtc-stats#733 (4 comments by @henbos, @vr000m)
-
Fix wrong html tag for mediaSourceId description w3c/webrtc-stats#738 (3 comments by @dontcallmedom, @fippo, @henbos)
-
Document recently added audio metrics as features at risk w3c/webrtc-stats#750 (1 comment by @henbos)
-
w3c/webrtc-pc
-
8 issues opened.
-
Shouldn't call sender/receiver.getCapabilities() from other algorithms w3c/webrtc-pc#2849, by @jan-ivar.
-
RTCRtpEncodingParameters.active flag and the ~ in the SDP w3c/webrtc-pc#2848, by @henbos.
-
What is setCodecPreferences's contract? w3c/webrtc-pc#2845, by @jan-ivar.
-
Remove "MAY generate statistics that are not documented." w3c/webrtc-pc#2844, by @jan-ivar.
-
Make RTCRtpHeaderExtensionCapability.uri required w3c/webrtc-pc#2840, by @henbos.
-
Transceivers stopped prior to being negotiated are never removed from the set of transcievers w3c/webrtc-pc#2838, by @henbos.
-
Section 4.4.2: createOffer() and setLocalDescription() resource handling w3c/webrtc-pc#2835, by @aboba.
-
-
4 issues closed.
-
What is setCodecPreferences's contract? w3c/webrtc-pc#2845.
-
RTCRtpEncodingParameters.active flag and the ~ in the SDP w3c/webrtc-pc#2848.
-
Hard to tell if there are state gaps in connectionState algorithm w3c/webrtc-pc#2827.
-
Make RTCRtpHeaderExtensionCapability.uri required w3c/webrtc-pc#2840.
-
-
10 issues received 31 new comments.
-
If you close your data channel before first offer, does the "m=application" line still show up? w3c/webrtc-pc#2839 (7 comments by @alvestrand, @fippo, @henbos, @lgrahl)
-
Transceivers stopped prior to being negotiated are never removed from the set of transcievers w3c/webrtc-pc#2838 (6 comments by @henbos, @jan-ivar)
-
What is setCodecPreferences's contract? w3c/webrtc-pc#2845 (5 comments by @jan-ivar, @Orphis, @youennf)
-
RTCRtpEncodingParameters.active flag and the ~ in the SDP w3c/webrtc-pc#2848 (3 comments by @fippo, @henbos)
-
Hard to tell if there are state gaps in connectionState algorithm w3c/webrtc-pc#2827 (2 comments by @dontcallmedom-bot, @pthatcher)
-
Section 4.4.2: createOffer() and setLocalDescription() resource handling w3c/webrtc-pc#2835 (2 comments by @dontcallmedom-bot, @youennf)
-
Remove "MAY generate statistics that are not documented." w3c/webrtc-pc#2844 (2 comments by @henbos)
-
Why is RTCIceCandidatePairStats.totalRoundTripTime mandatory to implement, but not responsesReceived? w3c/webrtc-pc#2819 (2 comments by @fippo, @jan-ivar)
-
Maybe setParameters/insertDtmf/replaceTrack should reject on [[Stopping]] as well as [[Stopped]]? w3c/webrtc-pc#2820 (1 comment by @dontcallmedom-bot)
-
Is it OK to call addTransceiver() with a track already added by addTrack()? w3c/webrtc-pc#583 (1 comment by @fukemy)
-
-
12 pull requests opened.
-
Export more definitions to use in webrtc-extensions w3c/webrtc-pc#2851, by @Orphis.
-
Add sender/receiver.getCapabilities() algorithms (and use them in offer/answer) w3c/webrtc-pc#2850, by @jan-ivar.
-
Add a codec match algorithm for setCodecPreferences w3c/webrtc-pc#2847, by @Orphis.
-
Update to ReSpec version 32.8.0 w3c/webrtc-pc#2846, by @dontcallmedom.
-
Mark PreferredCodec internal slot as exported w3c/webrtc-pc#2843, by @dontcallmedom.
-
Make RTCRtpHeaderExtensionCapability.uri required w3c/webrtc-pc#2841, by @henbos.
-
Fix scaleResolutionDownBy explanatory prose to match normative algorithm w3c/webrtc-pc#2836, by @jan-ivar.
-
Annotate amendment boxes w3c/webrtc-pc#2833, by @dontcallmedom.
-
add RTCIceCandidatePair.responsesReceived to MTI stats w3c/webrtc-pc#2832, by @fippo.
-
Re-organize respec plugins w3c/webrtc-pc#2831, by @dontcallmedom.
-
-
13 pull requests merged.
-
Add a codec match algorithm for setCodecPreferences w3c/webrtc-pc#2847.
-
Export more definitions to use in webrtc-extensions w3c/webrtc-pc#2851.
-
Update to ReSpec version 32.8.0 w3c/webrtc-pc#2846.
-
add RTCIceCandidatePair.responsesReceived to MTI stats w3c/webrtc-pc#2832.
-
Fix typo w3c/webrtc-pc#2842.
-
Mark PreferredCodec internal slot as exported w3c/webrtc-pc#2843.
-
Make RTCRtpHeaderExtensionCapability.uri required w3c/webrtc-pc#2841.
-
Fix scaleResolutionDownBy explanatory prose to match normative algorithm w3c/webrtc-pc#2836.
-
Add internal slots for signaling state, connection state, ice gatheri… w3c/webrtc-pc#2826.
-
Annotate amendment boxes w3c/webrtc-pc#2833.
-
Re-organize respec plugins w3c/webrtc-pc#2831.
-
-
1 pull request closed.
-
Update to ReSpec version 32.7.1 w3c/webrtc-pc#2824.
-
-
10 pull requests received 49 new comments.
-
Add a codec match algorithm for setCodecPreferences w3c/webrtc-pc#2847 (19 comments by @jan-ivar, @Orphis)
-
Add sender/receiver.getCapabilities() algorithms (and use them in offer/answer) w3c/webrtc-pc#2850 (9 comments by @henbos, @jan-ivar, @Orphis)
-
Make RTCRtpHeaderExtensionCapability.uri required w3c/webrtc-pc#2841 (6 comments by @dontcallmedom, @henbos)
-
setParameters(), replaceTrack(), & insertDTMF() reject after stop(). w3c/webrtc-pc#2829 (4 comments by @dontcallmedom-bot, @jan-ivar)
-
Express RTCPeerConnectionState values using [[IceConnectionState]], and reduce complexity w3c/webrtc-pc#2828 (3 comments by @dontcallmedom, @dontcallmedom-bot)
-
add RTCIceCandidatePair.responsesReceived to MTI stats w3c/webrtc-pc#2832 (2 comments by @dontcallmedom, @jan-ivar)
-
Create RTCRtpCodec dictionary and reuse in RTCRtpCodecParameters and RTCRtpCodecCapability definitions w3c/webrtc-pc#2834 (2 comments by @alvestrand, @jan-ivar)
-
Add internal slots for signaling state, connection state, ice gatheri… w3c/webrtc-pc#2826 (2 comments by @dontcallmedom, @jan-ivar)
-
w3c/mediacapture-main
-
7 issues opened.
-
Avoid the word "legal" to describe input validation w3c/mediacapture-main#946, by @jan-ivar.
-
Clarify the type of Constrainable Properties w3c/mediacapture-main#945, by @jan-ivar.
-
Settings are signed while constraints are unsigned w3c/mediacapture-main#944, by @jan-ivar.
-
Spec-inherent capabilities of one differ from other capabilities of one, an unnecessary variant w3c/mediacapture-main#941, by @jan-ivar.
-
What is the granularity of a source? w3c/mediacapture-main#940, by @youennf.
-
Global object relevant to what? w3c/mediacapture-main#938, by @jan-ivar.
-
Should we introduce a media stream task source? w3c/mediacapture-main#935, by @youennf.
-
-
1 issue closed.
-
Global object relevant to what? w3c/mediacapture-main#938.
-
-
4 issues received 21 new comments.
-
Fitness distance steps 4 and 5 are inconsistent with the rest of the spec w3c/mediacapture-main#933 (12 comments by @alvestrand, @eehakkin, @guidou, @jan-ivar)
-
Settings are signed while constraints are unsigned w3c/mediacapture-main#944 (2 comments by @guidou, @jan-ivar)
-
-
8 pull requests opened.
-
s/legal/valid/ w3c/mediacapture-main#949, by @jan-ivar.
-
Replace Values with Type column in Constrainable Properties tables. w3c/mediacapture-main#948, by @jan-ivar.
-
s/long/unsigned long/ in MediaTrackSettings. w3c/mediacapture-main#947, by @jan-ivar.
-
Update to latest ReSpec version 32.8.0 w3c/mediacapture-main#943, by @dontcallmedom.
-
Add note about deviceId and groupId inconsistency with other capabilities. w3c/mediacapture-main#942, by @jan-ivar.
-
Move "global" internal slots to MediaDevices, and fix "relevant object" links w3c/mediacapture-main#939, by @jan-ivar.
-
Remove focus requirement on enumerateDevices, for real this time #912. w3c/mediacapture-main#937, by @jan-ivar.
-
Remove focus from mute/unmute SHOULD prose to match #912 best practice. w3c/mediacapture-main#936, by @jan-ivar.
-
-
2 pull requests merged.
-
Update to latest ReSpec version 32.8.0 w3c/mediacapture-main#943.
-
Move "global" internal slots to MediaDevices, and fix "relevant object" links w3c/mediacapture-main#939.
-
-
3 pull requests received 26 new comments.
-
Move "global" internal slots to MediaDevices, and fix "relevant object" links w3c/mediacapture-main#939 (24 comments by @jan-ivar, @youennf)
-
Add note about deviceId and groupId inconsistency with other capabilities. w3c/mediacapture-main#942 (1 comment by @eladalon1983)
-
w3c/webrtc-svc
-
2 issues received 4 new comments.
-
SVC getCapabilities() is redundant with Media Capabilities query w3c/webrtc-svc#49 (2 comments by @aboba, @opusonline)
w3c/webrtc-nv-use-cases
-
1 issue closed.
-
Advanced Codec Capabilities API w3c/webrtc-nv-use-cases#53.
-
-
1 issue received 1 new comment.
w3c/webrtc-charter
-
2 issues closed.
-
Move -extensions rules from webrtc-pc to charter repo w3c/webrtc-charter#63.
-
Include call-for-adoption process in the charter? w3c/webrtc-charter#69.
-
-
1 issue received 2 new comments.
-
1 pull request opened.
-
Align coordination with MEIG with reality w3c/webrtc-charter#80, by @dontcallmedom.
-
w3c/webrtc-encoded-transform
-
1 issue opened.
-
SFrameTransform should inherit from EventTarget w3c/webrtc-encoded-transform#175, by @dontcallmedom.
-
-
1 issue received 2 new comments.
-
Tell SDP negotiation to negotiate support for non-standard codecs w3c/webrtc-encoded-transform#172 (2 comments by @alvestrand, @dontcallmedom-bot)
-
-
1 pull request opened.
-
Fix bikeshed-isms w3c/webrtc-encoded-transform#176, by @dontcallmedom.
-
-
3 pull requests received 4 new comments.
-
Add presentationTimestamp to RTCEncodedVideoFrameMetadata w3c/webrtc-encoded-transform#173 (1 comment by @alvestrand)
w3c/media-pipeline-arch
-
1 issue closed.
-
Processing pipeline: Create VideoFrame out of WebGPU result w3c/media-pipeline-arch#7.
-
-
1 issue received 1 new comment.
-
Processing pipeline: Create VideoFrame out of WebGPU result w3c/media-pipeline-arch#7 (1 comment by @tidoust)
-
w3c/mediacapture-handle
-
1 issue received 10 new comments.
-
Expose a MessagePort using Capture Handle w3c/mediacapture-handle#70 (10 comments by @eladalon1983, @youennf)
-
w3c/mediacapture-record
-
1 pull request received 4 new comments.
w3c/mediacapture-image
-
1 pull request opened.
-
Amend and fix implementation status on Windows w3c/mediacapture-image#301, by @eehakkin.
-
-
1 pull request merged.
-
Amend and fix implementation status on Windows w3c/mediacapture-image#301.
-
w3c/mediacapture-region
-
1 issue opened.
-
Behavior after a failed call to cropTo() w3c/mediacapture-region#77, by @eladalon1983.
-
w3c/webrtc-ice
-
1 issue received 1 new comment.
w3c/mediacapture-screen-share-extensions
-
1 issue opened.
-
Exposing mouse events from captured surfaces w3c/mediacapture-screen-share-extensions#2, by @eladalon1983.
-
-
2 issues received 2 new comments.
-
Capability Delegation for getDisplayMedia() w3c/mediacapture-screen-share-extensions#3 (1 comment by @bradisbell)
-
Exposing mouse events from captured surfaces w3c/mediacapture-screen-share-extensions#2 (1 comment by @happylinks)
-
TR publications
-
9 documents published.
-
Identifiers for WebRTC's Statistics API published as a Candidate Recommendation Draft. History of Identifiers for WebRTC's Statistics API
-
Audio Output Devices API published as a Candidate Recommendation Draft. History of Audio Output Devices API
-
Media Capture and Streams published as a Candidate Recommendation Draft. History of Media Capture and Streams
-
MediaStream Image Capture published twice as a Working Draft. History of MediaStream Image Capture
-
Scalable Video Coding (SVC) Extension for WebRTC published 4 times as a Working Draft. History of Scalable Video Coding (SVC) Extension for WebRTC
-
Past meetings
-
1 meeting.
Participants
-
3 participants joined.
-
Shengyuan Feng (Agora.io) joined.
-
Jared Siskin (Meta) joined.
-
Sean Nunley (Meta) joined.
-
-
9 participants left.
-
Seth Hampson (Google LLC) left.
-
Daniel Fishkov (RingCentral) left.
-
Dmitry Porokh (RingCentral) left.
-
Alexey Petrov (RingCentral) left.
-
jiaheng su (Agora.io) left.
-
hexiang cui (Agora.io) left.
-
Xiao Fu (Agora.io) left.
-
yang lee (Agora.io) left.
-
Zeyu Guo (Agora.io) left.
-
-
1 organization left.
-
RingCentral left.
-
GitHub
w3c/mediacapture-main
-
4 issues opened.
-
Don't block getUserMedia on the user typing in URL bar w3c/mediacapture-main#934, by @jan-ivar.
-
Fitness distance steps 4 and 5 are inconsistent with the rest of the spec w3c/mediacapture-main#933, by @guidou.
-
Web compat issue with permissions.query() in non-persistent permission models w3c/mediacapture-main#928, by @jan-ivar.
-
Web compat issue with permissions.query() in per-camera/mic permission models w3c/mediacapture-main#927, by @jan-ivar.
-
-
1 issue closed.
-
Web compat issue with permissions.query() in per-camera/mic permission models w3c/mediacapture-main#927.
-
-
3 issues received 3 new comments.
-
Web compat issue with permissions.query() in per-camera/mic permission models w3c/mediacapture-main#927 (1 comment by @jan-ivar)
-
Unclear how to associate current active device with enumerated devices w3c/mediacapture-main#299 (1 comment by @ryuujo1573)
-
Why does `navigator.mediaDevices.enumerateDevices()` require that `Document` must have active keyboard focus? w3c/mediacapture-main#905 (1 comment by @jan-ivar)
-
-
3 pull requests opened.
-
query without deviceId is for access to any device of a kind. w3c/mediacapture-main#932, by @jan-ivar.
-
Update to latest ReSpec version 32.7.1 w3c/mediacapture-main#931, by @dontcallmedom.
-
Update to latest ReSpec version 32.7.0 w3c/mediacapture-main#929, by @dontcallmedom.
-
-
4 pull requests merged.
-
Update to latest ReSpec version 32.7.1 w3c/mediacapture-main#931.
-
query without deviceId is for access to any device of a kind. w3c/mediacapture-main#932.
-
Update to latest ReSpec version 32.7.0 w3c/mediacapture-main#929.
-
Split device sanitation note into separate paragraph w3c/mediacapture-main#926.
-
-
1 pull request received 5 new comments.
-
query without deviceId is for access to any device of a kind. w3c/mediacapture-main#932 (5 comments by @alvestrand, @jan-ivar)
-
w3c/webrtc-extensions
-
2 issues opened.
-
Do we need a control API for RTCP feedback mechanisms? w3c/webrtc-extensions#143, by @alvestrand.
-
Header extension: direction woes and renames w3c/webrtc-extensions#141, by @henbos.
-
-
1 issue closed.
-
Not clear what should happen if header extensions are inconsistent across bundled transports w3c/webrtc-extensions#140.
-
-
4 issues received 8 new comments.
-
Header extension: direction woes and renames w3c/webrtc-extensions#141 (4 comments by @fippo, @henbos)
-
Not clear what should happen if header extensions are inconsistent across bundled transports w3c/webrtc-extensions#140 (2 comments by @fippo, @henbos)
-
Do we need a control API for RTCP feedback mechanisms? w3c/webrtc-extensions#143 (1 comment by @bdrtc)
-
-
1 pull request opened.
-
Update header extensions API to get-modify-set. w3c/webrtc-extensions#142, by @henbos.
-
-
1 pull request received 7 new comments.
-
Update header extensions API to get-modify-set. w3c/webrtc-extensions#142 (7 comments by @fippo, @henbos)
-
w3c/webrtc-stats
-
2 issues opened.
-
scalabilityMode: Same as in getParameters() or not? w3c/webrtc-stats#731, by @henbos.
-
The HW exposure check does not solve Cloud Gaming use cases w3c/webrtc-stats#730, by @henbos.
-
-
1 issue closed.
-
Interframe delay stat for video receive stream. w3c/webrtc-stats#229.
-
-
4 issues received 24 new comments.
-
scalabilityMode: Same as in getParameters() or not? w3c/webrtc-stats#731 (12 comments by @aboba, @alvestrand, @eshrubs, @henbos, @Orphis)
-
The HW exposure check does not solve Cloud Gaming use cases w3c/webrtc-stats#730 (10 comments by @alvestrand, @drkron, @fippo, @henbos, @pes10k, @vr000m)
-
-
4 pull requests opened.
-
specifiy inbound-rtp RTX statistics w3c/webrtc-stats#735, by @fippo.
-
editorial: fix decoderImplementation idl reference w3c/webrtc-stats#734, by @fippo.
-
mark totalInterFrameDelay and totalSquaredInterFrameDelay as video-only w3c/webrtc-stats#733, by @fippo.
-
Expose powerEfficientEncoder/Decoder if MediaCapabilities allows it w3c/webrtc-stats#732, by @henbos.
-
-
1 pull request merged.
-
editorial: fix decoderImplementation idl reference w3c/webrtc-stats#734.
-
-
4 pull requests received 36 new comments.
-
Expose powerEfficientEncoder/Decoder if MediaCapabilities allows it w3c/webrtc-stats#732 (24 comments by @aboba, @alvestrand, @henbos, @pes10k, @vr000m, @xingri)
-
Add RTCInboundRtpStreamStats:decoderFallback w3c/webrtc-stats#725 (7 comments by @Diego-Perez-Botero, @henbos, @xingri)
-
w3c/mediacapture-extensions
-
3 issues opened.
-
Limit when configurationchange fires to useful cases. w3c/mediacapture-extensions#87, by @jan-ivar.
-
Detecting user-actionable camera issues (e.g., camera shutters) w3c/mediacapture-extensions#140, by @guidou.
-
Clarify which event loop task will be used for track in configuration change . w3c/mediacapture-extensions#86, by @beaufortfrancois.
-
-
2 issues closed.
-
Limit when configurationchange fires to useful cases. w3c/mediacapture-extensions#87.
-
MediaStreamTrack: actual frame rates captured w3c/mediacapture-extensions#76.
-
-
3 issues received 12 new comments.
-
Detecting user-actionable camera issues (e.g., camera shutters) w3c/mediacapture-extensions#140 (7 comments by @eladalon1983, @jan-ivar, @youennf)
-
Limit when configurationchange fires to useful cases. w3c/mediacapture-extensions#87 (3 comments by @eladalon1983, @jan-ivar, @youennf)
-
Clarify which event loop task will be used for track in configuration change . w3c/mediacapture-extensions#86 (2 comments by @jan-ivar, @youennf)
-
-
1 pull request opened.
-
Queue a task to fire configurationchange w3c/mediacapture-extensions#88, by @beaufortfrancois.
-
-
1 pull request merged.
-
MediaStreamTrack.getFrameStats() w3c/mediacapture-extensions#77.
-
-
5 pull requests received 39 new comments.
-
Add changes to configurationchange MediaStreamTrack event w3c/mediacapture-extensions#83 (29 comments by @alvestrand, @annevk, @beaufortfrancois, @eehakkin, @eladalon1983, @jan-ivar, @youennf)
-
Queue a task to fire configurationchange w3c/mediacapture-extensions#88 (4 comments by @beaufortfrancois, @youennf)
-
Restrict onconfigurationchange to background blur w3c/mediacapture-extensions#80 (4 comments by @eehakkin, @jan-ivar)
-
w3c/webrtc-ice
-
1 issue received 2 new comments.
w3c/webrtc-nv-use-cases
-
5 issues opened.
-
Dropping "NV" from the document name w3c/webrtc-nv-use-cases#107, by @aboba.
-
Section 3.10.3: Feedback related to decoding pre-encoded media use case w3c/webrtc-nv-use-cases#106, by @youennf.
-
Section 3.10.2: Feedback related to Transmitting stored encoded media use case w3c/webrtc-nv-use-cases#105, by @youennf.
-
Section 3.10.1: Feedback related to Live encoded non-WebRTC media use case w3c/webrtc-nv-use-cases#104, by @youennf.
-
Section 3.2: Feedback related to WebRTC-NV Low Latency Streaming Use Case w3c/webrtc-nv-use-cases#103, by @youennf.
-
-
1 issue received 1 new comment.
-
standardized support for captions/subtitles w3c/webrtc-nv-use-cases#70 (1 comment by @KiaraGrouwstra)
-
-
1 pull request opened.
-
Rename "WebRTC-NV Use Cases" to "WebRTC Extended Use Cases" w3c/webrtc-nv-use-cases#108, by @aboba.
-
w3c/mediacapture-image
-
2 pull requests opened.
-
Update macOS support w3c/mediacapture-image#300, by @beaufortfrancois.
-
Update Image Capture polyfill w3c/mediacapture-image#299, by @FluorescentHallucinogen.
-
-
2 pull requests merged.
-
Update macOS support w3c/mediacapture-image#300.
-
Update Image Capture polyfill w3c/mediacapture-image#299.
-
-
1 pull request received 8 new comments.
-
Update Image Capture polyfill w3c/mediacapture-image#299 (8 comments by @beaufortfrancois, @FluorescentHallucinogen, @riju, @w3cbot)
-
w3c/mediacapture-record
-
1 issue closed.
-
Add replaceTrack method to MediaStream w3c/mediacapture-record#167.
-
-
3 issues received 3 new comments.
-
More information about timing of recording (start event, blob event, stop event) w3c/mediacapture-record#208 (1 comment by @sepehr500)
-
-
2 pull requests closed.
-
Add replaceStream to MediaRecorder w3c/mediacapture-record#186.
-
Add replaceTrack method to MediaRecorder. w3c/mediacapture-record#187.
-
-
4 pull requests received 26 new comments.
-
Add keyframe interval support. w3c/mediacapture-record#216 (21 comments by @alvestrand, @handellm, @henbos, @jan-ivar, @Pehrsons, @shangl, @youennf)
-
Make Error Event go after ondataavailable. w3c/mediacapture-record#118 (3 comments by @alvestrand, @jan-ivar, @Pehrsons)
-
w3c/webrtc-pc
-
5 issues opened.
-
Hard to tell if there are state gaps in connectionState algorithm w3c/webrtc-pc#2827, by @jan-ivar.
-
ongatheringstatechange references wrong ICE gathering state w3c/webrtc-pc#2825, by @jan-ivar.
-
RTCSctpTransport.maxMessageSize is a floating point type w3c/webrtc-pc#2822, by @docfaraday.
-
-
5 issues received 21 new comments.
-
Why is RTCIceCandidatePairStats.totalRoundTripTime mandatory to implement, but not responsesReceived? w3c/webrtc-pc#2819 (9 comments by @alvestrand, @dontcallmedom, @fippo, @jan-ivar)
-
Hard to tell if there are state gaps in connectionState algorithm w3c/webrtc-pc#2827 (5 comments by @jan-ivar, @lgrahl, @pthatcher)
-
Maybe setParameters/insertDtmf/replaceTrack should reject on [[Stopping]] as well as [[Stopped]]? w3c/webrtc-pc#2820 (5 comments by @aboba, @docfaraday, @jan-ivar)
-
-
8 pull requests opened.
-
Update README w3c/webrtc-pc#2830, by @fippo.
-
setParameters(), replaceTrack(), & insertDTMF() reject after stop(). w3c/webrtc-pc#2829, by @jan-ivar.
-
Express RTCPeerConnectionState values using [[IceConnectionState]], and reduce complexity w3c/webrtc-pc#2828, by @jan-ivar.
-
Add internal slots for signaling state, connection state, ice gatheri… w3c/webrtc-pc#2826, by @jan-ivar.
-
Update to ReSpec version 32.7.1 w3c/webrtc-pc#2824, by @dontcallmedom.
-
Update title of spec, removing 1.0 and making it 'in' rather than 'between' browsers w3c/webrtc-pc#2823, by @dontcallmedom.
-
Update to ReSpec version 32.7.0 w3c/webrtc-pc#2821, by @dontcallmedom.
-
Use markup conventions for algorithms w3c/webrtc-pc#2818, by @dontcallmedom.
-
-
3 pull requests merged.
-
Update README w3c/webrtc-pc#2830.
-
Update to ReSpec version 32.7.0 w3c/webrtc-pc#2821.
-
-
4 pull requests received 9 new comments.
-
Use markup conventions for algorithms w3c/webrtc-pc#2818 (4 comments by @alvestrand, @dontcallmedom, @fippo)
-
Express RTCPeerConnectionState values using [[IceConnectionState]], and reduce complexity w3c/webrtc-pc#2828 (2 comments by @alvestrand, @jan-ivar)
-
setParameters(), replaceTrack(), & insertDTMF() reject after stop(). w3c/webrtc-pc#2829 (2 comments by @alvestrand, @jan-ivar)
-
Add internal slots for signaling state, connection state, ice gatheri… w3c/webrtc-pc#2826 (1 comment by @alvestrand)
-
w3c/mediacapture-screen-share-extensions
-
1 issue opened.
-
Capability Delegation for getDisplayMedia() w3c/mediacapture-screen-share-extensions#3, by @eladalon1983.
-
-
2 issues received 8 new comments.
-
Auto-pause capture when user switches captured content w3c/mediacapture-screen-share-extensions#4 (7 comments by @eladalon1983, @jan-ivar, @youennf)
-
Capability Delegation for getDisplayMedia() w3c/mediacapture-screen-share-extensions#3 (1 comment by @jan-ivar)
-
w3c/webrtc-svc
-
3 issues opened.
-
Why is scalabilityMode not an enum? w3c/webrtc-svc#87, by @henbos.
-
Other modes missing from the table w3c/webrtc-svc#83, by @aboba.
-
L3T1_KEY is missing from the table, but not the diagram section w3c/webrtc-svc#81, by @henbos.
-
-
4 issues closed.
-
S modes and a single active simulcast layer w3c/webrtc-svc#73.
-
Why is scalabilityMode not an enum? w3c/webrtc-svc#87.
-
Other modes missing from the table w3c/webrtc-svc#83.
-
L3T1_KEY is missing from the table, but not the diagram section w3c/webrtc-svc#81.
-
-
4 issues received 12 new comments.
-
S modes and a single active simulcast layer w3c/webrtc-svc#73 (5 comments by @aboba, @alvestrand, @Orphis)
-
L3T1_KEY is missing from the table, but not the diagram section w3c/webrtc-svc#81 (4 comments by @aboba, @DanilChapovalov, @henbos)
-
-
4 pull requests opened.
-
Refine error conditions for use of 'S' modes w3c/webrtc-svc#86, by @aboba.
-
Minor fix for simulcast with L1T3 sample code. w3c/webrtc-svc#85, by @taste1981.
-
Add missing modes to the table w3c/webrtc-svc#84, by @aboba.
-
Addition of mode L3T1_KEY to table w3c/webrtc-svc#82, by @aboba.
-
-
4 pull requests merged.
-
Refine error conditions for use of 'S' modes w3c/webrtc-svc#86.
-
Minor fix for simulcast with L1T3 sample code. w3c/webrtc-svc#85.
-
Add missing modes to the table w3c/webrtc-svc#84.
-
Addition of mode L3T1_KEY to table w3c/webrtc-svc#82.
-
-
3 pull requests received 5 new comments.
w3c/webrtc-encoded-transform
-
1 issue opened.
-
Define needed data to pass between depacketizer and decoder w3c/webrtc-encoded-transform#174, by @alvestrand.
-
-
1 pull request opened.
-
Add presentationTimestamp to RTCEncodedVideoFrameMetadata w3c/webrtc-encoded-transform#173, by @tonyherre.
-
-
3 pull requests received 6 new comments.
-
make generateKeyFrame take a list of rids and return a promise<undefined> w3c/webrtc-encoded-transform#165 (4 comments by @youennf)
-
Add rtp timestamp and capture time to RTCEncodedVideoFrameMetadata w3c/webrtc-encoded-transform#137 (1 comment by @tonyherre)
-
Add presentationTimestamp to RTCEncodedVideoFrameMetadata w3c/webrtc-encoded-transform#173 (1 comment by @tonyherre)
-
w3c/mediacapture-handle
-
2 issues received 7 new comments.
-
Expose a MessagePort using Capture Handle w3c/mediacapture-handle#70 (4 comments by @eladalon1983, @jan-ivar, @youennf)
-
w3c/mediacapture-region
-
2 issues opened.
-
Prevent uncropping w3c/mediacapture-region#76, by @eladalon1983.
-
[QUESTION] How to pass CropTarget to chrome extension service worker? w3c/mediacapture-region#75, by @wlevchenko.
-
-
1 issue closed.
-
[QUESTION] How to pass CropTarget to chrome extension service worker? w3c/mediacapture-region#75.
-
-
1 issue received 4 new comments.
-
[QUESTION] How to pass CropTarget to chrome extension service worker? w3c/mediacapture-region#75 (4 comments by @beaufortfrancois, @eladalon1983, @wlevchenko, @youennf)
-
w3c/mediacapture-output
-
1 issue closed.
-
Spec uses settings object's responsible document which was removed w3c/mediacapture-output#132.
-
-
2 pull requests merged.
-
Editorial: use associated Document in place of responsible document w3c/mediacapture-output#131.
-
Fix default allowlist link that broke. w3c/mediacapture-output#134.
-
w3c/mediacapture-transform
-
1 issue received 1 new comment.
w3c/webrtc-identity
-
1 issue opened.
-
Broken references in Identity for WebRTC 1.0 w3c/webrtc-identity#40, by @dontcallmedom-bot.
-
-
1 pull request opened.
-
Fix broken links w3c/webrtc-identity#41, by @dontcallmedom.
-
TR publications
-
11 documents published.
-
Identifiers for WebRTC's Statistics API published twice as a Candidate Recommendation Draft. History of Identifiers for WebRTC's Statistics API
-
Media Capture and Streams published as a Candidate Recommendation Draft. History of Media Capture and Streams
-
WebRTC Encoded Transform published as a Working Draft. History of WebRTC Encoded Transform
-
Scalable Video Coding (SVC) Extension for WebRTC published twice as a Working Draft. History of Scalable Video Coding (SVC) Extension for WebRTC
-
Screen Capture published as a Working Draft. History of Screen Capture
-
WebRTC Next Version Use Cases published 4 times as a Draft Note. History of WebRTC Next Version Use Cases
-
Past meetings
-
1 meeting.
Participants
-
6 participants joined.
-
Antoine Dumas (Preset Computing) joined.
-
Dag-Inge Aas (Daily, Co) joined.
-
Aleix Conchillo Flaqué (Daily, Co) joined.
-
Sun Shin (NVIDIA) joined.
-
Sameer Vijaykar (Google LLC) joined.
-
Filipi Da Silva Fuchter (Daily, Co) joined.
-
-
1 participant left.
-
Matt Gordon (Microsoft Corporation) left.
-
-
2 organizations joined.
-
Preset Computing joined.
-
NVIDIA joined.
-
GitHub
w3c/webrtc-extensions
-
2 issues opened.
-
Not clear what should happen if header extensions are inconsistent across bundled transports w3c/webrtc-extensions#140, by @henbos.
-
support disable ipv6 candidate in RTCConfiguration w3c/webrtc-extensions#138, by @bdrtc.
-
-
2 issues closed.
-
Disabling hardware acceleration w3c/webrtc-extensions#98.
-
maxFramerate probably should not be allowed in addTransceiver/setParameters for audio senders w3c/webrtc-extensions#107.
-
-
11 issues received 33 new comments.
-
support disable ipv6 candidate in RTCConfiguration w3c/webrtc-extensions#138 (13 comments by @bdrtc, @fippo, @henbos, @steely-glint)
-
Not clear what should happen if header extensions are inconsistent across bundled transports w3c/webrtc-extensions#140 (6 comments by @fippo, @henbos)
-
Suggestion: rename [[HeaderExtensionsToOffer]] to [[HeaderExtensionsSupported]] w3c/webrtc-extensions#132 (2 comments by @bdrtc, @fippo)
-
Negotiationless codec selection and per-encoding layer codec configuration w3c/webrtc-extensions#126 (2 comments by @aboba, @henbos)
-
Should setOfferedHeaderExtensions be allowed to restart stopped extensions? w3c/webrtc-extensions#134 (1 comment by @fippo)
-
Potential web compat issue with setOfferedRtpHeaderExtensions w3c/webrtc-extensions#130 (1 comment by @fippo)
-
How to deal with encoder errors / codec availability errors? w3c/webrtc-extensions#127 (1 comment by @henbos)
-
Deprecate audio/video enumeration in getCapabilities in favour of Media Capabilities API w3c/webrtc-extensions#95 (1 comment by @aboba)
-
maxFramerate probably should not be allowed in addTransceiver/setParameters for audio senders w3c/webrtc-extensions#107 (1 comment by @aboba)
-
-
1 pull request opened.
-
Per-encoding codec selection w3c/webrtc-extensions#139, by @aboba.
-
-
1 pull request merged.
-
add sender/receiver extensions to disable hardware encoding w3c/webrtc-extensions#128.
-
w3c/webrtc-encoded-transform
-
1 issue opened.
-
Tell SDP negotiation to negotiate support for non-standard codecs w3c/webrtc-encoded-transform#172, by @alvestrand.
-
-
2 issues received 3 new comments.
-
expose RTP sequence numbers w3c/webrtc-encoded-transform#166 (2 comments by @fippo, @vitaly-castLabs)
-
Tell SDP negotiation to negotiate support for non-standard codecs w3c/webrtc-encoded-transform#172 (1 comment by @fippo)
-
-
1 pull request merged.
-
audio: add rtp sequence number on incoming frames w3c/webrtc-encoded-transform#154.
-
-
4 pull requests received 15 new comments.
-
make generateKeyFrame take a list of rids and return a promise<undefined> w3c/webrtc-encoded-transform#165 (6 comments by @alvestrand, @fippo, @jan-ivar, @youennf)
-
audio: add rtp sequence number on incoming frames w3c/webrtc-encoded-transform#154 (4 comments by @fippo, @steely-glint)
-
add mimeType to metadata w3c/webrtc-encoded-transform#140 (3 comments by @alvestrand, @fippo, @youennf)
-
Add rtp timestamp and capture time to RTCEncodedVideoFrameMetadata w3c/webrtc-encoded-transform#137 (2 comments by @alvestrand, @Orphis)
-
w3c/webrtc-nv-use-cases
-
10 issues opened.
-
Section 3.10: "(outgoing/incoming) WebRTC connection" not defined w3c/webrtc-nv-use-cases#102, by @stefhak.
-
Section 3.10.2: Introducing app content-decisions at the encoded video level isn't webby w3c/webrtc-nv-use-cases#101, by @jan-ivar.
-
Section 3.10.1: Live encoded non-WebRTC media use case not compelling w3c/webrtc-nv-use-cases#100, by @jan-ivar.
-
Sections 3.10.1, 3.10.2 and 3.10.3: Control of packetization/depacketization w3c/webrtc-nv-use-cases#96, by @aboba.
-
Low Latency Streaming: Review of requirements w3c/webrtc-nv-use-cases#95, by @aboba.
-
Section 3.2.1: Improvements for game pad input w3c/webrtc-nv-use-cases#94, by @aboba.
-
Section 3.10: A little thought about the one way media use case w3c/webrtc-nv-use-cases#93, by @bdrtc.
-
N15 latency control should be formulated in a technology-agnostic way w3c/webrtc-nv-use-cases#91, by @alvestrand.
-
Is the DRM requirement in the Low latency Broadcast with Fanout use case satisfied by data channels? w3c/webrtc-nv-use-cases#86, by @jan-ivar.
-
What is a "node" in the Low latency Broadcast with Fanout use case? w3c/webrtc-nv-use-cases#85, by @jan-ivar.
-
-
7 issues closed.
-
N15 latency control should be formulated in a technology-agnostic way w3c/webrtc-nv-use-cases#91.
-
Is the DRM requirement in the Low latency Broadcast with Fanout use case satisfied by data channels? w3c/webrtc-nv-use-cases#86.
-
What is a "node" in the Low latency Broadcast with Fanout use case? w3c/webrtc-nv-use-cases#85.
-
use case:disable A/V sync for remote control or online gaming w3c/webrtc-nv-use-cases#78.
-
Use case: Transmit stored pre-encoded content over RTP w3c/webrtc-nv-use-cases#82.
-
Use case: Transmit pre-encoded live content over RTP w3c/webrtc-nv-use-cases#81.
-
-
1 issue reopened.
-
Advanced Codec Capabilities API w3c/webrtc-nv-use-cases#53, by @henbos.
-
-
10 issues received 31 new comments.
-
Section 3.10.1: Live encoded non-WebRTC media use case not compelling w3c/webrtc-nv-use-cases#100 (16 comments by @aboba, @alvestrand, @eladalon1983, @jan-ivar, @steely-glint, @youennf)
-
What is a "node" in the Low latency Broadcast with Fanout use case? w3c/webrtc-nv-use-cases#85 (2 comments by @aboba, @alvestrand)
-
Is the DRM requirement in the Low latency Broadcast with Fanout use case satisfied by data channels? w3c/webrtc-nv-use-cases#86 (2 comments by @aboba)
-
Section 3.10.2: Introducing app content-decisions at the encoded video level isn't webby w3c/webrtc-nv-use-cases#101 (1 comment by @alvestrand)
-
Sections 3.10.1, 3.10.2 and 3.10.3: Control of packetization/depacketization w3c/webrtc-nv-use-cases#96 (1 comment by @alvestrand)
-
use case:disable A/V sync for remote control or online gaming w3c/webrtc-nv-use-cases#78 (1 comment by @bdrtc)
-
N15 latency control should be formulated in a technology-agnostic way w3c/webrtc-nv-use-cases#91 (1 comment by @aboba)
-
Use case: Process encoded data received via non-WebRTC means and inject into WebRTC-based media reception pipelines w3c/webrtc-nv-use-cases#83 (1 comment by @aboba)
-
-
9 pull requests opened.
-
N15 latency control should be formulated in a technology-agnostic way w3c/webrtc-nv-use-cases#99, by @aboba.
-
Clarify meaning of "node" in requirement N39 w3c/webrtc-nv-use-cases#98, by @aboba.
-
Remove DRM Requirement N36 w3c/webrtc-nv-use-cases#97, by @aboba.
-
Describe use cases for decoding pre-encoded media w3c/webrtc-nv-use-cases#92, by @alvestrand.
-
Remove requirement N36 (and substitute N13) w3c/webrtc-nv-use-cases#90, by @aboba.
-
Remove requirement N36 (and substitute N13) w3c/webrtc-nv-use-cases#89, by @aboba.
-
Remove requirement N36 (and substitute N13) w3c/webrtc-nv-use-cases#88, by @aboba.
-
Use case:Stored media for RTP transmission w3c/webrtc-nv-use-cases#87, by @alvestrand.
-
Add use case for connecting preencoded video from cameras w3c/webrtc-nv-use-cases#84, by @alvestrand.
-
-
6 pull requests merged.
-
N15 latency control should be formulated in a technology-agnostic way w3c/webrtc-nv-use-cases#99.
-
Remove DRM Requirement N36 w3c/webrtc-nv-use-cases#97.
-
Clarify meaning of "node" in requirement N39 w3c/webrtc-nv-use-cases#98.
-
Describe use cases for decoding pre-encoded media w3c/webrtc-nv-use-cases#92.
-
Use case:Stored media for RTP transmission w3c/webrtc-nv-use-cases#87.
-
Add use case for connecting preencoded video from cameras w3c/webrtc-nv-use-cases#84.
-
-
3 pull requests closed.
-
Remove requirement N36 (and substitute N13) w3c/webrtc-nv-use-cases#90.
-
Remove requirement N36 (and substitute N13) w3c/webrtc-nv-use-cases#89.
-
Remove requirement N36 (and substitute N13) w3c/webrtc-nv-use-cases#88.
-
-
2 pull requests received 2 new comments.
w3c/mediacapture-extensions
-
5 issues opened.
-
Face Detection: Variance of Results w3c/mediacapture-extensions#85, by @aboba.
-
Face Detection: Scope of Applicability w3c/mediacapture-extensions#84, by @aboba.
-
Filtering for relevant configurationchange events w3c/mediacapture-extensions#82, by @eladalon1983.
-
Alternative approach to configurationchange w3c/mediacapture-extensions#81, by @eladalon1983.
-
Face Detection: Segmentation metadata w3c/mediacapture-extensions#79, by @aboba.
-
-
5 issues received 27 new comments.
-
Filtering for relevant configurationchange events w3c/mediacapture-extensions#82 (14 comments by @beaufortfrancois, @eehakkin, @eladalon1983, @youennf)
-
Face Detection: Scope of Applicability w3c/mediacapture-extensions#84 (5 comments by @aboba, @steely-glint, @ttoivone, @youennf)
-
Face Detection: Segmentation metadata w3c/mediacapture-extensions#79 (4 comments by @aboba, @steely-glint, @ttoivone, @youennf)
-
Face Detection: Variance of Results w3c/mediacapture-extensions#85 (3 comments by @aboba, @ttoivone, @youennf)
-
Echo cancellation: Need to specify the source of the echo cancellation reference signal w3c/mediacapture-extensions#31 (1 comment by @zoschfrosch)
-
-
2 pull requests opened.
-
Add changes to configurationchange MediaStreamTrack event w3c/mediacapture-extensions#83, by @beaufortfrancois.
-
Restrict onconfigurationchange to background blur w3c/mediacapture-extensions#80, by @beaufortfrancois.
-
-
3 pull requests received 77 new comments.
-
Add face detection constraints and VideoFrameMetadata members w3c/mediacapture-extensions#78 (34 comments by @aboba, @alvestrand, @chrisn, @dontcallmedom, @jan-ivar, @martinthomson)
-
MediaStreamTrack.getFrameStats() w3c/mediacapture-extensions#77 (31 comments by @alvestrand, @dontcallmedom, @guidou, @henbos, @vr000m, @youennf)
-
Restrict onconfigurationchange to background blur w3c/mediacapture-extensions#80 (12 comments by @beaufortfrancois, @eladalon1983, @guidou, @riju, @youennf)
-
w3c/mediacapture-main
-
1 issue opened.
-
Better documentation of ended event w3c/mediacapture-main#924, by @eladalon1983.
-
-
1 issue closed.
-
Check if we use "Browsing Context" in our specs w3c/mediacapture-main#913.
-
-
1 issue received 4 new comments.
-
Garbage collection of live tracks w3c/mediacapture-main#910 (4 comments by @eladalon1983, @jan-ivar, @youennf)
-
-
3 pull requests opened.
-
Split device sanitation note into separate paragraph w3c/mediacapture-main#926, by @fippo.
-
Fix default allowlist link that broke. w3c/mediacapture-main#925, by @jan-ivar.
-
Update to latest ReSpec version 32.6.1 w3c/mediacapture-main#923, by @dontcallmedom.
-
-
4 pull requests merged.
-
Replace use of browsing context with modern constructs. w3c/mediacapture-main#919.
-
Fix default allowlist link that broke. w3c/mediacapture-main#925.
-
Update Privacy and Security Considerations to reflect spec. w3c/mediacapture-main#897.
-
Update to latest ReSpec version 32.6.1 w3c/mediacapture-main#923.
-
-
2 pull requests received 3 new comments.
-
Replace use of browsing context with modern constructs. w3c/mediacapture-main#919 (2 comments by @jan-ivar)
-
Update Privacy and Security Considerations to reflect spec. w3c/mediacapture-main#897 (1 comment by @alvestrand)
-
w3c/webrtc-pc
-
2 issues opened.
-
maxFramerate probably should not be allowed in addTransceiver/setParameters for audio senders w3c/webrtc-pc#2815, by @aboba.
-
4 issues closed.
-
scaleResolutionDownBy's odd-resolution requirement trips up HW encoders w3c/webrtc-pc#2802.
-
6 issues received 15 new comments.
-
Missing url in RTCIceCandidateInit w3c/webrtc-pc#2795 (9 comments by @alvestrand, @fippo, @jan-ivar, @youennf)
-
Should garbage collecting RTCDataChannels be observable? w3c/webrtc-pc#2624 (2 comments by @jan-ivar, @youennf)
-
maxFramerate probably should not be allowed in addTransceiver/setParameters for audio senders w3c/webrtc-pc#2815 (1 comment by @aboba)
-
A simulcast transceiver saved from rollback by addTrack doesn't re-associate, but unicast does w3c/webrtc-pc#2796 (1 comment by @jan-ivar)
-
-
3 pull requests opened.
-
Update to ReSpec version 32.6.1 w3c/webrtc-pc#2816, by @dontcallmedom.
-
Update explanation of simulcast envelope. w3c/webrtc-pc#2814, by @jan-ivar.
-
Ignore comma-separated rid alternatives. w3c/webrtc-pc#2813, by @jan-ivar.
-
-
6 pull requests merged.
-
Update explanation of simulcast envelope. w3c/webrtc-pc#2814.
-
Ignore comma-separated rid alternatives. w3c/webrtc-pc#2813.
-
Update to ReSpec version 32.6.1 w3c/webrtc-pc#2816.
-
Remove reference to removed test w3c/webrtc-pc#2809.
-
Allow encoder resolution alignment in scaleResolutionDownBy. w3c/webrtc-pc#2808.
-
add test annotations for msid generation w3c/webrtc-pc#2812.
-
-
5 pull requests received 11 new comments.
-
Allow encoder resolution alignment in scaleResolutionDownBy. w3c/webrtc-pc#2808 (3 comments by @jan-ivar)
w3c/mediacapture-handle
-
1 issue received 3 new comments.
-
Expose a MessagePort using Capture Handle w3c/mediacapture-handle#70 (3 comments by @arnaudbud, @eladalon1983, @youennf)
-
w3c/webrtc-svc
-
2 issues opened.
-
Lack of access to webrtc-svc w3c/webrtc-svc#80, by @alvestrand.
-
Returning the default scalabilityMode problematic after fallback w3c/webrtc-svc#75, by @Orphis.
-
-
4 issues closed.
-
should scalabilityMode be an array scalabilityModes? w3c/webrtc-svc#50.
-
Lack of access to webrtc-svc w3c/webrtc-svc#80.
-
Returning the default scalabilityMode problematic after fallback w3c/webrtc-svc#75.
-
`getCapabilities` seems to leak hardware capabilities w/o a permission w3c/webrtc-svc#22.
-
-
4 issues received 6 new comments.
-
SVC getCapabilities() is redundant with Media Capabilities query w3c/webrtc-svc#49 (3 comments by @aboba, @fippo, @henbos)
-
Returning the default scalabilityMode problematic after fallback w3c/webrtc-svc#75 (1 comment by @aboba)
-
-
4 pull requests opened.
-
Update getParameters() to not return the default scalabilityMode w3c/webrtc-svc#79, by @Orphis.
-
Add Media Capabilities Sample w3c/webrtc-svc#78, by @aboba.
-
Remove extension to getCapabilities() in favour of MediaCapabilities w3c/webrtc-svc#77, by @aboba.
-
Remove extension to getCapabilities() in favour of MediaCapabilities w3c/webrtc-svc#76, by @Orphis.
-
-
2 pull requests merged.
-
Update getParameters() to not return the default scalabilityMode w3c/webrtc-svc#79.
-
Remove extension to getCapabilities() in favour of MediaCapabilities w3c/webrtc-svc#76.
-
-
2 pull requests closed.
-
Add Media Capabilities Sample w3c/webrtc-svc#78.
-
Remove extension to getCapabilities() in favour of MediaCapabilities w3c/webrtc-svc#77.
-
-
4 pull requests received 18 new comments.
-
Remove extension to getCapabilities() in favour of MediaCapabilities w3c/webrtc-svc#76 (12 comments by @aboba, @dontcallmedom, @henbos, @jan-ivar, @Orphis, @youennf)
-
Update getParameters() to not return the default scalabilityMode w3c/webrtc-svc#79 (4 comments by @aboba, @jan-ivar, @youennf)
-
Remove extension to getCapabilities() in favour of MediaCapabilities w3c/webrtc-svc#77 (1 comment by @aboba)
-
w3c/webrtc-stats
-
3 issues opened.
-
Delete "Retiring stats objects" section w3c/webrtc-stats#729, by @henbos.
-
"media-playout" needs to have a "kind" member w3c/webrtc-stats#727, by @henbos.
-
Add RTCInboundRtpStreamStats:decoderFallback w3c/webrtc-stats#724, by @xingri.
-
-
1 issue closed.
-
"media-playout" needs to have a "kind" member w3c/webrtc-stats#727.
-
-
2 issues received 9 new comments.
-
Add RTCInboundRtpStreamStats:decoderFallback w3c/webrtc-stats#724 (8 comments by @eshrubs, @fippo, @henbos, @xingri)
-
-
3 pull requests opened.
-
Add "kind" to RTCAudioPlayoutStats w3c/webrtc-stats#728, by @henbos.
-
Fix stats object reference in example code w3c/webrtc-stats#726, by @redoPop.
-
Add RTCInboundRtpStreamStats:decoderFallback w3c/webrtc-stats#725, by @xingri.
-
-
3 pull requests merged.
-
Fix stats object reference in example code w3c/webrtc-stats#726.
-
Add "kind" to RTCAudioPlayoutStats w3c/webrtc-stats#728.
-
Don't export the informative RTCStats reproduction w3c/webrtc-stats#721.
-
-
4 pull requests received 7 new comments.
-
Add RTCInboundRtpStreamStats:decoderFallback w3c/webrtc-stats#725 (4 comments by @fippo, @henbos, @xingri)
-
w3c/mediacapture-screen-share-extensions
-
1 issue received 2 new comments.
-
Auto-pause capture when user switches captured content w3c/mediacapture-screen-share-extensions#4 (2 comments by @eladalon1983, @youennf)
-
w3c/webrtc-provisional-stats
-
1 pull request opened.
-
Affiliation change w3c/webrtc-provisional-stats#41, by @vr000m.
-
-
1 pull request merged.
-
Affiliation change w3c/webrtc-provisional-stats#41.
-
w3c/mediacapture-record
-
1 issue received 3 new comments.
-
Ability to record non-realtime / frame-by-frame w3c/mediacapture-record#213 (3 comments by @pie6k, @Vanilagy, @yume-chan)
-
-
1 pull request opened.
-
Add keyframe interval support. w3c/mediacapture-record#216, by @handellm.
-
-
1 pull request closed.
-
Input width, height MUST be recorded and playable w3c/mediacapture-record#172.
-
-
2 pull requests received 7 new comments.
-
Input width, height MUST be recorded and playable w3c/mediacapture-record#172 (1 comment by @alvestrand)
w3c/mediacapture-output
-
1 pull request opened.
-
Fix default allowlist link that broke. w3c/mediacapture-output#134, by @jan-ivar.
-
-
1 pull request received 2 new comments.
-
Fix default allowlist link that broke. w3c/mediacapture-output#134 (2 comments by @dontcallmedom, @jan-ivar)
-
w3c/mediacapture-image
-
1 issue received 1 new comment.
w3c/mediacapture-region
-
1 issue received 4 new comments.
-
Is muting track the right call for empty cropped tracks? w3c/mediacapture-region#9 (4 comments by @eladalon1983, @thomas-gg)
-
w3c/mediacapture-screen-share
-
1 issue opened.
-
Detect when minimizing a window pauses capture (was: Capability polling - capture-while-minimized) w3c/mediacapture-screen-share#257, by @eladalon1983.
-
-
1 issue received 2 new comments.
-
Detect when minimizing a window pauses capture (was: Capability polling - capture-while-minimized) w3c/mediacapture-screen-share#257 (2 comments by @eladalon1983, @youennf)
-
-
1 pull request opened.
-
Fix default allowlist link that broke. w3c/mediacapture-screen-share#256, by @jan-ivar.
-
-
1 pull request merged.
-
Fix default allowlist link that broke. w3c/mediacapture-screen-share#256.
-
-
1 pull request received 1 new comment.
-
Remove restriction over changing capture source w3c/mediacapture-screen-share#170 (1 comment by @eladalon1983)
-
w3c/mediacapture-transform
-
1 issue received 1 new comment.
-
1 pull request received 2 new comments.
-
Update proposal according to WG directions w3c/mediacapture-transform#66 (2 comments by @dontcallmedom, @foolip)
-