I know you’re busy and I hate bugging but just an fyi i did send log updates 
@techieanalyst I took another look at your logs and it appears the issue is bad dolby vision data. Previously the transcoder just ignored DOVI data, however there is better support in this version so its erroring on data it previously ignored (even though we are just using this support to strip the DOVI data since we do not have a licensing agreement with dolby to support DOVI). That being said it doesn’t make a lot of sense to care if the data we are stripping is valid or not so I created an issue, though i cannot guarantee how it will be prioritized against other regressions or if will be a blocker for the public release.
NP, I mean does the data mean or help anything maybe just ignore it int he newer release as well lol
There were fundimental changes which make ignoring it not an option
Always a logic loop
Question… What specifically does “we do not have a licensing agreement with dolby to support DOVI” mean functionally? Does it mean DoVi files won’t play as DoVi in Plex or that the transcoder won’t use DoVi information for transcoding\tone mapping? It might have been explained elsewhere but seeing a statement that Dolby Vision won’t be supported by Plex caught my eye and seems like a big deal so I just wanted to confirm what was meant by that statement please.
Plex can direct play Dolby Vision video.
Plex cannot transcode Dolby Vision video.
If the video is DV only (profile 5) and Plex needs to transcode, it will fail and display a “color space not supported” error.
If the video has HDR 10 compatibility (profiles 7 & 8), and Plex cannot direct play the DV video, it will try to direct play the HDR 10 video. If it cannot, then it will try to transcode the HDR 10 video.
4 Likes
@FordGuy61 is correct. we do not have an agreement with dolby to support generating dolby vision so DOVI data is stripped from all transcodes. Unfortunately the license to encode DOVI data is a couple thousand per machine so i do not see us supporting this any time soon. We still support direct play of DOVI where we can.
5 Likes
Thank you @FordGuy61 and @chris_decker08 for detailing that out for me. I appreciate it. 
I knew the licensing thing could be rough (particularly around Dolby Vision and Dolby Atmos) and recognize why Plex needs to comply with it (for the business model). I just got a little worried with the phrasing. Thanks!
Do you have any information for my problem with live TV ?
@ouvr7 I have your live TV error on my todo list, however i have NO IDEA why the error is blocking other playback for you, others who see the same error are not experiencing the same behavior.
2 Likes
I have an issue with live TV on the latest beta. Playback randomly stops with the following error:
Oct 28, 2025 21:12:15.190 [139676810726200] ERROR - Session 0x7f08ea8e1298 terminated
Oct 28, 2025 21:12:15.296 [139676211309368] ERROR - [Req#12b7bc/Transcode] MDE: No part decision to choose from
Oct 28, 2025 21:12:15.296 [139676211309368] ERROR - [Req#12b7bc/Transcode] MDE: No part decision to choose from
Oct 28, 2025 21:12:15.296 [139676211309368] ERROR - [Req#12b7bc/Transcode] Streaming Resource: Cannot make a decision because either the file is unplayable or the client provided bad data
Everything was fine until the version of ffmpeg was updated to v6 in 1.43.0.10162.
Sure thing, next week I will be able to send you some logs.
Too bad they didn’t permit us to buy a license directly and load it on our servers
I don’t know that all that many server admins would be willing to fork out this kind of money from their own pockets…I can see why they didn’t.
their licensing structure is defiantly designed with the thought that only production houses would be purchasing the encoding licenses and priced it as such.
2 Likes
Im just saying the option would be nice, I mean I put a 6000 RTX blackwell in my server for transcoding 
everyone is different
Actually $1k a license it looks like
can you guys just add it so we can put in a license code or if we prove we buy one it’s all good or not how it works?
@chris_decker08 so, weird thing, i’ve tried rolling back to earlier stable builds,and have rolled back again to the 1.43 channel.
My issue is that my Win 11 plex server will not transcode at all (audio or video) - nor will it create any more optimised versions - for any media item (haven’t tried music but i’ve never optimised that anyways).
Win 11 pro 24h2 26100.7019, PMS version 1.43.0.10231.
I reset windows firewall settings and have now turned it off for local networks.
I tried playing via browser to test transcodes - no go.
If I force direct play - that works fine for the most part.
i’ve done one DB repair but there were no issues found there.
Any guidance would be appreciated 
@chris_decker08 Adding some additional logs to some transcoding issues I am facing.
Running 1.43.0.10231 in docker running a Gen 12 Intel CPU
What I am facing is the following;
When a play a video that requires transcoding, it transcodes up to like ~80 chunks and then it just stops or halts… so the video on the client plays until it reaches the final chunk and then it just hangs until it times out on the client. So it does transcode, but just stops and there are no real transcoding errors or anything in the logs.
Tried on 3 clients, issue reproduced all 3 clients,
- an LG OLED tv(transcodes on its own due to lack of support)
- Macbook client (can direct play, but when forcing transcoding to test the issue re-appears).
- Using web player
I tried reverting back to the latest public release 1.42.2.10156 to test but that is also facing the same issue for some reason. As far as I know the video is not corrupted because i can watch it without any problems with direct play.
