Some of my files are green

Plex Media Server
1

Server Version#: 1.32.5.7328
Player Version#: Plex Web 4.110.1
<If providing server logs please do NOT turn on verbose logging, only debug logging should be enabled>

It’s not easy being green… or watching an old episode of a TV show tinted green. This error isn’t occurring with all of my files, and seems to be more prevalent with the older ones. Basically everything is tinted green. This remains even if you optimize the file or elect a different quality. It’s happening on the web player, my android app and my samsung tizen players, so I think it relates to the new server update rather than the players themselves. I rolled my server back a few versions (because I’m also trying to avoid the transcoder prematurely exiting issue on the samsung TV, which started with server versions released after Memorial Day) to 1.32.1.6999, which resolved the issue.

This happening to anyone else? Will this get fixed in the next version?

2

Show a screenshot please.

You likely have DolbyVision Profile 5 video files (which cannot be transcoded & tonemapped).

They are DirectPlay only in Plex.

3

image
image886×564 76.1 KB

image
image904×553 67.3 KB

The first image is with the server running version 1.32.1.6999. The second one (the green one) is after updating to 1.32.5.7328.

4

GeminiLake CPU? (J4xxx)

5

AMD Radeon R7

6

In your Transcoder settings - Turn off ToneMapping

We now have AMD HW transcoding support - EXCEPT FOR tonemapping :slight_smile:

This is ‘release 1 - SDR transcoding’ (which looks darn good anyway without tone mapping)

7

Unfortunately, that didn’t seem to fix it.

8

Quick question: Are the files in question “Interlaced” or “Progressive” scans?

Some of my older Interlaced files look like that on certain players, only the green kinda ‘flickers’.

9

So, that’s not the case here. There’s no flicker. It’s as though all light’s been filtered through a green gel, and occurs across mobile, web, and smart tv players.

I was hopeful about the tone-mapping idea, but the thing that seems to make the difference is rolling back the server, and it strikes me as unlikely that a setting that existed in the older version (where everything worked fine) would be responsible for a problem that existed in the newer one. At the same time, this is impacting a significant chunk of my library, to an extent where I would also expect that I wouldn’t be alone with this issue, which seems to be the case. So I’m flummoxed,

If it helps, the latest version of the qpkg where I know this wasn’t occurring was 1.32.4.7195.

The first time I encountered the problem was when I downloaded the beta 1.32.5.7318 in the hopes it would remove the error I was getting on the tizen players that I described above. I didn’t try the beta versions prior to that, so I can’t pinpoint the release where it started. Rolling back the server reliably stops this, so earlier versions of the plex server could handle my files just fine.

10

Disabling hw acceleration solved this for me. Also have AMD GPU on the server.

11

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.