Jerky playback

Have a MythTV related problem? Ask for help from other MythTV users here.

Moderator: Forum Moderators

stinga
Junior
Posts: 15
Joined: Thu Apr 06, 2023 12:23 am
Australia

Jerky playback

Post by stinga »

G'day all,

I have a combo front/back end

Code: Select all

root@mythtv:/var/log/apt# mythbackend --version
Please attach all output as a file in bug reports.
MythTV Version : v31.0+fixes.20200911.c4aa648-0ubuntu0
MythTV Branch : fixes/31
Network Protocol : 91
Library API : 31.20200101-1
QT Version : 5.11.3
Options compiled in:
 linux profile use_hidesyms using_alsa using_oss using_pulse using_pulseoutput using_backend using_bindings_perl using_bindings_python using_bindings_php using_dvb using_firewire using_frontend using_hdhomerun using_vbox using_ceton using_hdpvr using_ivtv using_joystick_menu using_libcec using_libcrypto using_gnutls using_libdns_sd using_libfftw3 using_libxml2 using_lirc using_mheg using_opengl using_egl using_qtwebkit using_qtscript using_qtdbus using_taglib using_v4l2 using_v4l2prime using_x11 using_libbluray_external using_xrandr using_profiletype using_systemd_notify using_systemd_journal using_drm using_bindings_perl using_bindings_python using_bindings_php using_freetype2 using_mythtranscode using_opengl using_egl using_drm using_vaapi using_nvdec using_vdpau using_ffmpeg_threads using_mheg using_libass using_libxml2 using_libmp3lame

Code: Select all

root@mythtv:/var/log/apt# /usr/bin/mythfrontend.real --version
Please attach all output as a file in bug reports.
MythTV Version : v31.0+fixes.20200911.c4aa648-0ubuntu0
MythTV Branch : fixes/31
Network Protocol : 91
Library API : 31.20200101-1
QT Version : 5.11.3
Options compiled in:
 linux profile use_hidesyms using_alsa using_oss using_pulse using_pulseoutput using_backend using_bindings_perl using_bindings_python using_bindings_php using_dvb using_firewire using_frontend using_hdhomerun using_vbox using_ceton using_hdpvr using_ivtv using_joystick_menu using_libcec using_libcrypto using_gnutls using_libdns_sd using_libfftw3 using_libxml2 using_lirc using_mheg using_opengl using_egl using_qtwebkit using_qtscript using_qtdbus using_taglib using_v4l2 using_v4l2prime using_x11 using_libbluray_external using_xrandr using_profiletype using_systemd_notify using_systemd_journal using_drm using_bindings_perl using_bindings_python using_bindings_php using_freetype2 using_mythtranscode using_opengl using_egl using_drm using_vaapi using_nvdec using_vdpau using_ffmpeg_threads using_mheg using_libass using_libxml2 using_libmp3lame
At some point I have upgraded something and play back is no longer smooth.

It is not the recording, playing back on another PC using VLC and the recording is OK

I am not sure when this happened as I have been away for a bit.

I went through the apt logs and here is an edited version of updates.
I removed what was obviously unrelated but I may have removed evidence of something as well.

Code: Select all

Upgrade: base-files:amd64 (10.3+deb10u11, 10.3+deb10u12)
End-Date: 2022-03-28  10:27:26

Start-Date: 2022-03-28  10:28:46
Commandline: apt --only-upgrade install linux-libc-dev
Upgrade: linux-libc-dev:amd64 (4.19.146-1, 4.19.235-1)
End-Date: 2022-03-28  10:28:48

Start-Date: 2022-03-31  11:08:44
Commandline: apt install mythtv-backend
Install: libmyth:amd64 (2:31.0+fixes.20200911.c4aa648-0ubuntu0, automatic), libqt5printsupport5:amd64 (5.11.3+dfsg1-1+deb10u4, automatic), mythtv-common:amd64 (2:31.0+fixes.20200911.c4aa648-0ubuntu0, automatic), mythtv-dbg:amd64 (2:31.0+fixes.20200911.c4aa648-0ubuntu0, automatic), libqt5webkit5:amd64 (5.212.0~alpha2-21, automatic), zenity:amd64 (3.30.0-2, automatic), libwebkit2gtk-4.0-37:amd64 (2.34.6-1~deb10u1, automatic), mythtv-transcode-utils:amd64 (2:31.0+fixes.20200911.c4aa648-0ubuntu0, automatic), mythtv-backend:amd64 (2:31.0+fixes.20200911.c4aa648-0ubuntu0)
Upgrade: libjavascriptcoregtk-4.0-18:amd64 (2.32.3-1~deb10u1, 2.34.6-1~deb10u1)
End-Date: 2022-03-31  11:09:13

