+- Kodi Community Forum (https://forum.kodi.tv)
+-- Forum: Support (https://forum.kodi.tv/forumdisplay.php?fid=33)
+--- Forum: PVR & Live TV Support (https://forum.kodi.tv/forumdisplay.php?fid=167)
+---- Forum: MythTV (https://forum.kodi.tv/forumdisplay.php?fid=170)
+---- Thread: Solved Myth TV playback top half of screen only LOG INCLUDED (/showthread.php?tid=351213)
Myth TV playback top half of screen only LOG INCLUDED - jmgibson1981 - 2020-01-24
Last night when my wife's uncle came home he tried to watch TV in the guest room. The bottom half of the screen is washed out real bad if it has any color at all. This was working just fine 2 days ago so something changed but I'm unsure of what. I did do updates yesterday I believe. Everything else is fine, local media from our server and music playback is all good. Just MythTV playback has the issue so I can rule out the hdmi port, the cable, or the tv.
https://paste.ubuntu.com/p/zMNCGfnQgG/3
What's interesting is that this is an Ubuntu 18.04 machine, which is identical to the living room yet the living room doesn't have this problem. I'm thinking a setting or something.
This paste is the updates I did just the other day.
https://paste.ubuntu.com/p/P6Ckt4Kz7f/
*EDIT* just for good measure I dumped the user folder and started fresh. same problem exists.
*EDIT* Mythtv is not the problem. Turns out it was definitely one of those updates. I didn't track down which. For 18.04 I've had a ton of trouble with my pxe image. I've changed it to use my 16.04 image and it works just fine.
RE: [SOLVED] Myth TV playback top half of screen only LOG INCLUDED - flogfloof - 2020-03-17
I've got the same problem, but am using AMDGPU only, so it's at least not nouveau.
RE: Myth TV playback top half of screen only LOG INCLUDED - srdjan - 2020-03-31
With all due respect, why is this "solved"? The problem exists. I am on Kodi 18 with add on v5.10.5, which is the latest official, AMD radeon stock diver, broken in both ubuntu 18.04 and 19.10
RE: Myth TV playback top half of screen only LOG INCLUDED - yasij - 2020-04-06
This is a bug in Mesa on AMD. The fix is queued for the next Mesa 20.0.5 stable release, and already in the development Mesa 20.1.x branch.