Color space is not supported error after updating to 1.25.5

Do we know, for certain, that this is a licensing issue? I haven’t seen BigWheel say anything other than both the server and the client need updates (but since Infuse addressed this with just their client, I’m not sure why this is the case).

Search for “@BigWheel licensing” gives multiple results, including in this thread.

1 Like

Jellyfin hasn’t entirely figured it out. I have a file that throws the error on Plex so it won’t play at all, in jellyfin it plays but the colors are wrong (looks like it’s missing a color), and it plays fine in Infuse. This is all on an AppleTV 4K. My Zidoo Z9X also plays it just fine (wish Plex was available on that platform). I just stood-up Emby to see how that handles it (out of curiosity more than anything, but it’s still scanning).

Newest apple tv client version + newest plex server version seems to have fixed the issue, and 4k DV MKVs are being direct steamed without issue

Which version of client and server are you using? I have the latest the auto updates are providing (server: 1.27.2.5929 and ATV 4K client: 8.5 (2986)) and the problem still exists for me.

@calebcall For Apple TV 8.6 which was just released today. rollouts are staged so you might not get update notification for a day or so but you can always manually update.

you have the needed server version.

perfect, that’s exactly what I was wondering. Thanks!

Bummer, still same issue for me even after upgrading to 8.6:

Complete name                            : The Lost City (2022) WEBDL-2160p.mkv
Format                                   : Matroska
Format version                           : Version 4
File size                                : 11.5 GiB
Duration                                 : 1 h 51 min
Overall bit rate                         : 14.7 Mb/s
Encoded date                             : UTC 2022-05-10 04:03:16
Writing application                      : mkvmerge v61.0.0 ('So') 64-bit
Writing library                          : libebml v1.4.2 + libmatroska v1.6.4

Video
ID                                       : 1
Format                                   : HEVC
Format/Info                              : High Efficiency Video Coding
Format profile                           : Main 10@L5@High
HDR format                               : Dolby Vision, Version 1.0, dvhe.05.06, BL+RPU
Codec ID                                 : V_MPEGH/ISO/HEVC
Duration                                 : 1 h 51 min
Bit rate                                 : 14.3 Mb/s
Width                                    : 3 840 pixels
Height                                   : 1 608 pixels
Display aspect ratio                     : 2.40:1
Frame rate mode                          : Constant
Frame rate                               : 23.976 (24000/1001) FPS
Color space                              : YUV
Chroma subsampling                       : 4:2:0
Bit depth                                : 10 bits
Bits/(Pixel*Frame)                       : 0.097
Stream size                              : 11.2 GiB (97%)
Language                                 : English
Default                                  : Yes
Forced                                   : No

@calebcall is it possible to get your server logs and apple tv logs . there may be a scenario we have not considered in the fix.

Yep, I’ll share those as soon as I get home.

Here’s those logs, happy to provide anything else that’s needed.

com.plexapp.plex 2022-07-21–02-18-59-135.log (166.3 KB)
Plex Media Server.log (5.6 MB)

Can you try it again with the preroll disabled on the server?

I’ve updated the AppleTV app and have the latest server version and it’s not working for me either.
appletv_log.zip (1.3 MB)
Plex Media Server Logs_2022-07-21_00-58-50.zip (2.5 MB)

@calebcall can you please turn off verbose logging on server and reproduce again.

Sorry, didn’t realize I still had that enabled.

Let’s try this again:
Plex Media Server.log (9.4 MB)
com.plexapp.plex 2022-07-21–16-47-51-783.log (518.5 KB)

Looks to still be enabled. Be sure you are turning it off for server which is a check box. the one for web player is a drop down.

Make sure debug is checked and verbose is not checked then hit save at bottom, {edit thx @pl_5309 } restart server, then reproduce issue

Only because I keep forgetting, logging changes require server restart.

2 Likes

There has been so much discussion of remuxing, transcoding, color space profiles, tone mapping, etc, I’m not entirely sure what fix precisely is supposed to be in Apple TV 8.6.

I have two AppleTV setups, one on a DV-capable TV, and one on a projector that doesn’t support DV (just HDR10).

I have a DV profile 5 movie in an mkv container. In AppleTV 8.5, this would not play in either setup. Using tools shared on this thread, when i remuxed it to an mp4 file with correct DV flags, it was able to play on my DV-capable setup (but not my non-DV projector).

With AppleTV 8.6 update, the original mkv-container file plays in Plex on my DV-capable setup. It still does not play on my non-DV projector.

Infuse will play either file on either setup with colors that look right.

1 Like

That’s the expected behavior, and the expected improvement in MKV playback behavior on a DV-capable system with app version 8.6. (With some questions about why Plex activates HDR10 output mode instead of DV mode.)

Plex itself isn’t tone-mapping DV. When connected to a non-DV TV, the Apple TV doesn’t announce that DV is available.

It’s very interesting that the Apple TV 4K is capable of tone-mapping DV to either HDR10 or SDR when set to those modes, but only when the Apple TV 4K detects a DV-capable TV. I wonder if it’s a naive capability check, or if it’s a licensing entitlement check.

But if it’s a non-DV capable TV, the Apple TV won’t decode DV itself. So in that environment Plex isn’t expected to play DV P5.

Infuse is doing something different, and appears to perform tone-mapping in the app itself.

That is what I had done. So I was just going to reproduce it again but wanted to make sure logging was correct so I deleted all my logs, then restarted the server, and then went to reproduce and it now works. So I’m guessing it was the restart of the server and maybe the process was in such a state that it wasn’t picking up the logging changes and also not working right with the 8.6 update? Odd, but the 8.6 update seems to have fixed it for me now as well.

2 Likes