My provider gives the HD versions of channels on higher numbers (channel 4 is SD, 704 is HD for the same channel). If I scroll in the channel list for 704 and try to watch, it tunes 4, which is only SD and looks horrible. The problem seems to exist for all channels that have an SD and HD version. Plex always tunes the lower channel number which is SD only. I confirmed that it was tuning to the wrong channel by checking the tuner status on my HDHomerun device.
Prior to the update with the grid guide, I was able to tune the HD versions via Plex (though it was tedious). Now it seems impossible which makes live TV kind of useless…
Can anyone help? I definitely think this is a bug somewhere since I am explicitly choosing one channel number to tune, but Plex grabs another.
My cable provider has the same channel scheme and I have good reason to want to maintain the integrity of the lineup (completeness rather then truncating or removing the SD channels).
I can confirm your findings and first came upon the bug the day of the release of PMS Version 1.13.2.5154. I have also since reported it in this forum and believe that the Plex devs are aware of the issue.
Just to be clear though, I see this bug only in the Plex Media Server’s (Web Interface) new grid guide view and not in the Plex clients I have tested.
Also if in the Plex Media Servers new grid guide you switch from “Channels” to “Discover” (older guide method) and navigate to an HD channel you may find that you can indeed Live tune to an HD channel properly.
As long as scheduled recordings are specified with respect to channel they should tune to the correct HD channel when recording.
Its an annoying bug but if you are seeing the same bug I am it can be worked around as long as you aren’t using the PMS web interface with grid guide as your main method for watching Live TV.
Edit
Hopefully a fix is coming soon.
I have comcast and they have duplicate channels, SD from 0-699, HD 700-875, and a new channel test with both combined 1000-1500 or 1600.
Since most are duplicates it doesn’t make any since to include the SD versions in your list. So you go to the Homerun tuner and block the channels that are duplicates and anything that doesn’t suit your fancy, like shopping or religious channels.
After that go to the Plex UI and have the tuner re scan channels removing the undesired duplicates, and you will never have to see them again.
That might work for the OP but not for me.
Most of my SD channels are duplicated in HD channels but not all of them. There are some SD channels that are only available in SD in my lineup. Therefore, I would have to go through almost hundreds of channels with a fine toothed comb to find them.
Also I actually want my SD channels because they load up faster and perform better on portable devices. Plus SD channels look about the same as HD on smaller screen devices (iPhone or iPad for example) without being as taxing.
So SD is useful and tedious to remove.
Then there is the simple fact that this is a bug that should be fixed on the developer’s side not necessarily worked around on the users side.
I’m sure (or hope) the Plex developers appreciate the feedback so that they can find and fix bugs that were previously overlooked.
I am having the same exact issue… Hope this bug is fixed soon
I am also having the same issue. NYC FiOS. Channel lineup is SD channel + 500 for HD (so CBS 2 is CBSHD 502). When tuning to a HD channel Plex via the new grid guide instead tunes the SD variant.
Still I’ve found that despite this bug, recorded TV is indeed in HD provided the channel set to record is specified. That’s something,…
Unfortunately the updated Windows client with grid guide view has this bug too so the bug is spreading to clients that gain the new guide,…rather then being fixed.
Edit:
I suspect this is a server side bug. If so, when PMS receives a bug fix for this the client software will likely be automatically corrected as well.
In the meantime, it doesn’t look good to see new client software with a grid guide view update propagating a known bug.
Unfortunately I don’t see any mention of a fix in the release notes for PMS version 1.13.3.5208, which is as I understand it, the latest version. I’m out of town anyway for the next few days and can’t update my PMS install anyway. Even if I could do the install remotely I wouldn’t because I prefer to keep an eye on the upgrade.
