Server Version#: 1.30.0.6359
Player Version#: PlexWeb Version 4.87.2
Tuner Make/Model: HDHomeRun
Model: HDHR5-2US
Firmware: 20221031
Guide/Lineup name: zap2xml
Using XMLTV?: zap2xml
Channel number/Name: ABC 15.1
I’m getting vertical lines in Plex, but not in the HDHomeRun viewing app.
The right image is Plex. The left is HDHomeRun
Anyone else seeing this? I’m not exactly sure when it started, but I noticed it on a recording I had at least 2 weeks ago also.
Related: Live TV HD Appears Pixelated
This seems to be something new/recent w/ Plex transcoding. Everything was working really well for me until recently when I noticed this issue.
If anyone on the Plex team wants to test with me, feel free to reach out. If you’re even listening.
I had some time to go back in time and here’s where I DON’T notice the problem. These are 32 bit Windows versions, BTW.
Reverted back to:
1.29.2.6364 (11/08/2022 release?) - No pixilation/vertical lines
Upgraded to:
1.30.0.6359 (11/08/2022 released?) - Pixilation/vertical lines returned.
I don’t have any links to versions in-between those versions, but I can confirm the issue exists in 6406 and 6442 also.
FWIW… I’m going back to 1.29.2.6364 and will spot check future releases until I deem that Plex has fixed their problem. Stay tuned for further reports.
Maybe drop a note in this thread Plex Media Server 1.30.0.6359 - New Transcoder Preview - #47 by xerxist.
I’ve marked my issue as “fixed” but would like to direct all firepower to this issue as the official issue to track.
I don’t appear to have the appropriate access or rights to post in there. I’ll try perusing that area for access instructions, or perhaps @FordGuy61 can hook me up.
Not sure why you can’t post in the transcoder preview thread. It is a thread, just like any other. I don’t see anything special about it.
Anyway, I’ll drop a note in that thread with a link back to this one.
There’s no Reply button in any of the Beta threads when I view them. It must be by invite or permission. Is there someone in the Beta section I should ask? Thanks for cross posting this in there though.
I am curious about this issue and if it’s been identified and labeled for a potential fix in a future version. I see that this issue has been marked as solved, but that’s not the case is it?
I am unclear how Plex release schedule/protocol handles this so any context/insight would be appreciated. 
I am now realizing that this is for the beta band. 
I have always had our server set to the RTM band but somehow it got switched over to Beta and hence the disruption here. Setting back to Public has removed the nag to update and everything is OK here now.
As such, this is no longer a priority for me, although it would be nice to get it fixed before it RTMs 
My testing yesterday/today with 1.30.0.6497 is providing good results so far.
Doh… feeling a little lost now. I am getting a prompt now in Public band for 1.30.0.6486 … is this safe for this issue? I thought Public was 1.29.x. 
It’s the Holidays’ do you really want to add new problems.
I am just now seeing this and never saw a notification. Are you asking me or Plex? 
is 1.30 public or beta? I am on the Public band but it’s saying to upgrade to 1.30 so I am confused here hence my question.
I haven’t upgraded yet and awaiting some guidance here before I do so. 
@Mike-E It was intended for you, If you are on 1.29.2 then wait till the new year. You can read all the “My Server is Crashing” threads for those that already upgraded just as most of the support left for the holidays.
That is hilarious @pl_5309! So if I understand correctly the Beta was indeed pushed to Public and here we are.
Got the same issue & its driving me crazy. Hoping they fix it in an update soon
I haven’t seen a Plex employee post in this thread yet about the issue and if they are working on a fix, or even acknowledging that it is an issue. I have yet to update my PMS past 1.29.2.6364 that doesn’t have this issue. Would love to hear an update to so I can look forward to getting on the newest PMS.
For what it’s worth, so far, as of 1.30.0.6497, I no longer see the artifacts I observed before.
Still have the issue on 1.30.0.6486.