Start-Date: 2022-03-31  11:09:56
Commandline: apt install mythweb
Install: mythweb:amd64 (2:31.0+fixes.20200911.c4aa648-0ubuntu0)
End-Date: 2022-03-31  11:09:59

Start-Date: 2022-03-31  11:10:36
Commandline: apt install mythtv-frontend
Install: mythtv-frontend:amd64 (2:31.0+fixes.20200911.c4aa648-0ubuntu0)
End-Date: 2022-03-31  11:10:39

Start-Date: 2023-03-20  15:08:20
Commandline: apt --only-upgrade install libnvidia-cbl
Upgrade: libnvidia-cbl:amd64 (418.197.02-1, 418.226.00-3)
End-Date: 2023-03-20  15:08:26

Start-Date: 2023-03-23  07:05:02
Commandline: apt --only-upgrade install libnvidia-eglcore
Upgrade: libnvidia-eglcore:amd64 (418.197.02-1, 418.226.00-3)
End-Date: 2023-03-23  07:05:15

Start-Date: 2023-03-23  07:05:19
Commandline: apt --only-upgrade install libnvidia-glcore
Upgrade: libnvidia-glcore:amd64 (418.197.02-1, 418.226.00-3)
End-Date: 2023-03-23  07:05:22

Start-Date: 2023-03-23  07:05:35
Commandline: apt --only-upgrade install libnvidia-fatbinaryloader libnvidia-glvkspirv libnvidia-ptxjitcompiler1 libnvidia-rtcore
Upgrade: libnvidia-glvkspirv:amd64 (418.197.02-1, 418.226.00-3), libnvidia-ptxjitcompiler1:amd64 (418.197.02-1, 418.226.00-3), libnvidia-fatbinaryloader:amd64 (418.197.02-1, 418.226.00-3), libnvidia-rtcore:amd64 (418.197.02-1, 418.226.00-3)
End-Date: 2023-03-23  07:05:44



Start-Date: 2023-04-03  13:05:02
Commandline: apt --only-upgrade install fonts-opensymbol
Upgrade: fonts-opensymbol:amd64 (2:102.10+LibO6.1.5-3+deb10u7, 2:102.10+LibO6.1.5-3+deb10u8)
End-Date: 2023-04-03  13:05:15

Start-Date: 2023-04-03  13:05:53
Commandline: apt --only-upgrade install libnss-systemd
Upgrade: libsystemd0:amd64 (241-7~deb10u8, 241-7~deb10u9), libsystemd-dev:amd64 (241-7~deb10u8, 241-7~deb10u9), libpam-systemd:amd64 (241-7~deb10u8, 241-7~deb10u9), systemd:amd64 (241-7~deb10u8, 241-7~deb10u9), libnss-systemd:amd64 (241-7~deb10u8, 241-7~deb10u9)
End-Date: 2023-04-03  13:06:10

Start-Date: 2023-04-03  13:06:42
Commandline: apt --only-upgrade install libudev-dev
Upgrade: udev:amd64 (241-7~deb10u8, 241-7~deb10u9), libudev1:amd64 (241-7~deb10u8, 241-7~deb10u9), libudev-dev:amd64 (241-7~deb10u8, 241-7~deb10u9)
End-Date: 2023-04-03  13:07:20

Start-Date: 2023-04-03  13:08:01
Commandline: apt --only-upgrade install systemd-sysv
Upgrade: systemd-sysv:amd64 (241-7~deb10u8, 241-7~deb10u9)
End-Date: 2023-04-03  13:08:04

Start-Date: 2023-04-04  08:37:29
Commandline: apt --only-upgrade install linux-compiler-gcc-8-x86
Upgrade: linux-compiler-gcc-8-x86:amd64 (4.19.208-1, 4.19.269-1)
End-Date: 2023-04-04  08:37:31

Start-Date: 2023-04-06  07:09:51
Commandline: apt --only-upgrade install ghostscript libgs9-common google-chrome-stable libgs9
Upgrade: libgs9:amd64 (9.27~dfsg-2+deb10u6, 9.27~dfsg-2+deb10u7), google-chrome-stable:amd64 (111.0.5563.146-1, 112.0.5615.49-1), ghostscript:amd64 (9.27~dfsg-2+deb10u6, 9.27~dfsg-2+deb10u7), libgs9-common:amd64 (9.27~dfsg-2+deb10u6, 9.27~dfsg-2+deb10u7)
End-Date: 2023-04-06  07:10:43

