I’m afraid not, it was early 2020 and I ended up ditching Plex as the TV OS couldn’t handle running the Plex app properly. Now I have the new Chromecast w/Google TV, I want to try again.
However, if you look at the bottom of the support page (https://support.plex.tv/articles/community-supported-tuners), the guy who realised the Windows Server issue was running the same card.
Is there no way of forcing which tuners are used?
Possible related tickets (open ticket for full list):
Is there a CLI command within Plex to check and verify the DVR status? I’m seeing “check your tuner or antenna” error when I try watching Live TV. When I use Kaffeine to verify the antenna signal, the signal is very strong. From the log file, it appears the Grabber is unable to status the DVR. However, if I stop and start the plexmediaserver the Grabber works fine and I can connect to Live TV.
My setup is a WinTV-DualHD on OpenSuse Leap 15.2 with Plex Version 1.21.1.3876. Here are the error messages.
ERROR - [Grabber/3.1-b9cnnecgft73cfb2xezucvkc] Error issuing curl_easy_perform(handle): 7
ERROR - [Grabber/3.1-b9cnnecgft73cfb2xezucvkc] Error parsing content.
ERROR - [Grabber/3.1-b9cnnecgft73cfb2xezucvkc] Error parsing XML: Error parsing file.
ERROR - [Grabber/3.1-b9cnnecgft73cfb2xezucvkc] Grabber: Error obtaining device status.
ERROR - [Grabber/3.1-b9cnnecgft73cfb2xezucvkc] Unable to find title for item of type 5
ERROR - [Grabber/3.1-b9cnnecgft73cfb2xezucvkc] Unable to find title for item of type 5
ERROR - [Transcoder] [tcp @ 0x20e9780] Connection to tcp://127.0.0.1:32600 failed: Connection refused
ERROR - [Transcoder] http://127.0.0.1:32600/devices/compound_device072dvb%23v4l%23%2Fsys%2Fdevices%2Fpci0000%3A00%2F0000%3A00%3A14.0%2Fusb2%2F2-1%2F2-1%3A1.0%3A0014110245/media/triplet%3A%2F%2F0%3A3203%3A3?param=<%3Fxml%20version%3D"1.0"%20encoding%3D"UTF-8"%3F>
<tunedata><tt>8<%2Ftt><dq>0<%2Fdq><dr%2F><fr>11<%2Ffr><md>0<%2Fmd><sr>0<%2Fsr><pl>0<%2Fpl><lf>0<%2Flf><l1>0<%2Fl1><l2>0<%2Fl2><ls>0<%2Fls><pp>0<%2Fpp><hz>0<%2Fhz><in>0<%2Fin><fc>0<%2Ffc><t>3203<%2Ft><n>0<%2Fn><s>3<%2Fs><en>0<%2Fen><%2Ftunedata>
: Connection refused
ERROR - [Grabber/3.1-b9cnnecgft73cfb2xezucvkc] Failed to start session.
ERROR - [Grabber/3.1-b9cnnecgft73cfb2xezucvkc] Recorder: Unable to create transcode session or session failed to start.
ERROR - [Grabber/3.1-b9cnnecgft73cfb2xezucvkc] Recorder: Error 16 (Recording failed. Please check your tuner or antenna.) starting the record, shutting things down.
This indicates either the Plex Tuner Service process crashed out, not started or some firewall issue blocking requests to port 32600
Having full logs zip and covering from time of launch with debug logging enabled before the server is launched would give more info and eliminate some of the possible causes I mentioned
Update: The syntax does not look right
param=<%3Fxml%20version%3D"1.0"%20encoding%3D"UTF-8"%3F> <tunedata><tt>8<%2Ftt><dq>0<%2Fdq><dr%2F><fr>11<%2Ffr><md>0<%2Fmd><sr>0<%2Fsr><pl>0<%2Fpl><lf>0<%2Flf><l1>0<%2Fl1><l2>0<%2Fl2><ls>0<%2Fls><pp>0<%2Fpp><hz>0<%2Fhz><in>0<%2Fin><fc>0<%2Ffc><t>3203<%2Ft><n>0<%2Fn><s>3<%2Fs><en>0<%2Fen><%2Ftunedata> :](http://127.0.0.1:32600/devices/compound_device072dvb%23v4l%23%2fsys%2fdevices%2fpci0000%3a00%2f0000%3a00%3a14.0%2fusb2%2f2-1%2f2-1%3a1.0%3a0014110245/media/triplet%3A%2F%2F0%3A3203%3A3?param=%3C%3Fxml%20version%3D%221%2E0%22%20encoding%3D%22UTF-8%22%3F%3E%0A%3Ctunedata%3E%3Ctt%3E8%3C%2Ftt%3E%3Cdq%3E0%3C%2Fdq%3E%3Cdr%2F%3E%3Cfr%3E11%3C%2Ffr%3E%3Cmd%3E0%3C%2Fmd%3E%3Csr%3E0%3C%2Fsr%3E%3Cpl%3E0%3C%2Fpl%3E%3Clf%3E0%3C%2Flf%3E%3Cl1%3E0%3C%2Fl1%3E%3Cl2%3E0%3C%2Fl2%3E%3Cls%3E0%3C%2Fls%3E%3Cpp%3E0%3C%2Fpp%3E%3Chz%3E0%3C%2Fhz%3E%3Cin%3E0%3C%2Fin%3E%3Cfc%3E0%3C%2Ffc%3E%3Ct%3E3203%3C%2Ft%3E%3Cn%3E0%3C%2Fn%3E%3Cs%3E3%3C%2Fs%3E%3Cen%3E0%3C%2Fen%3E%3C%2Ftunedata%3E%0A
Would need full logs to investigate
Please ensure debug logging enabled - see https://support.plex.tv/articles/201643703-reporting-issues-with-plex-media-server/
and restart the server and reproduce then download and attach zipped logs
See
https://support.plex.tv/articles/200250417-plex-media-server-log-files/
and what is the make and model of the DVR
OK - I see that release notes did mention it before but got missed in later release note
To pass new evidence of a problem to the development team, i do need it to be from the current version .
Please reproduce with the latest beta 1.21.2.3918-e47113e83 and let me have new logs zips with debug logging enabled beforehand
After more investigation I found that the issue was due to a bug in a beta release of my VPN software. It took me a while to figure it out because the browser I was accessing Plex with was set to bypass the VPN and even that shouldn’t have mattered since I was going to a LAN address.
I have been struggling with this for the last year as well.
Everything works fine and then within the same day or the next day all of the sudden Plex can’t tune to the channel for either Live TV streaming and DVR recordings fail. If I remote desktop to the machine and restart Plex the issue is fixed.
It’s getting very old constantly baby sitting this.
OK, I just installed 1.21.2.3943. REbooted just in case. Tried to tune in a live channel and got the usual error. Checked the task manager and there was no Plex Tuner Service. So, I killed all the Plex precesses and restarted Plex. Now the tuner works normally. So, for some reason the tuner service didn’t start correctly during the reboot, but started correctly after waiting some time before starting Plex. Attached are logs, check at approc 5:15 for failures. Plex Media Server Logs_2021-01-27_17-27-34.zip (2.1 MB) Plex Media Server Logs_2021-01-27_17-27-34.zip (2.1 MB)
Adding my setup to the “Reception Issues Pile”…
Config: HDHomeRun Extend tuner–> Synology NAS → browser, app, and xbox clients. All software updates are current on all devices. All devices show norminal operation with no latency issues (memory, cpu, etc.)
Problem: Problem began a few months ago. Plex is unable to tune in some OTA channels and some channels will work fine for minutes/hours, then just stop working. The SiliconDust OTA viewer does not have these issues and the reception on TV’s are fine so it’s something within Plex. I’ll submit logs if requested.
Plex Media Server v.1.21.2.3943
Was having the same issue: Playback error. Could not tune channel. Check…
Problem was resolved by exiting Plex and restarting. After this was able to tune a channel. Sounds like a timing issue. Could be a bug. Either way, I think I have a workaround.
Please try not to break the DVR/Live TV feature of this product. As many others, it is my only reason for subscribing to Plex.
Another data point:
Still running 1.21.2.3943, the tuner service worked fine for the last four days both for live and DVR recording. Today (Monday) I rebooted the computer (Windows 10) and watched the plex services in the task manager. The Plex tuner service started, and after short while it disappeared. During the start up period CPU usage stayed at 100%. (There are a lot of other jobs starting at this time.) Tried to tune in a live channel and of course it failed. Then I killed plex processes and restarted Plex. again everything is working fine. So, there really does seem to be a continuing problem with the tuner service startup when the system is under load.
I would need logs covering this from the latest version of Plex Media Server to start a new investigation. The symptoms that were seen before - exiting whilst trying to get a locked mutex with Plex Media Server should have been addressed
At this moment the current version to use is 1.21.2.3943-a91458577
Edit: I see there are some logs in your previous post. I will have a look
Thank you for the logs. I have re-opened the issue with our development team
I did some re-organization on my network and believe the issue might be related to the HDHomeRun not having a static assigned IP. I noticed that the Plex server caches the IP address won’t update it. If your router occasionally reboots, the HDHomeRun gets new leases with different IPs, etc. this could be the culprit? I have statically assigned the HDHomeRun and will see how things go.
I don’t know when it broke exactly, but I’m using a Hauppauge
WinTV-quadHD tuner, and running PMS version 1.21.3.4021.
Cannot search for channels (to re-add the tuner, after the could not tune channel errors), tvheadend works fine.
P.S The OS in my case is Ubuntu Server 20.04.
I’m still having issues on my Android TV devices. (Sony TV and Chromecast (GoogleTV).) It works on all my Roku TVs and Mobile.
Hauppauge WinTV-dualHD ATSC Tuner 2, Standards 24
Feb 16, 2021 10:49:55.145 [2924] INFO - [I] device_manager_t::get_device_list. Device Hauppauge WinTV-dualHD ATSC Tuner, id dvb#bda#0#@device:pnp:\\?\usb#vid_2040&pid_826d#0014147620#{71985f48-1ca1-11d3-9cc8-00c04f7971e0}\{7c8095ab-c110-40e5-9f4d-310858bbbf64}, tuners 1, state 0, standards 24
Feb 16, 2021 10:49:55.160 [2924] INFO - [I] device_manager_t::get_device_list. Device Hauppauge WinTV-dualHD ATSC Tuner 2, id dvb#bda#0#@device:pnp:\\?\usb#vid_2040&pid_826d#0014147620#{71985f48-1ca1-11d3-9cc8-00c04f7971e0}\{510162d9-2f7e-49e7-907b-dbd3a5a15eb9}, tuners 1, state 2, standards 24
Feb 16, 2021 10:49:58.226 [10660] INFO - [I] web_service_t::process_device_status
Feb 16, 2021 10:49:58.226 [10660] INFO - [I] device_reactor_t::get_device_list (dvb#bda#usb#vid_2040&pid_826d#0014147620#)
Feb 16, 2021 10:49:58.226 [10660] INFO - [I] dvb_device_factory_t::get_device_list (dvb#bda#usb#vid_2040&pid_826d#0014147620#)
Feb 16, 2021 10:49:58.226 [4328] INFO - [I] DeviceGetListEx_impl: Filter [Hauppauge WinTV-dualHD ATSC Tuner]
Feb 16, 2021 10:49:58.226 [4328] INFO - [I] DeviceGetListEx_impl: device instance path usb#vid_2040&pid_826d#0014147620#
Feb 16, 2021 10:49:58.226 [4328] DEBUG - [I] enum_get_name(): IPropertyBag->Read method failed -2147024894
Feb 16, 2021 10:49:58.226 [4328] DEBUG - [I] BDA: DeviceGetListEx_impl. Skipped nameless BDA driver
Feb 16, 2021 10:49:58.226 [4328] DEBUG - [I] enum_get_name(): IPropertyBag->Read method failed -2147024894
Feb 16, 2021 10:49:58.226 [4328] DEBUG - [I] BDA: DeviceGetListEx_impl. Skipped nameless BDA driver
Feb 16, 2021 10:49:58.226 [4328] INFO - [I] DeviceGetListEx_impl: Filter [Hauppauge WinTV-dualHD ATSC Tuner 2]
Feb 16, 2021 10:49:58.226 [4328] INFO - [I] DeviceGetListEx_impl: device instance path usb#vid_2040&pid_826d#0014147620#
Feb 16, 2021 10:49:58.226 [4328] INFO - [I] DeviceGetListEx_impl: pDL->Count:2
Feb 16, 2021 10:49:58.226 [10660] INFO - [I] dvb_device_factory_t::get_device_list. Id dvb#bda#0#@device:pnp:\\?\usb#vid_2040&pid_826d#0014147620#{71985f48-1ca1-11d3-9cc8-00c04f7971e0}\{7c8095ab-c110-40e5-9f4d-310858bbbf64}, Name Hauppauge WinTV-dualHD ATSC Tuner, Standards 24
Feb 16, 2021 10:49:58.226 [10660] INFO - [I] dvb_device_factory_t::get_device_list. Id dvb#bda#0#@device:pnp:\\?\usb#vid_2040&pid_826d#0014147620#{71985f48-1ca1-11d3-9cc8-00c04f7971e0}\{510162d9-2f7e-49e7-907b-dbd3a5a15eb9}, Name Hauppauge WinTV-dualHD ATSC Tuner 2, Standards 24
Feb 16, 2021 10:49:58.226 [10660] INFO - [I] device_manager_t::get_device_list. Device Hauppauge WinTV-dualHD ATSC Tuner, id dvb#bda#0#@device:pnp:\\?\usb#vid_2040&pid_826d#0014147620#{71985f48-1ca1-11d3-9cc8-00c04f7971e0}\{7c8095ab-c110-40e5-9f4d-310858bbbf64}, tuners 1, state 0, standards 24
Feb 16, 2021 10:49:58.242 [10660] INFO - [I] device_manager_t::get_device_list. Device Hauppauge WinTV-dualHD ATSC Tuner 2, id dvb#bda#0#@device:pnp:\\?\usb#vid_2040&pid_826d#0014147620#{71985f48-1ca1-11d3-9cc8-00c04f7971e0}\{510162d9-2f7e-49e7-907b-dbd3a5a15eb9}, tuners 1, state 2, standards 24
Feb 16, 2021 10:50:01.327 [2924] INFO - [I] web_service_t::process_device_status
Feb 16, 2021 10:50:01.327 [2924] INFO - [I] device_reactor_t::get_device_list (dvb#bda#usb#vid_2040&pid_826d#0014147620#)
Feb 16, 2021 10:50:01.327 [2924] INFO - [I] dvb_device_factory_t::get_device_list (dvb#bda#usb#vid_2040&pid_826d#0014147620#)
Feb 16, 2021 10:50:01.327 [9328] INFO - [I] DeviceGetListEx_impl: Filter [Hauppauge WinTV-dualHD ATSC Tuner]
Feb 16, 2021 10:50:01.327 [9328] INFO - [I] DeviceGetListEx_impl: device instance path usb#vid_2040&pid_826d#0014147620#
Feb 16, 2021 10:50:01.327 [9328] DEBUG - [I] enum_get_name(): IPropertyBag->Read method failed -2147024894
Feb 16, 2021 10:50:01.327 [9328] DEBUG - [I] BDA: DeviceGetListEx_impl. Skipped nameless BDA driver
Feb 16, 2021 10:50:01.327 [9328] DEBUG - [I] enum_get_name(): IPropertyBag->Read method failed -2147024894
Feb 16, 2021 10:50:01.327 [9328] DEBUG - [I] BDA: DeviceGetListEx_impl. Skipped nameless BDA driver
Feb 16, 2021 10:50:01.327 [9328] INFO - [I] DeviceGetListEx_impl: Filter [Hauppauge WinTV-dualHD ATSC Tuner 2]
Feb 16, 2021 10:50:01.327 [9328] INFO - [I] DeviceGetListEx_impl: device instance path usb#vid_2040&pid_826d#0014147620#
Feb 16, 2021 10:50:01.327 [9328] INFO - [I] DeviceGetListEx_impl: pDL->Count:2
Feb 16, 2021 10:50:01.327 [2924] INFO - [I] dvb_device_factory_t::get_device_list. Id dvb#bda#0#@device:pnp:\\?\usb#vid_2040&pid_826d#0014147620#{71985f48-1ca1-11d3-9cc8-00c04f7971e0}\{7c8095ab-c110-40e5-9f4d-310858bbbf64}, Name Hauppauge WinTV-dualHD ATSC Tuner, Standards 24
Feb 16, 2021 10:50:01.327 [2924] INFO - [I] dvb_device_factory_t::get_device_list. Id dvb#bda#0#@device:pnp:\\?\usb#vid_2040&pid_826d#0014147620#{71985f48-1ca1-11d3-9cc8-00c04f7971e0}\{510162d9-2f7e-49e7-907b-dbd3a5a15eb9}, Name Hauppauge WinTV-dualHD ATSC Tuner 2, Standards 24
Feb 16, 2021 10:50:01.327 [2924] INFO - [I] device_manager_t::get_device_list. Device Hauppauge WinTV-dualHD ATSC Tuner, id dvb#bda#0#@device:pnp:\\?\usb#vid_2040&pid_826d#0014147620#{71985f48-1ca1-11d3-9cc8-00c04f7971e0}\{7c8095ab-c110-40e5-9f4d-310858bbbf64}, tuners 1, state 0, standards 24
Feb 16, 2021 10:50:01.343 [2924] INFO - [I] device_manager_t::get_device_list. Device Hauppauge WinTV-dualHD ATSC Tuner 2, id dvb#bda#0#@device:pnp:\\?\usb#vid_2040&pid_826d#0014147620#{71985f48-1ca1-11d3-9cc8-00c04f7971e0}\{510162d9-2f7e-49e7-907b-dbd3a5a15eb9}, tuners 1, state 2, standards 24
I opened another issue but am not getting any responses for a month.
FWIW - after assigning a static IP to the HDHomeRun, I’ve been running solid for 5 days straight. I’ve never made it this long before.
Version 1.21.4.4054 may have done the trick. It’s the first version in which the tuner service keeps running after a reboot. Time will tell.
Edit: 36 hours later and the DVR is still working correctly,
I got tired of missed recordings and restarts/reboots. I thought it was working better after reinstalling Windows & Plex, but eventually started to fail again.
For now I have switched to NextPVR with Kodi which is working quite smoothly.
I will continue to monitor this thread periodically to see if things get better. Frustrated as PlexDVR was my reason for purchasing a Plex Pass lifetime subscription.
I decided I couldn’t wait to get his working so I wrote some Powershell to check if the tuner is running, check if anyone is watching or if anything is being recorded, and restart Plex if needed.
I set it to run every 5 minutes via Task Scheduler. It doesn’t do anything if the tuner is running so overhead is negligible.
You can get it here if you’re interested.
