+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting)
+--- Thread: SOLVED: Dolby Vision issues (/t-solved-dolby-vision-issues)
Dolby Vision issues - andres87 - 2024-09-19
Hello, I'm experiencing weird issues when trying to play DV content.
If I try to play it on the browser (SDR) it transcodes, but all I see is a green screen.
If I try to play it on the WebOs app (DV compatible TV LG C3) the same happens, but then I go back and play it again and the "Dolby Vision" logo appears on the TV and it plays perfectly except for a hideous yellow tint affecting not only the video but the Jellyfin interface too.
The logs show when I play it on the browser is "transcoding" and when I play it on the TV is "remuxing". I attached the logs (with the video name censored) and my settings.
Is there a way I can fix this or is this related to my hardware and there's nothing I can do except not using DV files?
Thank you.
RE: Dolby Vision issues - nyanmisaka - 2024-09-19
The first issue means you need to update the Intel GPU driver.
https://www.intel.com/content/www/us/en/download/785597/intel-arc-iris-xe-graphics-windows.html
But beware stupid M$ may automatically downgrade your driver version which contains a bug that will cause the green screen.
RE: Dolby Vision issues - andres87 - 2024-09-19
(Yesterday, 10:55 AM)nyanmisaka Wrote: The first issue means you need to update the Intel GPU driver.Thank you this solved the issue completely. (As it was a brand new MiniPC that had A LOT of updates when I first started it I assumed everything would be updated, I didn't know I had to update things by myself.)
https://www.intel.com/content/www/us/en/download/785597/intel-arc-iris-xe-graphics-windows.html
But beware stupid M$ may automatically downgrade your driver version which contains a bug that will cause the green screen.
As for the second issue turns out you have to calibrate the LG TV while playing "Dolby Vision" content because it doesn't respect the general calibration of the TV. So that's solved too!