Bug#851170: libqt5webengine5: h.264 video does not seem to work
Awesome, I can't wait to try it! On 01/15, Sandro Knauß wrote: > Control: tags -1 +pending > Hey, > > I also had a look and came to same comclusion than you, that > use_proprietary_codecs only activates the interface. I gave it alsoready a > try > on amd64 and it built successfully. I will activate it with the next upload. > > Best Regards, > > sandro > > > -- > Am Donnerstag, 12. Januar 2017, 17:56:32 CET schrieb Robert Cross: > > (sorry for the double mail Sandro, I am very bad at email!!!) > > > > I'm trying to figure out what exactly use_system_ffmpeg and > > use_proprietary_codecs does. > > > > It seems to me that use_system_ffmpeg will do exactly as it sounds and will > > use system libav* libraries. > > > > I went and downloaded webengine 5.7 source: > > git clone https://code.qt.io/qt/qtwebengine.git -b 5.7 > > > > and did some digging in there. > > > > In src/core/renderer/content_renderer_client_qt.cpp I found: > > > > #if defined(USE_PROPRIETARY_CODECS) > > info.supported_init_data_types |= media::kInitDataTypeMaskCenc; > > info.supported_codecs |= media::EME_CODEC_MP4_ALL; > > #endif // defined(USE_PROPRIETARY_CODECS) > > > > After some searching around, I found that media::EME_CODEC_MP4_ALL is > > defined in chromium, see: > > https://chromium.googlesource.com/chromium/src.git/+/lkcr/media/base/eme_con > > stants.h > > > > So it looks like to me with my non-expert eyes, that use_proprietary_codecs > > is just setting the bits that the underlying browser engine reports that > > certain codecs are available to use. > > > > It seems that if you have use_proprietary_codecs and use_system_ffmpeg both > > on, it will still delegate the video to the system libraries. > > > > I could be wrong, these are just the results of some preliminary digging! > > > > On 01/12, Sandro Knauß wrote: > > > Hey, > > > > > > > please be gentle as this is my first bug report :) > > > > > > feel welcome! I hope your first experience with Debian bug reporting is a > > > good one. > > > > > > > I'm excited that Qt WebEngine is being packaged, so I could use it with > > > > qutebrowser. > > > > > > that is great and we need packages using QtWebEngine to get an idea if we > > > packaged it correctly. > > > > > > > It seems to work beautifully, except that H.264 video is not working. > > > > I've talked to the developer of qutebrowser and he said that qtwebengine > > > > might not be configured to use proprietary codecs (see: > > > > http://doc.qt.io/qt-5/qtwebengine-features.html#audio-and-video-codecs ) > > > > > > We were in a rush to get QtWebEngine ready for Debian, so we couldn't > > > evaluate all the potentials of QtWebEngine. But on Debian we can't simply > > > include proprietary codecs, because that would mean, that QtWebEngine > > > will move from main to non-free and all software using it would endup in > > > contrib. And I think must use cases are not include sing proprietary > > > codecs. > > > > > > The solution would be, that we would able to use ffmpeg/libh264 from the > > > system, if available, like other media player do this. And we actually > > > push > > > this information into the build. So in theory it should be picked up and > > > use the system ffmpeg libs: > > > qmake WEBENGINE_CONFIG+="use_system_ffmpeg=1" > > > > > > Did you try to just install the necessary libs? > > > > > > Under [0] you find the complete build script for Debian. > > > > > > >I know that multimedia codecs can be very hairy things in general, but > > > >I'm > > > > > > hoping that since H.264 is enabled in chromium, that the same can be done > > > for Qt WebEngine. > > > > > > I hope so too, but the build of QtWebEngine is another layer on top of the > > > complex build of the internal chromium. > > > > > > Any help how to push QtWebEngine to use system h264 is very welcomed! > > > > > > Best Regards, > > > > > > sandro > > > > > > [0] > > > https://anonscm.debian.org/git/pkg-kde/qt/qtwebengine.git/tree/debian/ > > > rules >
Bug#851170: libqt5webengine5: h.264 video does not seem to work
Control: tags -1 +pending Hey, I also had a look and came to same comclusion than you, that use_proprietary_codecs only activates the interface. I gave it alsoready a try on amd64 and it built successfully. I will activate it with the next upload. Best Regards, sandro -- Am Donnerstag, 12. Januar 2017, 17:56:32 CET schrieb Robert Cross: > (sorry for the double mail Sandro, I am very bad at email!!!) > > I'm trying to figure out what exactly use_system_ffmpeg and > use_proprietary_codecs does. > > It seems to me that use_system_ffmpeg will do exactly as it sounds and will > use system libav* libraries. > > I went and downloaded webengine 5.7 source: > git clone https://code.qt.io/qt/qtwebengine.git -b 5.7 > > and did some digging in there. > > In src/core/renderer/content_renderer_client_qt.cpp I found: > > #if defined(USE_PROPRIETARY_CODECS) > info.supported_init_data_types |= media::kInitDataTypeMaskCenc; > info.supported_codecs |= media::EME_CODEC_MP4_ALL; > #endif // defined(USE_PROPRIETARY_CODECS) > > After some searching around, I found that media::EME_CODEC_MP4_ALL is > defined in chromium, see: > https://chromium.googlesource.com/chromium/src.git/+/lkcr/media/base/eme_con > stants.h > > So it looks like to me with my non-expert eyes, that use_proprietary_codecs > is just setting the bits that the underlying browser engine reports that > certain codecs are available to use. > > It seems that if you have use_proprietary_codecs and use_system_ffmpeg both > on, it will still delegate the video to the system libraries. > > I could be wrong, these are just the results of some preliminary digging! > > On 01/12, Sandro Knauß wrote: > > Hey, > > > > > please be gentle as this is my first bug report :) > > > > feel welcome! I hope your first experience with Debian bug reporting is a > > good one. > > > > > I'm excited that Qt WebEngine is being packaged, so I could use it with > > > qutebrowser. > > > > that is great and we need packages using QtWebEngine to get an idea if we > > packaged it correctly. > > > > > It seems to work beautifully, except that H.264 video is not working. > > > I've talked to the developer of qutebrowser and he said that qtwebengine > > > might not be configured to use proprietary codecs (see: > > > http://doc.qt.io/qt-5/qtwebengine-features.html#audio-and-video-codecs ) > > > > We were in a rush to get QtWebEngine ready for Debian, so we couldn't > > evaluate all the potentials of QtWebEngine. But on Debian we can't simply > > include proprietary codecs, because that would mean, that QtWebEngine > > will move from main to non-free and all software using it would endup in > > contrib. And I think must use cases are not include sing proprietary > > codecs. > > > > The solution would be, that we would able to use ffmpeg/libh264 from the > > system, if available, like other media player do this. And we actually > > push > > this information into the build. So in theory it should be picked up and > > use the system ffmpeg libs: > > qmake WEBENGINE_CONFIG+="use_system_ffmpeg=1" > > > > Did you try to just install the necessary libs? > > > > Under [0] you find the complete build script for Debian. > > > > >I know that multimedia codecs can be very hairy things in general, but > > >I'm > > > > hoping that since H.264 is enabled in chromium, that the same can be done > > for Qt WebEngine. > > > > I hope so too, but the build of QtWebEngine is another layer on top of the > > complex build of the internal chromium. > > > > Any help how to push QtWebEngine to use system h264 is very welcomed! > > > > Best Regards, > > > > sandro > > > > [0] > > https://anonscm.debian.org/git/pkg-kde/qt/qtwebengine.git/tree/debian/ > > rules signature.asc Description: This is a digitally signed message part.
Bug#851170: libqt5webengine5: h.264 video does not seem to work
(sorry for the double mail Sandro, I am very bad at email!!!) I'm trying to figure out what exactly use_system_ffmpeg and use_proprietary_codecs does. It seems to me that use_system_ffmpeg will do exactly as it sounds and will use system libav* libraries. I went and downloaded webengine 5.7 source: git clone https://code.qt.io/qt/qtwebengine.git -b 5.7 and did some digging in there. In src/core/renderer/content_renderer_client_qt.cpp I found: #if defined(USE_PROPRIETARY_CODECS) info.supported_init_data_types |= media::kInitDataTypeMaskCenc; info.supported_codecs |= media::EME_CODEC_MP4_ALL; #endif // defined(USE_PROPRIETARY_CODECS) After some searching around, I found that media::EME_CODEC_MP4_ALL is defined in chromium, see: https://chromium.googlesource.com/chromium/src.git/+/lkcr/media/base/eme_constants.h So it looks like to me with my non-expert eyes, that use_proprietary_codecs is just setting the bits that the underlying browser engine reports that certain codecs are available to use. It seems that if you have use_proprietary_codecs and use_system_ffmpeg both on, it will still delegate the video to the system libraries. I could be wrong, these are just the results of some preliminary digging! On 01/12, Sandro Knauß wrote: > Hey, > > > please be gentle as this is my first bug report :) > > feel welcome! I hope your first experience with Debian bug reporting is a > good > one. > > > I'm excited that Qt WebEngine is being packaged, so I could use it with > > qutebrowser. > > that is great and we need packages using QtWebEngine to get an idea if we > packaged it correctly. > > > It seems to work beautifully, except that H.264 video is not working. > > I've talked to the developer of qutebrowser and he said that qtwebengine > > might not be configured to use proprietary codecs (see: > > http://doc.qt.io/qt-5/qtwebengine-features.html#audio-and-video-codecs ) > > We were in a rush to get QtWebEngine ready for Debian, so we couldn't > evaluate > all the potentials of QtWebEngine. But on Debian we can't simply include > proprietary codecs, because that would mean, that QtWebEngine will move from > main to non-free and all software using it would endup in contrib. And I > think > must use cases are not include sing proprietary codecs. > > The solution would be, that we would able to use ffmpeg/libh264 from the > system, if available, like other media player do this. And we actually push > this information into the build. So in theory it should be picked up and use > the system ffmpeg libs: > qmake WEBENGINE_CONFIG+="use_system_ffmpeg=1" > > Did you try to just install the necessary libs? > > Under [0] you find the complete build script for Debian. > > >I know that multimedia codecs can be very hairy things in general, but I'm > hoping that since H.264 is enabled in chromium, that the same can be done for > Qt WebEngine. > > I hope so too, but the build of QtWebEngine is another layer on top of the > complex build of the internal chromium. > > Any help how to push QtWebEngine to use system h264 is very welcomed! > > Best Regards, > > sandro > > [0] https://anonscm.debian.org/git/pkg-kde/qt/qtwebengine.git/tree/debian/ > rules -- Robert Cross - OpenPGP key ID: AA332044 Uphold your right to privacy, encrypt your email! https://emailselfdefense.fsf.org/
Bug#851170: libqt5webengine5: h.264 video does not seem to work
Hey, > please be gentle as this is my first bug report :) feel welcome! I hope your first experience with Debian bug reporting is a good one. > I'm excited that Qt WebEngine is being packaged, so I could use it with > qutebrowser. that is great and we need packages using QtWebEngine to get an idea if we packaged it correctly. > It seems to work beautifully, except that H.264 video is not working. > I've talked to the developer of qutebrowser and he said that qtwebengine > might not be configured to use proprietary codecs (see: > http://doc.qt.io/qt-5/qtwebengine-features.html#audio-and-video-codecs ) We were in a rush to get QtWebEngine ready for Debian, so we couldn't evaluate all the potentials of QtWebEngine. But on Debian we can't simply include proprietary codecs, because that would mean, that QtWebEngine will move from main to non-free and all software using it would endup in contrib. And I think must use cases are not include sing proprietary codecs. The solution would be, that we would able to use ffmpeg/libh264 from the system, if available, like other media player do this. And we actually push this information into the build. So in theory it should be picked up and use the system ffmpeg libs: qmake WEBENGINE_CONFIG+="use_system_ffmpeg=1" Did you try to just install the necessary libs? Under [0] you find the complete build script for Debian. >I know that multimedia codecs can be very hairy things in general, but I'm hoping that since H.264 is enabled in chromium, that the same can be done for Qt WebEngine. I hope so too, but the build of QtWebEngine is another layer on top of the complex build of the internal chromium. Any help how to push QtWebEngine to use system h264 is very welcomed! Best Regards, sandro [0] https://anonscm.debian.org/git/pkg-kde/qt/qtwebengine.git/tree/debian/ rules signature.asc Description: This is a digitally signed message part.
Bug#851170: libqt5webengine5: h.264 video does not seem to work
Package: libqt5webengine5 Version: 5.7.1+dfsg-4 Severity: normal Hello, please be gentle as this is my first bug report :) I'm excited that Qt WebEngine is being packaged, so I could use it with qutebrowser. It seems to work beautifully, except that H.264 video is not working. I've talked to the developer of qutebrowser and he said that qtwebengine might not be configured to use proprietary codecs (see: http://doc.qt.io/qt-5/qtwebengine-features.html#audio-and-video-codecs ) I know that multimedia codecs can be very hairy things in general, but I'm hoping that since H.264 is enabled in chromium, that the same can be done for Qt WebEngine. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (650, 'testing'), (1, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.8.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libqt5webengine5 depends on: ii libc6 2.24-8 ii libqt5core5a [qtbase-abi-5-7-1] 5.7.1~20161021+dfsg-6 ii libqt5gui55.7.1~20161021+dfsg-6 ii libqt5qml5 [qtdeclarative-abi-5-7-0] 5.7.1-1 ii libqt5quick5 5.7.1-1 ii libqt5webchannel5 5.7.1-1 ii libqt5webengine-data 5.7.1+dfsg-4 ii libqt5webenginecore5 5.7.1+dfsg-4 ii libstdc++66.2.1-5 libqt5webengine5 recommends no packages. libqt5webengine5 suggests no packages. -- no debconf information
