VDR Streamdev Plugin

Which priority is configured in the streamdev-client setup? If the value is negativ, the client is not allowed to switch channels on the server unless live TV on the server is suspended

schmirl wrote:

Which priority is configured in the streamdev-client setup? If the value is negativ, the client is not allowed to switch channels on the server unless live TV on the server is suspended

Hi,
It's 0. When there is no recording running on the server, the client can switch to any channel.
Peter

There should be "Streamdev: No device provides channel ... at priority ..." messages in the server log (VDR must be run with full logging, i.e. without -l switch or with -l 3). Would be interesting to see the priorities of the other devices in this case. You could install the peer plugin to see the priorities (peer must be installed on server and client, svdrpservice on the client. In the peer setup on the client you need to configure the server. The server must allow SVDRP connections from the client).

Hi,
I don't get any messages on the server, but on the client I get these lines when trying to switch to a channel, that should be available:

vdr: [29180] [vdr-fe] Keypress: XKeySym KP_2
vdr: [29174] [xine..put] cXinelibOsd::CanHandleAreas(): Device does not support ARGB
vdr: [29174] switching to channel 2
vdr: [29174] info: Channel not available!
vdr: [29174] switching to channel 1

Perhaps it has nothing to do with streamdev, but with vdr itself: the client vdr sees, that channel 1 is being recorded. It sees the same channel.conf and the same timers.conf, but perhaps it does not know, that channel 2 is on another dvb-device, so the client thinks, that switching to channel 2 won't be possible and it does not even try. What do you think?

Thanks for your efforts, Peter

Yes, indeed, that's the problem!

I've just changed the client setup, so that the client sees an empty timers.conf: now it no more thinks, that there is a recording running and all channels are available!

Sorry for the noise, Peter

schmirl wrote:

Oh - so your client and server were both recording the same programme?

No. Only the server can record. For the client all files and directories are read-only (nfs-mounted). This way, we can watch all recordings of the server and see the timers, but the client cannot do any harm.

Now, we can no more see the timers of the server, but we can switch to more channels, when the server is recording. That's ok.

Peter

Hi Peter,

you could install my remotetimers plugin from http://vdr.schmirler.de. To keep anyone from doing changes, enable the plugin setup option to hide the mainmenu and use a skin which shows a timer list in the mainmenu. Skinnopacity has builtin support for remotetimers, for skinlcars the remotetimers sources include a patch.

Regards,
Frank

schmirl wrote:

you could install my remotetimers plugin from http://vdr.schmirler.de.

This is no more necessary: I've installed VDRAdmin-AM, where I can see the timers and much more.
Nevertheless thanks for your efforts, Peter