You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Decoding of pre-encoded media can be done via either MSE or WebCodecs.
It seems this use case is mainly based on the assumption that JS based processing via WebCodecs is not optimal for speedy processing and the WebRTC pipeline would be more efficient.
It would be good to have measurements to understand what perf improvements we are talking about and the shortcomings of MSE and/or WebCodecs are not fitting the bill.
Is it possible this is only User Agent implementation issues?
The text was updated successfully, but these errors were encountered:
aboba
changed the title
Feedback related to decoding pre-encoded media use case
Section 3.10.1: Feedback related to decoding pre-encoded media use case
May 15, 2023
aboba
changed the title
Section 3.10.1: Feedback related to decoding pre-encoded media use case
Section 3.10.3: Feedback related to decoding pre-encoded media use case
May 15, 2023
Decoding of pre-encoded media can be done via either MSE or WebCodecs.
It seems this use case is mainly based on the assumption that JS based processing via WebCodecs is not optimal for speedy processing and the WebRTC pipeline would be more efficient.
It would be good to have measurements to understand what perf improvements we are talking about and the shortcomings of MSE and/or WebCodecs are not fitting the bill.
Is it possible this is only User Agent implementation issues?
The text was updated successfully, but these errors were encountered: