![]() Everything else in this specification is normative. Require broad knowledge of video encoders, audio-processing steps orĪ separate section of this specification describes expected behaviorįor specific components that process a MediaStreamTrack.Īs well as sections marked as non-normative, all authoring guidelines, diagrams, examples, and notes in this specification are non-normative. These settings are not intended to replace encoder-level settingsĬompletely but rather complement them with a simpler hint that does not Music-studio application would be able to prevent noise suppression from Motion from desktop capture at the cost of individual frame detail. Web application that streams video-game content would be able to preserve User input to inform consumers of what kind of content is being encoded. In some cases the web application can make a more-educated guess or take Example shows 100%, 50% and 25%Ĭubic downscale corresponding to downscaling from HD to VGA and QVGA Scenarios, this example illustrates lost text intelligibility when While downscaling can be done to preserve motion in low-bitrate This mismatch may also happen when HDMI video-capture cardsĪre seen as USB webcams but actually screencast webpage text. Webcam video on the other hand leads to too-blurry content when beingĮither quantized or downscaled beyond readability to meet bitrate Treating highly-detailed content as regular Screencasting high-motion content such as a movie or streaming a video This manifests as high framedropping when While usually appropriate this educated guess leads to sub-optimal ![]() Webcam video, and higher quantization levels and downscaling are Another assumption is that regular USB video devices provide Quantization levels, and drop frames extensively to meet bitrate This guess may be based onĪssuming that screencast content, such asĬsktopCapture, contains text content and must use low Without automatic detection of media content, a MediaStreamTrackĬonsumer can only make an educated guess. If the content is downscaled or otherwise blurry. Is completely unintelligible if the quantization levels are too high or Screencast content of presentations or webpages with a lot of text content Intelligible even when downscaled or with high quantization levels. It is less appropriate for music signals.įor video, webcam content often require denoising and is often While this makes speech more intelligible Work well on music, and noise-suppression algorithms might remove drum ![]() 5.2.1 Dictionary RTCRtpSendParameters New MembersĪlgorithms used for processing speech and music differ greatly.Įcho-cancellation algorithms developed for speech-type content might not.5.2 Degradation preference when encoding.Behaviors of other components based on content-hint Must disclose the information in accordance with Knowledge of a patent which the individual believes contains Made in connection with the deliverables of Or obsoleted by other documents at any time. This is a draft document and may be updated, replaced Publication as a Working Draft does not imply endorsement This document is intended to become a W3C Recommendation.Īlternatively, you can send comments to our mailing list.Īrchives) with at the start of your This document was published by the Web Real-Time Communications Working Group as a Of this technical report can be found in the A list of current W3C publications and the latest revision This section describes the status of thisĭocument at the time of its publication. ) that process a track's audio or videoĬontent to choose processing parameters that are appropriate to the (defined in ) or MediaRecorder (defined in MediaStreamTrack sinks such as RTCPeerConnection Optional hint about the user's preference on how the media shouldīe treated when insufficient resources for perfect reproduction This specification extends MediaStreamTrack to provide an Trademark and permissive document license rules Participate: GitHub w3c/mst-content-hint File an issue Commit history Pull requests I have tried to reduce bitrates but to no avail.22 July 2021 This version: Latest published version: Latest editor's draft: Test suite: Previous version: Editor: Harald Alvestrand ( Google) The peers are not on the same network.Īt some point, the audio starts to add clicks to the stream. Signaling and candidates all seem to work correctly. I am using WebRTC to set up the Peer connection. I have created an app with a live conversation module in javascript.
0 Comments
Leave a Reply. |