Open matthew-jones-uk opened 4 years ago
Can you supply come clean logs from startup to playback exhibiting the blue screen?
Also, what happens when you force software decoding of the same file when playing in MPV?
Log: plexmediaplayer.log
MPV software decoding works fine with a partial version of the same file although a little slow.
I think I'm seeing this same issue with PMP 2.50 and QT 5.9.5 - although I get a black screen, rather than blue. There are also a number of similar reports over on the AUR package by others who have also built PMP with QT 5.9.5.
EDIT: I'll also note that the issue remains even if I force transcoding by changing the quality in PMP.
EDIT 2: plexmediaplayer.log (dead link)
EDIT 3: CPU is AMD Ryzen 2700X, GPU is an AMD Vega 64
EDIT 4: Interesting - so downgrading mesa-vdpau
to 19.1.1
(it just so happened to be the oldest one I had locally) fixes the black-screen issue. Time to find it exactly which version it breaks in.
EDIT 5: So 19.1.*
and 19.2.0
versions of mesa-vdpau
seems to work for me. Other versions of 19.2.*
crash PMP outright, and 19.3.*
exhibit the black-screen issue.
Test environment
PMS Version: 1.18.3.2156 PMP Version: 2.47.0 Platform: Arch Linux
Steps to reproduce
Current behavior
Expected behavior
My laptop has an i5-8250u processor which is capable of 4K h265 decoding and I've tested this with mpv using --hwdec=auto which defaults to vaapi (although it does still drop some frames). However, when I run the same file via plex a blue screen is shown and hardware decoding is not used. When I run another file that isn't HEVC it plays but ctrl-shift-d shows that no hardware acceleration is being used.
Not sure if this is a problem with my system setup but I don't think so as mpv hardware decoding is working - ish.