Server Version#: 1.18.3.2156
Player Version#: N/A
My Plex server DVR & Live TV was working a few weeks ago with this USB tuner but after upgrading to the latest version the existing DVR setup was lost. When I try to setup DVR and Live TV again my tuner is not detected. The DVR Setup screen displays “Looking for compatible devices…” with a never ending spinner and a link to manually add an HDHomeRun device. The TV service is running and the WinTV application works. Any help would be appreciated as this is the only reason I purchased a Plex Pass with a one year subscription the beginning of this month.
Uninstall the WinTV software and install only the driver. From the Supported DVR Tuners Supprt article https://support.plex.tv/articles/225877427-supported-dvr-tuners-and-antennas/
- Windows: “WinTV 8” (for WinTV tuners) or “AVerMedia TVBox” (for AVerMedia tuners) software might conflict with Plex Media Server’s use of the tuner. If you have issues tuning channels, please remove this software, install only the driver for your tuner, then attempt to scan channels again.
Thank you for your response. I removed the WinTV software which also removed the tuner driver. I installed the driver software only that I downloaded from the Hauppauge support site and restarted the box. The result is the same. My device is not detected.
I see these lines repeated in the Plex Tuner Service Log file:
Dec 29, 2019 12:41:03.354 [15308] INFO - [I] web_service_t::process_get_scanners
Dec 29, 2019 12:41:03.354 [15308] INFO - [I] device_reactor_t::get_device_list (dvb#bda#usb#vid_2040&pid_826d#0014051812#)
Dec 29, 2019 12:41:03.354 [15308] INFO - [I] dvb_device_factory_t::get_device_list (dvb#bda#usb#vid_2040&pid_826d#0014051812#)
Dec 29, 2019 12:41:03.362 [11316] INFO - [I] DeviceGetListEx_impl: Filter [Hauppauge WinTV-dualHD ATSC Tuner 2]
Dec 29, 2019 12:41:03.363 [11316] INFO - [I] DeviceGetListEx_impl: device instance path usb#vid_2040&pid_826d#0014051812#
Dec 29, 2019 12:41:03.363 [11316] INFO - [I] DeviceGetListEx_impl: Filter [Hauppauge WinTV-dualHD ATSC Tuner]
Dec 29, 2019 12:41:03.363 [11316] INFO - [I] DeviceGetListEx_impl: device instance path usb#vid_2040&pid_826d#0014051812#
Dec 29, 2019 12:41:03.364 [11316] DEBUG - [I] enum_get_name(): IPropertyBag->Read method failed -2147024894
Dec 29, 2019 12:41:03.364 [11316] DEBUG - [I] BDA: DeviceGetListEx_impl. Skipped nameless BDA driver
Dec 29, 2019 12:41:03.364 [11316] DEBUG - [I] enum_get_name(): IPropertyBag->Read method failed -2147024894
Dec 29, 2019 12:41:03.364 [11316] DEBUG - [I] BDA: DeviceGetListEx_impl. Skipped nameless BDA driver
Dec 29, 2019 12:41:03.364 [11316] INFO - [I] DeviceGetListEx_impl: pDL->Count:2
Dec 29, 2019 12:41:03.367 [15308] INFO - [I] dvb_device_factory_t::get_device_list. Id dvb#bda#0#@device:pnp:\?\usb#vid_2040&pid_826d#0014051812#{71985f48-1ca1-11d3-9cc8-00c04f7971e0}{510162d9-2f7e-49e7-907b-dbd3a5a15eb9}, Name Hauppauge WinTV-dualHD ATSC Tuner 2, Standards 24
Dec 29, 2019 12:41:03.367 [15308] INFO - [I] dvb_device_factory_t::get_device_list. Id dvb#bda#0#@device:pnp:\?\usb#vid_2040&pid_826d#0014051812#{71985f48-1ca1-11d3-9cc8-00c04f7971e0}{7c8095ab-c110-40e5-9f4d-310858bbbf64}, Name Hauppauge WinTV-dualHD ATSC Tuner, Standards 24
Dec 29, 2019 12:41:03.367 [15308] 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#0014051812#{71985f48-1ca1-11d3-9cc8-00c04f7971e0}{510162d9-2f7e-49e7-907b-dbd3a5a15eb9}, tuners 1, state 0, standards 24
Dec 29, 2019 12:41:03.367 [15308] 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#0014051812#{71985f48-1ca1-11d3-9cc8-00c04f7971e0}{7c8095ab-c110-40e5-9f4d-310858bbbf64}, tuners 1, state 0, standards 24
Any help would be much appreciated.
Here are my log files after following instructions to submit a server issue. Any help is appreciated.Plex Media Server Logs_2020-01-01_11-30-48.zip (3.4 MB)
Reviewing the logs I noticed the following errors listed:
Jan 01, 2020 11:13:15.094 [15072] ERROR - SQLITE3:0xa6086fb6, 11, database corruption at line 66053 of [bf8c1b2b7a]
Jan 01, 2020 11:13:15.094 [15072] ERROR - SQLITE3:0xa6086fb6, 11, database disk image is malformed in "PRAGMA cache_size=2000"
I would recommend first trying to fix the database corruption by following the instructions in the Repair a Corrupt Database Support Article.
After the database corruption is repaired you could check to see if the tuner is listed in the media_provider_resources table in your database by using a SQLite Database Browser Tool. If the tuner is listed you could try deleting it to see if Plex will detect the tuner again.
Of course all of the above should only be done while Plex Media Server is shutdown to ensure Plex is not trying to write to the database,
Thanks for your suggestions. I followed the instructions for fixing the database corruption then checked the table you referenced for my tuner device. I found a record for my device and deleted it. This did allow Plex to discover it again and all seemed good until I stopped the plex server and restarted it. Once I did this the Live TV & DVR node again disappeared and attempting to setup the DVR again resulted in the same problem, Plex wouldn’t discover the device. I again opened the database thinking I could just delete the device record from the table but I found two records for my device. I deleted both records and attempted to fix corruption using the instructions you pointed out but received a lot of errors about records already existing. When I attempted to restart Plex I received an error stating Plex could not start. Luckily I had screen captured my library setups so I decided to follow the instructions for a nearly fresh install and deleted all the database files in the databases directory and started Plex. It started fine and rebuilt all the database. I then re-setup my libraries and DVR. I restarted Plex and all seems to be working again.
Thanks for your help. Even though your solution didn’t work, in the end I found the solution that did in the forum post you pointed out.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