Start-Date: 2023-04-12  07:24:23
Commandline: apt --only-upgrade install udisks2 libudisks2-0 xserver-common xserver-xorg-core xserver-xorg-legacy
Upgrade: xserver-common:amd64 (2:1.20.4-1+deb10u4, 2:1.20.4-1+deb10u9), xserver-xorg-core:amd64 (2:1.20.4-1+deb10u1, 2:1.20.4-1+deb10u9), xserver-xorg-legacy:amd64 (2:1.20.4-1+deb10u1, 2:1.20.4-1+deb10u9), udisks2:amd64 (2.8.1-4, 2.8.1-4+deb10u2), libudisks2-0:amd64 (2.8.1-4, 2.8.1-4+deb10u2)
End-Date: 2023-04-12  07:24:53

Start-Date: 2023-04-20  12:29:54
Commandline: apt --only-upgrade install firefox-esr google-chrome-stable libprotobuf-lite17
Upgrade: google-chrome-stable:amd64 (112.0.5615.49-1, 112.0.5615.165-1), libprotobuf-lite17:amd64 (3.6.1.3-2, 3.6.1.3-2+deb10u1), firefox-esr:amd64 (102.9.0esr-1~deb10u1, 102.10.0esr-1~deb10u1)
End-Date: 2023-04-20  12:30:39

Code: Select all

root@mythtv:/var/log/apt# dpkg -l|grep nvid
rc  glx-alternative-nvidia                        1.0.0                                   amd64        allows the selection of NVIDIA as GLX provider
ii  libnvidia-cbl:amd64                           418.226.00-3                            amd64        NVIDIA binary Vulkan ray tracing (cbl) library
ii  libnvidia-eglcore:amd64                       418.226.00-3                            amd64        NVIDIA binary EGL core libraries
ii  libnvidia-fatbinaryloader:amd64               418.226.00-3                            amd64        NVIDIA FAT binary loader
ii  libnvidia-glcore:amd64                        418.226.00-3                            amd64        NVIDIA binary OpenGL/GLX core libraries
ii  libnvidia-glvkspirv:amd64                     418.226.00-3                            amd64        NVIDIA binary Vulkan Spir-V compiler library
ii  libnvidia-ptxjitcompiler1:amd64               418.226.00-3                            amd64        NVIDIA PTX JIT Compiler library
ii  libnvidia-rtcore:amd64                        418.226.00-3                            amd64        NVIDIA binary Vulkan ray tracing (rtcore) library
rc  nvidia-alternative                            418.152.00-1                            amd64        allows the selection of NVIDIA as GLX provider
rc  nvidia-installer-cleanup                      20151021+9                              amd64        cleanup after driver installation with the nvidia-installer
rc  nvidia-kernel-common                          20151021+9                              amd64        NVIDIA binary kernel module support files
rc  nvidia-kernel-support                         418.152.00-1                            amd64        NVIDIA binary kernel module support files
rc  nvidia-legacy-check                           418.152.00-1                            amd64        check for NVIDIA GPUs requiring a legacy driver
rc  nvidia-persistenced                           418.56-1                                amd64        daemon to maintain persistent software state in the NVIDIA driver
rc  nvidia-support                                20151021+9                              amd64        NVIDIA binary graphics driver support files
rc  xserver-xorg-video-nvidia
It is difficult to explain what it looks like but it almost looks like it not every frame is playing it is almost watchable! :)
Audio is fine.
I don't see anything of interest in the logs.
I have rebooted.

Code: Select all

root@mythtv:/var/log/apt# cat /sys/module/nvidia/version
390.138
root@mythtv:/var/log/apt# cat /proc/driver/nvidia/version
NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.138  Thu May 14 01:01:53 PDT 2020
GCC version:  gcc version 8.3.0 (Debian 8.3.0-6)
[/code]

Code: Select all

