How to disable PLEX PVR so it does not takes my TV tuner?




I have a QNAP TS-453A NAS with the TVButler tuner which I was using just fine with DVBLink, but since Plex started including the PVR option, I can't have both services enabled at the same time as before, which I'd like...

I want to use DVBLink server for TV and the rest with Plex, but now it turns out I can't use both at the same time because I couldn't find an option in Plex to disable the PVR part so it does not "takes" the TV tuner, resulting in DVBLink not being able to use it.

Any ideas?

Thank you in advance!


Cant you just Delete the DVR from your Plex?


Ok, forget about it. Thanks to nokdim’s answer I was checking more deeply the Plex options because couldn’t find it, and found instead an old plugin I had installed related with DVBLink and Plex. Uninstalled and fixed :slight_smile:


Ok false alarm, it is still happening and I don’t have the option showed by nokdim as you need a Plex Pass to use it… which I don’t have, so there is nothing to disable it.


Ok I think I have found a “dirty” way to avoid Plex loading the Tuner service…

First I have confirmed in the logs it was taking my Tuner device:
[/share/CE_CACHEDEV1_DATA/.qpkg/PlexMediaServer] # cat /share/CE_CACHEDEV1_DATA/.qpkg/PlexMediaServer/Library/Plex\ Media\ Server/Logs/Plex\ Tuner\ Service.1.log Sep 13, 2017 11:50:21.946 [0x7fa85fc1f700] INFO - Plex Tuner Service v1.0.0.0 - unknown PC unknown - build: Sep 13, 2017 11:50:21.947 [0x7fa85fc1f700] INFO - Linux version: 4.2.8 (#1 SMP Fri Sep 1 01:08:22 CST 2017), language: en-US Sep 13, 2017 11:50:21.947 [0x7fa85fc1f700] INFO - Processor Intel(R) Celeron(R) CPU N3160 @ 1.60GHz Sep 13, 2017 11:50:21.947 [0x7fa85fc1f700] INFO - /share/CE_CACHEDEV1_DATA/.qpkg/PlexMediaServer/Plex Tuner Service /share/CE_CACHEDEV1_DATA/.qpkg/PlexMediaServer/Resources/Tuner/Private /share/CE_CACHEDEV1_DATA/.qpkg/PlexMediaServer/Resources/Tuner/Shared 32600 /waitmutex Sep 13, 2017 11:50:21.937 [0x7fa864b9f780] INFO - * broker_t::start... ... Sep 13, 2017 11:50:27.923 [0x7fa85f067700] INFO - * dvb_device_factory_t::get_device_list. Id dvb#tvbutler#0#1:4, Name DVBLogic TVButler DVB-C/T/T2 (100tc), Standards 3 Sep 13, 2017 11:50:27.923 [0x7fa85f067700] INFO - * device_manager_t::get_device_list. Device DVBLogic TVButler DVB-C/T/T2 (100tc), id dvb#tvbutler#0#1:4, tuners 1, state 0, standards 3 Sep 13, 2017 11:50:27.926 [0x7fa85f643700] INFO - * web_service_t::process_device_status ...

I’ve checked the different Plex’s services running and located the binaries:
-rwxrwxr-x 1 admin administ 3952056 Sep 7 13:40 Plex DLNA Server* -rwxrwxr-x 1 admin administ 4807920 Sep 7 13:40 Plex Media Scanner* -rwxrwxr-x 1 admin administ 14653208 Sep 7 13:40 Plex Media Server* -rwxrwxr-x 1 admin administ 19440984 Sep 7 13:40 Plex Media Server Tests* -rwxrwxr-x 1 admin administ 886536 Sep 7 13:40 Plex Relay* -rwxr-xr-x 1 admin administ 5048 Sep 7 13:40 Plex Script Host* -rwxrwxr-x 1 admin administ 12988064 Sep 7 13:40 Plex Transcoder* -rwxrwxr-x 1 admin administ 5354736 Sep 7 13:40 Plex Tuner Service*

And checked the start script in /etc/init.d/ hoping i could edit it and remove the part responsible for launching the TV Tuner part but, it seems to be calling out just the “Plex Media Server” binary and not the other ones, so I guess that one is the responsible for executing the rest of the services…

So since I couldn’t find where exactly the “Plex Tuner Service” service is called, I have simply renamed it to “Plex Tuner Service.back” and now it won’t find it. Everything else seems to be working without any issues and now I have no conflict with DVBLink, but it seems to me a very “dirty” way of doing it, so maybe there is a better one I couldn’t find?



That is super dirty and I bet when you upgrade it will reinstall that and you will have to rename again…

If you had an IP based tuner I would suggest this:

route add -host x.x.x.x/32 reject

x.x.x.x being your tuner IP this way plex will not be able to get to the tuner so you dont have to mess with renaming.


Thank you for the answer nokdim!

Yes, that will happen when updating for sure… The thing is the tuner is not an IP one and it is connected directly to the NAS USB, so that won’t work for me :frowning: