@MikeLud1 Yup, I got notifications about that too.
As nice as it is to have a workaround, it is simply not acceptable to require users to do that in order to use the WebCodecs player when there are other players that don't require such an effort to use.
Besides, I find that WebCodecs is less robust than Media Source Extensions (the API used by UI3's HTML5 player). For example on my system here with Nvidia graphics, WebCodecs fails to decode a 5120x1440 (dual 4MP sensor cam) video unless I configure the video decoder to not use hardware acceleration. When hardware acceleration is used, it complains that there was no keyframe. The HTML5 player, by comparison, is automatically falling back to software decoding without UI3 needing to do anything, and for some reason the HTML5 player's software decoder appears to be substantially more efficient than WebCodecs's software decoder.
As nice as it is to have a workaround, it is simply not acceptable to require users to do that in order to use the WebCodecs player when there are other players that don't require such an effort to use.
Besides, I find that WebCodecs is less robust than Media Source Extensions (the API used by UI3's HTML5 player). For example on my system here with Nvidia graphics, WebCodecs fails to decode a 5120x1440 (dual 4MP sensor cam) video unless I configure the video decoder to not use hardware acceleration. When hardware acceleration is used, it complains that there was no keyframe. The HTML5 player, by comparison, is automatically falling back to software decoding without UI3 needing to do anything, and for some reason the HTML5 player's software decoder appears to be substantially more efficient than WebCodecs's software decoder.