Re: qt6-qtwebengine-freeworld?
Ankur Sinha via rpmfusion-developers wrote: >> That said, Chromium also uses a bundled OpenH264 to encode H.264 for >> WebRTC. If that is not patched to support dlopening, then we still need a >> qt6- qtwebengine-freeworld built with the bundled OpenH264 enabled. We >> are not allowed to ship OpenH264 directly in Fedora, only through that >> Cisco arrangement. > > I have these packages: > > ``` > $ rpm -qa \*264\* > x264-libs-0.164-8.20220602gitbaee400f.fc39.x86_64 > openh264-2.3.1-2.fc39.x86_64 > mozilla-openh264-2.3.1-2.fc39.x86_64 > gstreamer1-plugin-openh264-1.22.1-1.fc39.x86_64 > ``` > > > Again, not sure if stuff works as it should. I just haven't noticed any > issues in normal usage yet. Does "normal usage" include WebRTC use? Though even there, you can probably get away with only VP8/VP9 support in most cases. But if you do not have working H.264 encoding and the other end supports only H.264 (e.g., Safari 11 or 12.0, they added VP8 support in 12.1 according to Wikipedia), you are stuck. So it is kinda hard to test it in daily use until problems happen. You can use this page to test: https://mozilla.github.io/webrtc-landing/pc_test_no_h264.html though that might be testing only what the browser CLAIMS to support and not what actually works. That said, dlopening OpenH264 should work in qt6-qtwebengine thanks to these downstream patches: https://src.fedoraproject.org/rpms/qt6-qtwebengine/blob/rawhide/f/qtwebengine-blink-dlopen-h264.patch https://src.fedoraproject.org/rpms/qt6-qtwebengine/blob/rawhide/f/qtwebengine-webrtc-dlopen-h264.patch (We do not have these in qt5-qtwebengine, only in qt6-qtwebengine.) Kevin Kofler ___ rpmfusion-developers mailing list -- rpmfusion-developers@lists.rpmfusion.org To unsubscribe send an email to rpmfusion-developers-le...@lists.rpmfusion.org
Re: qt6-qtwebengine-freeworld?
Ankur Sinha via rpmfusion-developers wrote: > I upgraded here, so maybe I've done this in the past and it's still > there. I see this in my qutebrowser config: > > ``` > ppapi-widevine-path=/opt/google/chrome/libwidevinecdm.so > ``` So you have the proprietary google-chrome installed? That includes the DRM blob, and I guess it is one of the locations the QtWebEngine looks for it by default. If you want just Widevine without all of Google Chrome, then it is a game of finding and extracting the blob manually. I do not have Widevine at all, which means things like Netflix are just going to fail with an error message. > If there's a way to get the list or test out the supported codecs, I can > do that and report back. I assume at least H.264 works or Netflix would probably not work, would it? Though have you tried it with the FFmpeg from Fedora or only with the one from RPM Fusion? (In principle, both should support H.264 decoding, the one from Fedora through dlopened OpenH264 with a downstream Fedora patch, the one from RPM Fusion through the built-in decoder in FFmpeg.) Kevin Kofler ___ rpmfusion-developers mailing list -- rpmfusion-developers@lists.rpmfusion.org To unsubscribe send an email to rpmfusion-developers-le...@lists.rpmfusion.org
Re: qt6-qtwebengine-freeworld?
On Tue, Sep 26, 2023 19:28:57 +0200, Kevin Kofler via rpmfusion-developers wrote: > Ankur Sinha via rpmfusion-developers wrote: > > I'm not really sure. How would one test this? (Things like Netflix seem > > to work fine here for me) > > Netflix works for you?! I would have expected it to work only if you > manually install the widevine DRM blob into the correct directory. I upgraded here, so maybe I've done this in the past and it's still there. I see this in my qutebrowser config: ``` ppapi-widevine-path=/opt/google/chrome/libwidevinecdm.so ``` > > > I do see that `-DFeature_webengine_proprietary_codecs` is set to ON in > > the spec: > > > > https://src.fedoraproject.org/rpms/qt6-qtwebengine/blob/rawhide/f/qt6-qtwebengine.spec#_441 > > Then the Fedora package is probably overreporting the supported codecs. > Though on the other hand, at least H.264 is mostly supported by the Fedora > FFmpeg if OpenH264 is available for dlopening (though I have not tested > whether that feature actually works in Chromium/QtWebEngine, it works only > if the application does not hardcode the FFmpeg codec name), so the list > might not be all that wrong even in Fedora. If there's a way to get the list or test out the supported codecs, I can do that and report back. > That said, Chromium also uses a bundled OpenH264 to encode H.264 for WebRTC. > If that is not patched to support dlopening, then we still need a qt6- > qtwebengine-freeworld built with the bundled OpenH264 enabled. We are not > allowed to ship OpenH264 directly in Fedora, only through that Cisco > arrangement. I have these packages: ``` $ rpm -qa \*264\* x264-libs-0.164-8.20220602gitbaee400f.fc39.x86_64 openh264-2.3.1-2.fc39.x86_64 mozilla-openh264-2.3.1-2.fc39.x86_64 gstreamer1-plugin-openh264-1.22.1-1.fc39.x86_64 ``` Again, not sure if stuff works as it should. I just haven't noticed any issues in normal usage yet. -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London signature.asc Description: PGP signature ___ rpmfusion-developers mailing list -- rpmfusion-developers@lists.rpmfusion.org To unsubscribe send an email to rpmfusion-developers-le...@lists.rpmfusion.org
