Dear Thomas and Alf, Thank you for confirming that this fix for DVB support works as it should.
Thomas, if you have a few minutes of free time, would you please review the rest of this email, and consider verifying whether or not mpv_0.35.1-4 introduces a regression in smplayer? I hypothesise that mpv_0.35.1-3 works no better, but we need to be sure that mpv_0.35.1-4 doesn't cause any harm...if it does then smplayer will need a fix too (maybe just a rebuild). Alf <alf.debian...@gmx.de> writes: > (+) Video --vid=1 (h264 1280x720 50.000fps) Ok, h264. > (+) Audio --aid=1 (mp2 2ch 48000Hz) > File tags: > Title: arte HD(Unitymedia) > [ffmpeg/video] h264: co located POCs unavailable Here is a thread about what this message means: https://www.mail-archive.com/ffmpeg-devel@ffmpeg.org/msg80351.html > Using hardware decoding (vaapi). > AO: [pipewire] 48000Hz stereo 2ch s16p > VO: [gpu] 1280x720 vaapi[nv12] "nv12" is a colour space and pixel format thing. Yes, I had to look this up, because I've never seen "nv12" before. https://wiki.videolan.org/YUV > AV: 00:11:15 / 00:11:19 (99%) A-V: 0.000 Cache: 4.1s/5MB > > Hardware here is a quite old "Sundtek TV-Stick" from 2017 with their driver. > I am watching DVB-C television with it and the channels.conf is unchanged. > Thank you for noting the hardware you tested with, as well as the type of network that you're using to receive DVB. > THANKS for your fast response and the fix! > You're welcome :) > What now does not work: "smplayer". It only plays sound but no video. > SMplayer-Protocol continously spits huge amounts of these messagen: > [12:23:52:227] MPVProcess::parseLine: "[vo/vaapi] vaPutSurface() failed > (invalid parameter)" > When did this work previously? Is this a regression for non-DVB sources (like playing normal files)? "[vo/vaapi] vaPutSurface() failed (invalid parameter)" is a vaapi error emitted by mpv. I suspect that your smplayer config is different than your mpv config, and that the smplayer config is setting up vaapi acceleration and output in a wrong way. You can try running smplayer and mpv verbosely, and then comparing the output, as well as comparing their configuration. The output driver configuration should be found here: ~/.config/mpv/mpv.conf to ~/.config/smplayer2/smplayer2.ini If it's not a configuration issue, then maybe smplayer works fine with all yuv420p sources, and that it's only nv12 sources that pose a problem? It may also be that your your vaapi hardware can't handle nv12, and mpv (directly) can detect this and uses ffmpeg to convert the stream, whereas this autodetection doesn't work with smplayer+mpv. > But that's not an issue as long as "mpv" does the job. > Wonderful :) It's also important that the new mpv version doesn't cause a regression in smplayer, especially something like breaking playback of typical yuv420p files. The release team will want to know that we're not robbing Peter to pay Paul. Cheers, Nicholas
signature.asc
Description: PGP signature
