- From: Erik Språng via GitHub <sysbot+gh@w3.org>
- Date: Wed, 05 Mar 2025 14:29:24 +0000
- To: public-webrtc-logs@w3.org
It's a little strange to me that we chose the 0-63 as input, as that's not a range at all defined by the bitstream spec - rather it's a "convenience" feature of the libvpx/libaom implementations in order to keep parameters similar between codecs. For a raw interface like WebCodecs I think the bitstream spec would have made more sense (and allowed more granular bitrate control), but I fell it's too late to update that specific part of the API... Also I wonder how many implementations _actually_ support the QP = 0 level, as that implies the highly specialized lossless encoding mode. -- GitHub Notification of comment by sprangerik Please view or discuss this issue at https://github.com/w3c/webrtc-stats/issues/799#issuecomment-2701109418 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 5 March 2025 14:29:25 UTC