01:00.0 VGA compatible controller: NVIDIA Corporation GP107 [GeForce GTX 1050] (rev a1) (prog-if 00 [VGA controller])
	Subsystem: ASUSTeK Computer Inc. GP107 [GeForce GTX 1050]
	Flags: bus master, fast devsel, latency 0, IRQ 127
	Memory at 52000000 (32-bit, non-prefetchable) [size=16M]
	Memory at 40000000 (64-bit, prefetchable) [size=256M]
	Memory at 50000000 (64-bit, prefetchable) [size=32M]
	I/O ports at 4000 [size=128]
	[virtual] Expansion ROM at 000c0000 [disabled] [size=128K]
	Capabilities: [60] Power Management version 3
	Capabilities: [68] MSI: Enable+ Count=1/1 Maskable- 64bit+
	Capabilities: [78] Express Legacy Endpoint, MSI 00
	Capabilities: [100] Virtual Channel
	Capabilities: [250] Latency Tolerance Reporting
	Capabilities: [128] Power Budgeting <?>
	Capabilities: [420] Advanced Error Reporting
	Capabilities: [600] Vendor Specific Information: ID=0001 Rev=1 Len=024 <?>
	Capabilities: [900] #19
	Kernel driver in use: nvidia
	Kernel modules: nouveau, nvidia_drm, nvidia
What other info can I provide and what else can I look at?
blm-ubunet
Senior
Posts: 265
Joined: Sun Jun 15, 2014 1:08 am
Cambodia

Re: Jerky playback

Post by blm-ubunet »

Weird things in your logs..
Where does nvidia-418 come from?
Because 390 is reported in other places.

Your GTX1050 reports as supported by releases 390 490 525.
kernel logs:
sudo dmesg | grep -i 'nvrm\|nvidia\|nouv'
or Xorg logs:
/var/log/Xorg.0.log
stinga
Junior
Posts: 15
Joined: Thu Apr 06, 2023 12:23 am
Australia

Re: Jerky playback

Post by stinga »

Code: Select all

root@mythtv:~# dmesg | grep -i 'nvrm\|nvidia\|nouv'
[   19.176060] input: HDA NVidia HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input35
[   19.176173] input: HDA NVidia HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input36
[   19.176272] input: HDA NVidia HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input37
[   19.271540] nvidia: module license 'NVIDIA' taints kernel.
[   19.305071] nvidia-nvlink: Nvlink Core is being initialized, major device number 240
[   19.305698] nvidia 0000:01:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=io+mem
[   19.305851] NVRM: loading NVIDIA UNIX x86_64 Kernel Module  390.138  Thu May 14 01:01:53 PDT 2020 (using threaded interrupts)
[   19.673913] nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms  390.138  Thu May 14 04:02:47 PDT 2020
[   19.888016] [drm] [nvidia-drm] [GPU ID 0x00000100] Loading driver
[   19.888021] [drm] Initialized nvidia-drm 0.0.0 20160202 for 0000:01:00.0 on minor 0
[   26.319054] audit: type=1400 audit(1682351195.507:9): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe" pid=555 comm="apparmor_parser"
[   26.319061] audit: type=1400 audit(1682351195.507:10): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe//kmod" pid=555 comm="apparmor_parser"
[  172.858301] nvidia-uvm: Loaded the UVM driver in 8 mode, major device number 239
root@mythtv:~# 
I did notice the version difference and wrote it off as internal numbering....
There is no strange entries in /etc/apt files
stinga
Junior
Posts: 15
Joined: Thu Apr 06, 2023 12:23 am
Australia

Re: Jerky playback

Post by stinga »

Ah...

Code: Select all

