Hi all,
I would like to run my headless VDR without a primary DVB (or suspended output) but keep xineliboutput running. I can't figure out how.
My VDR has 4 receivers (2x Astra, 2x Hotbird) without MPEG decoder. It runs vnsiserver (for my Kodi client), streamdev-server (for some browser / VLC clients) and xineliboutput (because it's sometimes useful to have access to the VDR console via remote). Alas, xineliboutput will always be the primary DVB device and block a receiver, which is nasty when VDR is recording on one bouquet, xineliboutput blocks another bouquet and I want to watch live TV on just another bouquet, all on the same satellite.
Can I use the suspendoutput plugin while keeping xineliboutput active so that I can access it with vdr-sxfe when needed?
TIA!
(I could "park" xineliboutput on an arbitrary hotbird channel though but I'd like to have it automated ...)
Hi!
I never tried it myself, but isn't vdr-dummydevice used for that?
http://phivdr.dyndns.org/vdr/vdr-dummydevice/
Regards, Stephan.
Am 12/20/2016 um 05:05 PM schrieb Harald Milz:
I would like to run my headless VDR without a primary DVB (or suspended output) but keep xineliboutput running. I can't figure out how.
On Tue, Dec 20, 2016 at 06:09:46PM +0100, Stephan Loescher wrote:
Hi!
I never tried it myself, but isn't vdr-dummydevice used for that?
Hmmm, it seems xineliboutput doesn't like not being the primary:
Dec 21 14:39:38 vdr vdr: [3419] [xine..put] Dropping client: xineliboutput is not the primary device !
I think I'll park the primary at a hotbird channel via SVDRP / cron for now.
Hi,
I use these config parameters for xineliboutput plugin
--local=none --primary --remote=0.0.0.0:37890
in MLD 5.1.
I have no local OSD because of using VDR as server, and I can use it on my Ubuntus as a remote display/client using vdr-sxfe...
-Wanninger
---
Am 21.12.2016 um 14:42 schrieb Harald Milz:
On Tue, Dec 20, 2016 at 06:09:46PM +0100, Stephan Loescher wrote:
Hi!
I never tried it myself, but isn't vdr-dummydevice used for that?
Hmmm, it seems xineliboutput doesn't like not being the primary:
Dec 21 14:39:38 vdr vdr: [3419] [xine..put] Dropping client: xineliboutput is not the primary device !
I think I'll park the primary at a hotbird channel via SVDRP / cron for now.
-- This message was scanned by ESVA and is believed to be clean.
On Wed, Dec 21, 2016 at 03:14:29PM +0100, Niedermeier Günter wrote:
I use these config parameters for xineliboutput plugin
--local=none --primary --remote=0.0.0.0:37890
Yup, me too. In this case xineliboutput will be the primary display, and there will always be a channel running on it. Which is the root cause of my problem. If you omit --primary, xineliboutput will claim primary on its own if there is no other output device, which is the case when you have a receiver-only sat card.
That's right.
I use two ways to solve that issue:
1. for example, tune VDR to a non existant iptv channel or another one, which does not use DVB ressources. 2. use of vdr-plugin-suspendoutput - works also fine for me
---
Am 21.12.2016 um 16:36 schrieb Harald Milz:
On Wed, Dec 21, 2016 at 03:14:29PM +0100, Niedermeier Günter wrote:
I use these config parameters for xineliboutput plugin
--local=none --primary --remote=0.0.0.0:37890
Yup, me too. In this case xineliboutput will be the primary display, and there will always be a channel running on it. Which is the root cause of my problem. If you omit --primary, xineliboutput will claim primary on its own if there is no other output device, which is the case when you have a receiver-only sat card.
-- This message was scanned by ESVA and is believed to be clean.
Hi Harald!
Yes, xineliboutput always wants to be the primary. But you can change that online via SVDRP:
plug xineliboutput prim NUMBER
With that you can switch the primary device to another one.
Regards, Stephan.
Am 12/21/2016 um 02:42 PM schrieb Harald Milz:
On Tue, Dec 20, 2016 at 06:09:46PM +0100, Stephan Loescher wrote:
Hi!
I never tried it myself, but isn't vdr-dummydevice used for that?
Hmmm, it seems xineliboutput doesn't like not being the primary:
Dec 21 14:39:38 vdr vdr: [3419] [xine..put] Dropping client: xineliboutput is not the primary device !
I think I'll park the primary at a hotbird channel via SVDRP / cron for now.
ti, 2016-12-20 kello 17:05 +0100, Harald Milz kirjoitti:
Hi all,
I would like to run my headless VDR without a primary DVB (or suspended output) but keep xineliboutput running. I can't figure out how.
There was a bug in xineliboutput automatic primary device switching. It should be fixed in sourceforge git.
My VDR has 4 receivers (2x Astra, 2x Hotbird) without MPEG decoder. It runs vnsiserver (for my Kodi client), streamdev-server (for some browser / VLC clients) and xineliboutput (because it's sometimes useful to have access to the VDR console via remote). Alas, xineliboutput will always be the primary DVB device and block a receiver, which is nasty when VDR is recording on one bouquet, xineliboutput blocks another bouquet and I want to watch live TV on just another bouquet, all on the same satellite.
Can I use the suspendoutput plugin while keeping xineliboutput active so that I can access it with vdr-sxfe when needed?
Yes, that was one of the reasons why it was written.
Recent xineliboutput can trigger suspendoutput automatically when vdr- sxfe is disconnected (this could use some testing ...). See --auto- suspend option.
TIA!
(I could "park" xineliboutput on an arbitrary hotbird channel though but I'd like to have it automated ...)
Recent xineliboutput can trigger suspendoutput automatically when vdr- sxfe is disconnected (this could use some testing ...). See --auto- suspend option.
Is it enough to replace the xineliboutput plugin with the latest git-version and start the plugin it with "-s" parameter, or must I do further things?
Only updating the xineliboutput plugin does not trigger autosuspend yet. (At least in my environment)
-Wanninger
-- This message was scanned by ESVA and is believed to be clean.
ti, 2017-01-17 kello 17:37 +0100, Niedermeier Günter kirjoitti:
Recent xineliboutput can trigger suspendoutput automatically when vdr- sxfe is disconnected (this could use some testing ...). See --auto- suspend option.
Is it enough to replace the xineliboutput plugin with the latest git- version and start the plugin it with "-s" parameter, or must I do further things?
You need also recent vdr-suspedoutput plugin loaded: https://phivdr.dyndns.org/vdr/vdr-suspendoutput/vdr-suspendoutput-2.1.0 .tgz
Only updating the xineliboutput plugin does not trigger autosuspend yet. (At least in my environment)
Was there anything in the log when vdr-sxfe was started / stopped ?
It should trigger suspendoutput when there are no clients, and disable it when a client connects. But, as said, this is not much tested feature :)
-Wanninger
-- This message was scanned by ESVA and is believed to be clean.
vdr mailing list vdr@linuxtv.org https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
-
Harald Milz -
Niedermeier Günter -
Petri Hintukainen -
Stephan Loescher