Confirming that this is still an open, reported issue as of Version 1.23.2.4656.
Originally reported June 26th, 2020. This was 344 days ago:
Confirming that this is still an open, reported issue as of Version 1.23.3.4692.
This obvious and very reproducible bug was reported June 26th, 2020. This was 353 days ago:
After installing the latest server update (today), my web player for live TV/DVR was only streaming in SD. After fumbling around in the server settings (and HDHR) with no change in result, I downloaded the latest Plex player stand alone app desktop client to see if the the live TV/DVR streams would also be in SD.
The live stream was not in SD, and played as expected in the Plex app in HD on my desktop.
But then something funny happened. After installing the Plex app for desktop, my web player started to work as expected… in HD.
FWIW, I am on a Mac running Catalina. Good luck.
Cool thank you for sharing @enduser. In my case, the impacted channels are indeed with HD channels, but they do stream occasionally. I would actually be happy if there was an SD stream in place, but I typically get no stream at all 9/10 times (it seems) with the affected channels. Interestingly enough there are some HD channels that work pretty much all the time if not every time. That is, every time I test them they seem to work. It’s these other channels (which were reported extensively with logs to Plex) that are grumpy and “consistently” fail to stream.
I put that in quotes as they sometimes do stream successfully (examples of which have also been reported to Plex).
Hopefully, your solution can help others facing the same problem you encountered, however. 
(BTW, running Windows 10 here)
Confirming that this is still an open, reported issue as of Version 1.23.3.4706.
This obvious and very reproducible bug was reported June 26th, 2020. This was 356 days ago:
Confirming that this is still an open, reported issue as of Version 1.23.3.4707.
This obvious and very reproducible bug was reported June 26th, 2020. This was 360 days ago:
Confirming that this is still an open, reported issue as of Version 1.23.4.4712.
This obvious and very reproducible bug was reported June 26th, 2020. This was 361 days ago:
Happy 1-year anniversary to the reporting of this very obvious and reproducible bug.
It was originally reported on June 26th, 2020. This was exactly 365 days ago:
Confirming that this is still an open, reported issue as of Version 1.23.4.4775.
This obvious and very reproducible bug was reported June 26th, 2020. This was 374 days ago:
Confirming that this is still an open, reported issue as of Version 1.23.5.4801.
This obvious and very reproducible bug was reported June 26th, 2020. This was 386 days ago:
Confirming that this is still an open, reported issue as of Version 1.23.5.4841.
This obvious and very reproducible bug was reported June 26th, 2020. This was 389 days ago:
Confirming that this is still an open, reported issue as of Version 1.23.6.4810.
This obvious and very reproducible bug was reported June 26th, 2020. This was 390 days ago:
Confirming that this is still an open, reported issue as of Version 1.23.6.4881.
This obvious and very reproducible bug was reported June 26th, 2020. This was 398 days ago:
Confirming that this is still an open, reported issue as of Version 1.24.0.4897.
This obvious and very reproducible bug was reported June 26th, 2020. This was 405 days ago:
Confirming that this is still an open, reported issue as of Version 1.24.0.4916.
This obvious and very reproducible bug was reported June 26th, 2020. This was 409 days ago:
Confirming that this is still an open, reported issue as of Version 1.24.0.4921.
This obvious and very reproducible bug was reported June 26th, 2020. This was 410 days ago:
Confirming that this is still an open, reported issue as of Version 1.24.0.4930.
This obvious and very reproducible bug was reported June 26th, 2020. This was 412 days ago:
This has been going for a long while - My original suspicion was that this happens on channels that have more than one audio stream
Could you confirm if that is the case and also suggest listing all the channels that this fails on and may be I can get a developer to reproduce the problem - if the channel is available for their region
Awesome, thank you for your continued assistance, @sa2000 !
I believe I gave you my XmlTV channel listings, correct? This seems to happen with any stream that is of higher resolution. but I can consistently reproduce this on 3.1, 3.2, and 3.3 which are the WWMTDT channels in my area. Also, 6.1 (WLNSDT) and 8.1 (WOODDT) I test frequently and also consistently have problems.
Usually, if it’s a lower resolution, it pops right through, but it seems the higher-resolution channels are the ones that are struggling here.
Checking those “lower-resolution” channels that usually if not always pop right through, I see that they only have 1 audio stream, and the other high-resolution channels have 2, so you might be onto something there!
I greatly appreciate any further efforts you and your team can provide towards addressing this issue. 
Confirming that this is still an open, reported issue as of Version 1.24.3.5033.
This obvious and very reproducible bug was reported June 26th, 2020. This was 447 days ago:
