It will happen with path mapping as well. Iirc someone tested that on the PM4K thread before the patch was released, and it still had OSD stutter issue.
I believe the root cause was how the Kodi video player was invoked rather than the specific format.
PKC uses plugin handler, PM4K uses https/smb handler:
That makes sense re: why the TV seems apathetic to the incorrect bit selection. I’ve been doing a bit more digging into this issue and chatting with the PM4K creator.
Just a quick high-level summary.
There are 2x apps that extend Plex onto Kodi. They are PM4K (PlexMod4Kodi) and PKC (PlexKodiConnect).
Both are capable of SMB path substitution to directly play the content. However by default, both utilize the webstream method where it passes the stream URL generated by Plex into the internal pl…
HTTPS/SMB handler has a slight difference in timing vs plugin handler. This post from Portisch explains more:
It’s a knowing timing issue. Not sure yet how to solve it…
When it works:
kernel knows it’s DV, set display mode 0.5s after that → 8bit
When it does not work:
kernel does not know it’s DV, set display mode, kernel knows 0.5s after it’s DV → to late → 12bit
1 Like