- From: youennf via GitHub <sysbot+gh@w3.org>
- Date: Tue, 04 May 2021 06:45:25 +0000
- To: public-webrtc-logs@w3.org
There are some known advantages of using AudioWorklet over MediaStreamTrackProcessor. With AudioWorklet, an application is able to implement its own buffering strategy and the best way to present data for processing. For instance, an application might want to start with processing 10 ms chunks and will want to buffer 5 chunks of these. At some point though, to cope with networking, the application will switch to 50 ms chunks and will increase buffering to 5 chunks of 50ms. This is not easily doable with MediaStreamTrackProcessor: maxBufferSize is fixed at construction time and audio frames size is not in the application control. -- GitHub Notification of comment by youennf Please view or discuss this issue at https://github.com/w3c/mediacapture-transform/issues/29#issuecomment-831718079 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 4 May 2021 06:45:27 UTC