Hi!. It will take me awhile to gather all that info but I’ll do it.
I have not received anything from anyone. I do have a change in the next version that should be out this week that hopefully helps with some of these issues.
Oh, my. Seems like everyone may have assumed many other users would submit the requested info since there were so many people asking for updates in the thread.
I’ve just been removing all unnecessary subtitle streams from my files to avoid the issue for months now, but I’ll find a file that should be problematic and work on recreating the issue, gather the info and get it to you in the next few days. Thanks for your attention and work on the issue.
Hello,
I just sent sLumpy almost every information i could give, video file xml, plex logs, and settings in apps and hardware info.
Let me know if you need anything else.
2 Likes
JaguarPaw’s contribution motivated me to get the info to sLumpy as quickly as possible. I have also sent sLumpy the information requested. Thanks to you both!
Hope it gets fixed, yesterday there was an update 5.59.3, but the bug is still present.
1 Like
I thought I was alone with my Tizen TV (being from 2021),but it appears I’m not.
I have had this problem with many video files and embedded and external subtitle files (.srt). Tonight, it was by playing Mr. Deeds. Yesterday it was Avatar and Harry Potter and the Sorcerer’s stone.
Tonight, I thought, let’s try the PS5. Same video, same srt and NO issues. Like none at all, no skipping, no audio issues and I can keep the subtitles ON.
Now, how wonderful I thought of this workaround. I’d love to keep using the TV for my main viewing of Plex…
Hope the issues get resolved.
[UPDATE]:
And the PS5 has issues too, I was too soon with my enjoyment.
But it’s a fr better experience than on my Tizen TV.
Did some testing and looked over the info and samples provided (thanks @BigBabyBro and @JaguarPaw!), and it looks like the same issue as with some of the newer TV sets with files that have over 30 streams, but instead of failing hard, it just skips and artifacts. We may need to remux those files like we do as the workaround for the newer TVs, which means the video will direct stream. Is anyone having issues with a file that doesn’t have over 30 streams? If so, I’ll need more samples.
How come this bug did not happen a couple months ago? It used to work just fine.
The files are the same as always, they always included all the subtitles for all the languages (+30).
For me, it does not happen with other files, only the ones with a lot of subtitles.
Yar, that’s the confusing bit… Plex had no trouble playing the files with loads of streams for the longest time, whereas other methods on the TV would fail when too many streams were present (playing from USB flash drive comes to mind), then one day the skipping and artifacting began in Plex playback and it’s been that way ever since.
I’m thankful that I found this thread and we figured out the issue is able to be worked around by removing the excessive subtitle streams, but if the issue were able to be corrected and I didn’t have to remux files to ensure proper playback, that would obviously be preferable, heh.
Could be an update on Samsung’s side? I’m not sure.
If you read a bit further up the thread, you’ll come across a number of people, including myself, who think this is unrelated to the number of substitles. In my case, I could reproduce the issue each time audio transcoding was taking place on a video file.
The reason I noticed it was because a lot of my files included DTS, which suddenly last year became unplayable because of this tearing & out-of-sync issue. Enabling pass-through for DTS, which I was able to do because of my soundbar, solved the issue for a lot of my files.
The other files I had with incompatible audio for my setup, I had replaced with formats that are supported.
I’ll see if I can reverse the process for the DTS pass-through, and try to get you the logs.
1 Like
The last update is the Firmware version 1310 for this model and others, which came out July 2022, so, it’s been a while and this bug is newer than that.
Also, other people from this thread could check what firmware version they have on their TVs, that way we can rule out it’s Samsung’s fault.
I’m on 1310 as well on a UN55MU6300FXZA (2017).
4/29/23 Edit: Rather than spam with a new post, I’ve decided to just add some more information in this post.
I’ve done further testing with several files of different resolutions and codecs (all of which are still supported by the TV for direct play, so there will be no transcoding introduced into the scenario).
All of the files started with many total streams in the container (40+). I first used the sample I shared with sLumpy to pinpoint exactly how many total streams caused the issue and how many allowed the file to play as intended.
Repeatedly, when 33 or more total streams were present in the container, the stuttering/artifacting issue occurred. When I would remove a single subtitle stream, bringing the total streams to 32, every single file played just fine and the issue could not be reproduced. I used samples with and without Chapter data and it did not seem to make any difference either way or count toward the total streams figure.
For example, a file with a video stream, audio stream, 30 subtitle streams, and the chapter data always played normally for me in my testing.
I can’t speak with any personal experience to the DTS audio issue @dreagan_luna described, as I was never able to direct play files with DTS audio on my TV at any point in time. With that in mind, I would always immediately re-encoded any files with DTS audio to Dolby Digital surround so they could be direct played. IMHO, it sounds like a different problem that creates similar issues during playback.
If @dreagan_luna, or anyone else, is interested in testing with the 1-minute sample I shared with sLumpy, which is confirmed to cause the stuttering/artifacting issue I have experienced, I’d be happy to share the link so they could confirm whether or not it’s reproducible on their model of Samsung TV.
@BigBabyBro I would be very interested.
Weirdly enough, I havent had the issue of playing back 4K Pirates of the Caribbean but I do have issues with Mr. Deeds and English SRT.
I have a 2021 model, on version 2401.
1 Like
I did a little digging on what’s happening.
-
Movies and episodes that have lots of streams do not direct play well, but in this case they are unwatchable. For example a Ted Lasso episode is completely broken, stuttering every second, unwatchable. It has a total of 40 streams, and it’s 4K HDR, EAC3.
-
If I switch to “Direct Stream” (disabling Direct Play) the video playbacks OK. It just transcodes the audio and repackages the video container. The problem with “Direct Stream” is that sometimes I get an “Error 500” on the player client console, it stutters a while later, and then I get the audio desync.
-
The issue with direct stream happens time to time, and it’s not related to the number of streams. Here is an example:
I’m sending the logs to @sLumpy
Info about my setup:
* TV Year & Model number: Samsung UN43MU6100P (2018)
* Samsung app settings. Specifically:
* Advanced → Allow Insecure Connections & Prefer Insecure Connections: Always and Always
* Manual Servers (if any): 192.168.0.23:32400 (media was not played from this server, but from a remote one that is not manually set)
* Audio/Video/Subtitle Burn settings: Automatic
* PMS Network & Transcoder settings:
* Ipv6: disabled
* Strict TLS: Enabled
* GDM enabled
* Proxy relay: disabled
* URL: https://plex.mydomain:443
* Whitelist: my home IP
* Webhooks: enabled
* PMS device CPU/GPU:
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
Address sizes: 46 bits physical, 48 bits virtual
CPU(s): 4
On-line CPU(s) list: 0-3
Thread(s) per core: 1
Core(s) per socket: 1
Socket(s): 4
NUMA node(s): 1
Vendor ID: GenuineIntel
CPU family: 6
Model: 60
Model name: Intel Core Processor (Haswell, IBRS)
Stepping: 4
CPU MHz: 2599.998
BogoMIPS: 5199.99
Virtualization: VT-x
Hypervisor vendor: KVM
Virtualization type: full
L1d cache: 32K
L1i cache: 32K
L2 cache: 4096K
NUMA node0 CPU(s): 0-3
Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ss syscall nx pdpe1gb rdtscp lm constant_tsc rep_good nopl cpuid tsc_known_freq pni pclmulqdq vmx ssse3 fma cx16 pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand hypervisor lahf_lm abm invpcid_single pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase bmi1 avx2 smep bmi2 erms invpcid xsaveopt md_clear
Host OS: 4.19.0-8-amd64 #1 SMP Debian 4.19.98-1 (2020-01-26) x86_64 GNU/Linux
Docker image: "plexinc/pms-docker:1.31.1.6733-bc0674160"
Docker version: Docker version 23.0.1, build a5ee5b1
Additional info: I was reviewing my docker logs and I found some concerning stdout’s.
decoder information: 249
decoder error: 254
decoder error: 254
TrueHD processing failed with 254
decoder information: 249
decoder error: 254
decoder error: 254
TrueHD processing failed with 254
decoder information: 249
decoder error: 254
decoder error: 254
TrueHD processing failed with 254
decoder information: 249
decoder error: 254
decoder error: 254
TrueHD processing failed with 254
That’s just the information PMS is printing to the stdout. Maybe this issue requires a little bit of error handling from the server side at least to know the traceback or the log dates. It could be related or not.
Hi.
Can you try to play the file with 32+ streams, but this time disabling “Direct Play” in your Plex settings?
Hello.
When disabling “Direct Play” in the client settings, both a 1080p and 4K HDR file (with over 40 streams) play without encountering the issue that I have when using Direct Play. I didn’t have any Error 500 issue, but I didn’t play the files for a substantial length of time.
I did encounter a separate issue when using Direct Stream when I attempted to enable subtitles after a file was already playing. This particular file only had seven streams. I paused, selected the subtitle that I wanted, and tried to play the file. It had an extended period of buffering and then reported that it was playing in the dashboard but it wasn’t. After I backed out to the show episode menu and played from there, it ended up playing fine with the subtitles enabled. Kinda strange.
If I had to guess, I’d imagine that when Plex tears down the original file and repackages it for Direct Stream, it only includes the video, audio and relevant subtitle stream, rather than every subtitle stream being included in the modified file/container data that ends up getting sent to the client, allowing it to circumvent the maximum stream issue some (or is it all?) Samsung TVs have.
Perhaps a Ninja or Employee with a greater understanding of how Direct Stream handles things might be able to confirm or deny that’s what’s happening.
Thanks for working on the issue and trying to get to the bottom of things @dantebarba!
Error 500 only happens if you activate a SRT subtitle while playing. If you watch the movie with no subtitles set it will playback just fine. Unfortunately subtitles are a must in my case.
I sent everything to @sLumpy just as he requested. The issue continues to happen and it’s quite frequent in some movies. I still have some tests remaining to perform, but for what I’m seeing there is no evident server-side traceback on the error 500 so it might just be a client side bug.
Any feedback would be great.