root@mythtv:~# locate nvid|grep deb$
/var/cache/apt/archives/libnvidia-cbl_418.197.02-1_amd64.deb
/var/cache/apt/archives/libnvidia-cbl_418.211.00-1_amd64.deb
/var/cache/apt/archives/libnvidia-cbl_418.226.00-3_amd64.deb
/var/cache/apt/archives/libnvidia-eglcore_418.197.02-1_amd64.deb
/var/cache/apt/archives/libnvidia-eglcore_418.211.00-1_amd64.deb
/var/cache/apt/archives/libnvidia-eglcore_418.226.00-3_amd64.deb
/var/cache/apt/archives/libnvidia-fatbinaryloader_418.197.02-1_amd64.deb
/var/cache/apt/archives/libnvidia-fatbinaryloader_418.211.00-1_amd64.deb
/var/cache/apt/archives/libnvidia-fatbinaryloader_418.226.00-3_amd64.deb
/var/cache/apt/archives/libnvidia-glcore_418.197.02-1_amd64.deb
/var/cache/apt/archives/libnvidia-glcore_418.211.00-1_amd64.deb
/var/cache/apt/archives/libnvidia-glcore_418.226.00-3_amd64.deb
/var/cache/apt/archives/libnvidia-glvkspirv_418.197.02-1_amd64.deb
/var/cache/apt/archives/libnvidia-glvkspirv_418.211.00-1_amd64.deb
/var/cache/apt/archives/libnvidia-glvkspirv_418.226.00-3_amd64.deb
/var/cache/apt/archives/libnvidia-ptxjitcompiler1_418.197.02-1_amd64.deb
/var/cache/apt/archives/libnvidia-ptxjitcompiler1_418.211.00-1_amd64.deb
/var/cache/apt/archives/libnvidia-ptxjitcompiler1_418.226.00-3_amd64.deb
/var/cache/apt/archives/libnvidia-rtcore_418.197.02-1_amd64.deb
/var/cache/apt/archives/libnvidia-rtcore_418.211.00-1_amd64.deb
/var/cache/apt/archives/libnvidia-rtcore_418.226.00-3_amd64.deb
But I don't know what that means.....
white_haired_uncle
Senior
Posts: 244
Joined: Thu Feb 23, 2023 8:55 pm
Location: Safe outside my gilded cage
United States of America

Re: Jerky playback

Post by white_haired_uncle »

When modules loaded don't seem to match modules installed, the first place I look is /lib/modules and `uname -r`. Then I move on to initrd, though I don't think nvidia loads early enough for this to matter here.
blm-ubunet
Senior
Posts: 265
Joined: Sun Jun 15, 2014 1:08 am
Cambodia

Re: Jerky playback

Post by blm-ubunet »

Did you ever install video driver using the nvidia direct download & installer?
Almost no one needs to do that for last 10+ years.

I would install the latest nvidia package that's compatible with your kernel version.
May need to perform some package or ppa purging first.

Xorg logs ?
stinga
Junior
Posts: 15
Joined: Thu Apr 06, 2023 12:23 am
Australia

Re: Jerky playback

Post by stinga »

This version was built 2-3 years ago.
I usually doco stuff like that and my notes don't show that I installed a driver, does not mean I didn't.

Can I just down load latest supported driver and install or do I need to uninstall stuff first?
blm-ubunet
Senior
Posts: 265
Joined: Sun Jun 15, 2014 1:08 am
Cambodia

Re: Jerky playback

Post by blm-ubunet »

I would just install nvidia-525.
Nvidia's documentation & installation processes are 2nd to none.
Just make sure you have dkms & linux headers generic package installed.

The install script will compile a shim & rebuild initramfs image.

I would avoid nvidia-470 like the plague (this works real bad with 22.10 23.04 & Kepler GPU).

But your playback judder may just due to changes in MythTV video playback setup/configuration 31-->32.
You may have to reconfigure VDPAU and/or try NVDEC.

Latest MythTV does not utilize any VDPAU or NVDEC post processing functions, so PQ can be less.
stinga
Junior
Posts: 15
Joined: Thu Apr 06, 2023 12:23 am
Australia

Re: Jerky playback

Post by stinga »

@blm-ubunet
Thanks for that info.

It has been a while since I looked at VDPAU, usually it has just worked!
Do you ave further info on the changes I may need to make, my google fu has failed me....

What is PQ?

Code: Select all

MariaDB [mythconverg]> select * from settings where value like '%playb%file';
+-----------------------------+--------------------+----------+
| value                       | data               | hostname |
+-----------------------------+--------------------+----------+
| DefaultVideoPlaybackProfile | VDPAU High Quality | mythtv   |
+-----------------------------+--------------------+----------+
blm-ubunet
Senior
Posts: 265
Joined: Sun Jun 15, 2014 1:08 am
Cambodia

Re: Jerky playback

Post by blm-ubunet »

I would run mythfrontend with playback logging or from terminal with logging to be able to check for what is actually right or wrong.
Maybe VDPAU is not functional.

I'm still running an old version from git.. but I believe you just need to enter the video playback screens, make a note of your settings & then delete the VDPAU profile & then recreate with defaults.

GTX1050 should have no problem with VDPAU HQ (temporal spatial deinterlacing).

All post processing filters were removed so there is no extra GPU load..
VDPAU & NVDEC do not have any post processing support in MythTV.
stinga
Junior
Posts: 15
Joined: Thu Apr 06, 2023 12:23 am
Australia

Re: Jerky playback

Post by stinga »

I believe I have fixed the issue...
I installed the the divers... 525

