I’ve tried every possible troubleshooting method but just can’t get live tv to work. I’ve tried everything from restarting, unplugging the tuner, uninstalling and reinstalling plex, and much more. But whenever I try tuning to a channel I get a playback error:
I have a
-Asus ROG gu501gm
-Hauppauge! WinTV-HVR 955Q
Someone please help!
*Update for those still looking
Since live tv and DVR was the only reason I wanted Plex, I decided to cancel my subscription. However, we recently decided to invest in a relatively decent outdoor SWantenna, and also considering so when that arrives I will try it out once again. Thanks for all the discussion!
*Update 5/29 (probably final for me at least)
I am happy to say that my issue has resolved, after switching to an out door antenna. However, the quality of the recording and the broadcast were horrible, therefore I decided to abandon Plex (at least untill they fix some issues with the software), seeing that its not worth it. Becuase so many people are having Issues, I will keep the forum open. Thanks all!
Having the same issue. Running a Hauppauge 950Q on Windows with Plex Server 1.14.0.5470. I can get the tuner to pull up in WinTV app. Scans channels put can’t tune to them Logs attached.
I am having the same issue, and have been having a head strain trying to figure out the cause and how to fix it. We are using a HDHomeRun Extend, software version 1.14.1.5488-cc260c476 on Windows 10. Reading your post, it is unfortunate that this is not an isolated, per-streaming device incident; I believe that this is an error with Plex itself.
Plex scans all of the channels successfully and displays them in the Guide (http://prntscr.com/m1c6ye). When I try to access a channel, it gives the same error included in your image // EDIT: Attempted such at 08:37 MST -7:00 and it successfully loaded the channel. It appears that this is an intermittent issue.
When I run the HDHomeRun Windows app, it loads all of the channels and displays the stream with no problem. Hardware is a HDHomeRun box with an Ethernet running to our router and the coax line extending to a receiver outside.
This seems like a little-experienced case, so I am eager to hear back from others experiencing the same!
// I’m pondering downgrading software version, since I don’t remember this issue happening in the past. I’ll update the thread with results if undergoes
I am also having this problem since Dec 2018. I have the HDHomerun Dual, and it was working just fine for a couple months and then this issue popped up. I have been watching for any response from Plex in these forums, and I’ve seen nothing.
I have this exact same problem and cannot find a fix. HDHomeRun Dual is what I have. It perfectly works with the HDHomeRun software and the Channel app. For PMS (installed in uNraid server), it worked for a few days and have had this error mentioned above ever since. I cannot make it work again. I have tried many different possible solutions, like installing a version from 3 different repositories, uninstalling and reinstalling the DVR countless times, etc. I will really like this to be resolved.
/sigh, can’t access a bunch of channels. Logs are attached, and my attempts prior to capturing the logs were at 8:01am.
Can’t access ABC, etc. but can access my local Fox channel. I am running an hdhomerun prime, and plex is running on unraid. I can access the channels through the hdhomerun software, and through windows media center just fine.
What is weird about this, is that I had no issues with plex before leaving last weekend for an event, and when I came home, I no longer could access most of my channel lineup. I did upgrade to the latest version prior to leaving on Thursday but all was working just fine. Just thought I would throw this out there too. I am not sure what to do here, but I can’t get to most of my channels right now. none of my local channels. I’ve removed the dvr stuff, and re-added it all back in to plex. I’ve spun up a new instance of plex, and re-added everything, and completely set it up as a fresh new install. I am getting the exact same thing.
Just an idea but does anyone know if this a VHF vs UHF problem? All my channels come in UHF and I cannot access the two channels on VHF due to bad reception. But I am not having any issues on my UHF using a Hauppauge 4 tuner card running on UNRAID. Hopefully my comment can narrow down the issue. I wish I had access to VHF to confirm whether or not this is a VHF or a UHF problem.
hmm. I am using hdhomerun primes with cablecards. It’s not over the air, so I don’t believe I would be in the same boat as you? I did check the signal of the channels that Plex can’t access, from the hdhomerun software, and the signal was 100% and quality was 95% on all of them.
I really hope they respond soon with something to try, because not being able to watch ABC has my wife all up in arms over here… I am not sure I can withstand all the wife aggro… lol.
I am guessing this is where the issue is in the logs?
This was a fresh attempt I did just a couple minutes ago, and then I grabbed fresh logs(Attached)
Mar 26, 2019 11:52:28.521 [0x151c46ff7700] DEBUG - DVR:Grabber: Signal information for tune on channel 702: strength: 91, quality: 0
Mar 26, 2019 11:52:28.521 [0x151c46ff7700] DEBUG - Activity: updated activity 42cdf59d-dcc1-4e7a-acdb-accb62f27f86 - completed 1% - Recording
Mar 26, 2019 11:52:30.373 [0x151ca7bfd700] VERBOSE - WebSocket: processed 1 frame(s)
Mar 26, 2019 11:52:30.549 [0x151c459e9700] ERROR - [Transcoder] http://192.168.1.9:5004/auto/v702: Server returned 5XX Server Error reply
Mar 26, 2019 11:52:30.551 [0x151cac2e9700] VERBOSE - JobManager: child process with handle 8324 exited
Mar 26, 2019 11:52:30.551 [0x151cac2e9700] DEBUG - Jobs: ‘/usr/lib/plexmediaserver/Plex Transcoder’ exit code for process 8324 is 1 (failure)
Mar 26, 2019 11:52:30.551 [0x151ca61bf700] DEBUG - TranscodeSession: session failed while waiting for duration
Mar 26, 2019 11:52:30.551 [0x151ca7fff700] DEBUG - Streaming Resource: Terminated session 0x151c7c050850:ca2f216e-6fd6-4d98-a76e-ff5d7639f6af with reason Recording failed. Please check your tuner or antenna.
Mar 26, 2019 11:52:30.551 [0x151ca61bf700] ERROR - Failed to start session.
Mar 26, 2019 11:52:30.551 [0x151ca61bf700] ERROR - DVR:Recorder: Unable to create transcode session or session failed to start.
Mar 26, 2019 11:52:30.551 [0x151ca5fbe700] DEBUG - Killing job.
I am not sure why the strength is so low. and the quality0. I started a stream on WMC and attached that screenshot. But the signal and quality are 100%. I also watched plex try on 702 from the hdhomerun diag screen, and saw that it connects, and gets a good signal strength, but the quality never goes above 0, and then plex stops trying, and the hdhomerun diag goes blank because the stream stopped. Hope that makes sense.
Lastly I added in channel 002, which is the SD channel I was trying. and it works just fine in plex… There is something broken between the hdhomerun stream, and plex.
I saw that error, but was not sure why this would be the case when other apps can stream the channel just fine from the same tuner on the hdhr. I’m going to uncheck that channel on the .9 prime, so that only my other one (.8) will be used. just to see.
well crap. So it loaded up 702 just fine on the .8 tuner. I tried another channel that wasn’t working and it is now working too. the other channel is on the .9 right now. I just re-checked 702 on the .9, and it is working now too. Just before I unchecked the channel, I did try, and it had failed. So I dunno what caused this? but 702 is now playing on the .9 tuner just fine.
So I am noticing a lot of artifacting. And the signal quality is hovering between 60-70% I just turned off 702 from the .9 and am looking now at the quality to the .8 hdhr, I also have the same channel streaming on .8 from my htpc running windows media center.
WELL PISSSSS. okay so 702 is working fine on the .8… I just forced WMC to use the .9 only, and it has the same issue of really poor signal. I am going to swap the coax cables going to each, and see if the signal follows, or I guess my HDHR may going out. I guess this may not be a plex issue afterall… Which makes sense since I hadn’t done anything, other than upgrade a few days before leaving, and all was working fine…