How does one go about finding the root cause for something like this?
Aug 20, 2022 12:23:14.069 [0x7f0f019dcb00] ERROR - [Req#8656a] [Plex for Samsung] [xxx:yyy] [Unhandled Rejection]: PLAYER_ERROR_NOT_SUPPORTED_FORMAT
TypeMismatchError: PLAYER_ERROR_NOT_SUPPORTED_FORMAT
at getErrorObjectLocalStore (:1:5910)
at callback (:1:9454)
at :1:22577
at i (https://app.plex.tv/tv-tizen/main.js:2:1996)
Oddly, the TV is throwing this error only for a handful of files, while all others are fine, many of which are encoded in the exact same way as the files it is refusing to play. These are 4k files. And, like I said, most work. Some inexplicably don’t, even though there is no difference in the encoding (mp4, x265) I could find.
Any ideas or pointers would be greatly appreciated.
Looks like the number of subtitle tracks was causing the issues. Apparently, the Tizen player doesn’t like it if a 4k video has 32 subtitle tracks or above. Under 32 subtitle tracks all is well. On a 1080p video, it’s fine with 32 subtitle tracks or more. It seems the track restriction is just happening with 4k streams.
Also, to be honest, it may not be strictly subtitle tracks, but the overall number tracks. I didn’t invest the time to find out one way or the other. I chopped some subtitle tracks, and now all is fine.
It’s 30 streams, if you turn playback info on you will see the error, something like “direct play not possible file exceeds 30 streams”
Video and Audio are 2 streams so you may have another 28 tracks…It’s very frustrating as I have plenty of files with more than 28 subtitles and I have to use my Roku to direct play them, but thats a problem for Samsung/Tizen OS