One thing I have noticed, is when the video is panning up/down/left/right fast
(Or it maybe when there is a large amount of pixel change)

I get a line across the midle of the screen, not the exact middle, but around the middle.
Its not a drawn line it like the top and the bottom don't quite mesh.

It has done this for quite a while and have sort of got used to it but would be good to get rid of it if possible.
white_haired_uncle
Senior
Posts: 244
Joined: Thu Feb 23, 2023 8:55 pm
Location: Safe outside my gilded cage
United States of America

Re: Jerky playback

Post by white_haired_uncle »

It sounds like you're referring to "screen tearing". Lots of info out there if you know the magic search word.

BTW, have you tried the nouveau driver lately? I don't use (need) any sort of HW acceleration and whatnot, and I don't have any playback issues even with a 15 year old processor chosen not for speed but lowest power usage. I remember many years ago having some issues and high CPU load with HD, but then I set up an option in the profile so that if the video was 1920x1080 (same as my TV native resolution) not to do any deinterlacing and just let the TV handle it.
gedakc
Junior
Posts: 96
Joined: Fri Jul 18, 2014 1:28 am
Canada

Re: Jerky playback

Post by gedakc »

white_haired_uncle wrote:
Fri May 05, 2023 5:41 am
... but then I set up an option in the profile so that if the video was 1920x1080 (same as my TV native resolution) not to do any deinterlacing and just let the TV handle it.
If possible can you please share how you set up the option to let the TV handle the deinterlacing of MythTV recordings?
white_haired_uncle
Senior
Posts: 244
Joined: Thu Feb 23, 2023 8:55 pm
Location: Safe outside my gilded cage
United States of America

Re: Jerky playback

Post by white_haired_uncle »

gedakc wrote:
Fri May 05, 2023 3:11 pm
white_haired_uncle wrote:
Fri May 05, 2023 5:41 am
... but then I set up an option in the profile so that if the video was 1920x1080 (same as my TV native resolution) not to do any deinterlacing and just let the TV handle it.
If possible can you please share how you set up the option to let the TV handle the deinterlacing of MythTV recordings?
Frontend > Settings > TV Settings > Playback > Current Video Profile

From there I have two entries. The first has Width Range >=1920, and Height Range >=1080 (maybe this should be =, not >=, but I haven't encountered video resolutions larger than the TV yet). In this one both Deinterlacer Quality are set to None.

The second entry has nothing for Width/Height, so it matches anything else. Here I include my deinterlacing settings for other resolutions.

My understanding is that this setup sends 1080i recordings straight to the TV to use the built in deinterlacing, and handles 480i with the PC. There's been changes to playback since I set this up, so I don't know how accurate this is, but it was necessary years ago and playback still works fine today so I haven't messed with it.
blm-ubunet
Senior
Posts: 265
Joined: Sun Jun 15, 2014 1:08 am
Cambodia

Re: Jerky playback

Post by blm-ubunet »

What Desktop session / manager are you running?

The linux graphics stack is a total mess.
Nvidia always had the best documentation & video playback PQ but now the proprietary driver does not seem to fit well anywhere.

To guarantee no tearing with Nvidia VDPAU it must be using overlay & NOT blitter.
The nvidia driver settings has an OSD option to indicate that.

You get blitter presentation mode VDPAU if:
- Composite managers that does not correctly support un-redirected full screen video
- applications that do not know how to use recent full screen hinting API? (MythTV?)
- composite manager devs do not want/care if works with Nvidia driver (mate - marco - compton)

There's a lot of hate out there for NVidia driver..

circa 2019:
SettingFullCompositionPipeline on seems to cause frame jitter in mpv & MythTV.
gsettings set org.mate.Marco.general compositing-manager false (this wrecks Desktop UI/UX)

But others found soln was:
enabled (mate compton) GPU compositor , disabled fullcompostingpipeline and just leaved triplebuffer enabled

None of the above applies if using nouveau driver.
Good luck finding any guidance on using VDPAU or VAAPI with it.

The GTX1050ti can decode deinterlace & post process (HQ scale to 4K, sharpen. denoise) typical HD video without the fan spinning up..
I recall it hitting 600fps VDPAU decode H264 & NVDEC is faster & can do 2 streams at same time.
It has no problem playing 120Hz HD & scaling to 4K
No problem with any 4K video test tracks I scraped up Samsung demos, Jellyfish (inc. local broadcasts), some of these are interlaced.
Post Reply