[Marx1]

Is it possible to use VNSI only for recordings? For watching TV I use tuner built in TV, for recording planning I use web interface, the only thing I use from XBMC is watching recordings. It's nice that recordings can be scraped with XBMC and added to library, so I don't want to drop VNSI completely.

The bottom line is I have also problem with TV tuner while using XBMC (there were no problems before for a months). XBMC using VNSI constantly ping VDR for something, and tuner gets very hot (it's USB device). One tuner has been completely burnt, I replaced it for another new one and this another started to have problem. Switching off VNSI has helped and now tuner works ok.

As an alternative I can use vdrnfofs plugin.

[FernetMenta]

Wer von IBM Deutschland würde sich Ihrer Ansicht nach für das Thema interessieren?

As long as you don't watch a channel VNSI does nothing with the device. I don't think vnsi is the reason for your tuner getting hot.

[Marx1]

Maybe it's coincidence. Hovewer vnsi communicate with VDR every second - it's visible in VDR logs.

I've tried vdrnfofs and while it works ok, it doesn't work with xbmc scrapers well so isn't good alternative.

[FernetMenta]

please post a log

[Marx1]

please post a log

Here is log fragment:

Code:

Feb 21 20:43:12 wuwek vdr: [25420] VNSI: Requesting clients to reload channel list
Feb 21 20:43:12 wuwek vdr: [25420] VNSI: Requesting clients to reload channel list
Feb 21 20:43:13 wuwek vdr: [25420] VNSI: Requesting clients to reload channel list
Feb 21 20:43:31 wuwek vdr: [25420] VNSI: Requesting clients to reload channel list
Feb 21 20:43:32 wuwek vdr: [25420] VNSI: Requesting clients to reload channel list
Feb 21 20:43:32 wuwek vdr: [25420] VNSI: Requesting clients to reload channel list
Feb 21 20:43:32 wuwek vdr: [25420] VNSI: Requesting clients to reload channel list
Feb 21 20:43:32 wuwek vdr: [25420] VNSI: Requesting clients to reload channel list
Feb 21 20:43:33 wuwek vdr: [25420] VNSI: Requesting clients to reload channel list
Feb 21 20:44:13 wuwek vdr: [25420] VNSI: Requesting clients to reload channel list
Feb 21 20:44:14 wuwek vdr: [25420] VNSI: Requesting clients to reload channel list
Feb 21 20:44:14 wuwek vdr: [25420] VNSI: Requesting clients to reload channel list
Feb 21 20:44:14 wuwek vdr: [25420] VNSI: Requesting clients to reload channel list
Feb 21 20:44:14 wuwek vdr: [25420] VNSI: Requesting clients to reload channel list
Feb 21 20:44:34 wuwek vdr: [25420] VNSI: Requesting clients to reload channel list
Feb 21 20:44:35 wuwek vdr: [25420] VNSI: Requesting clients to reload channel list
Feb 21 20:44:35 wuwek vdr: [25420] VNSI: Requesting clients to reload channel list
Feb 21 20:44:35 wuwek vdr: [25420] VNSI: Requesting clients to reload channel list
Feb 21 20:44:35 wuwek vdr: [25420] VNSI: Requesting clients to reload channel list
Feb 21 20:44:36 wuwek vdr: [25420] VNSI: Requesting clients to reload channel list
Feb 21 20:45:16 wuwek vdr: [25420] VNSI: Requesting clients to reload channel list
Feb 21 20:45:17 wuwek vdr: [25420] VNSI: Requesting clients to reload channel list
Feb 21 20:45:17 wuwek vdr: [25420] VNSI: Requesting clients to reload channel list
Feb 21 20:45:17 wuwek vdr: [25420] VNSI: Requesting clients to reload channel list
Feb 21 20:45:37 wuwek vdr: [25420] VNSI: Requesting clients to reload channel list
Feb 21 20:45:38 wuwek vdr: [25420] VNSI: Requesting clients to reload channel list
Feb 21 20:45:39 wuwek vdr: [25420] VNSI: Requesting clients to reload channel list
Feb 21 20:45:39 wuwek vdr: [25420] VNSI: Requesting clients to reload channel list
Feb 21 20:46:19 wuwek vdr: [25420] VNSI: Requesting clients to reload channel list
Feb 21 20:46:19 wuwek vdr: [25420] VNSI: Requesting clients to reload channel list
Feb 21 20:46:20 wuwek vdr: [25420] VNSI: Requesting clients to reload channel list
Feb 21 20:46:40 wuwek vdr: [25420] VNSI: Requesting clients to reload channel list
Feb 21 20:46:41 wuwek vdr: [25420] VNSI: Requesting clients to reload channel list
Feb 21 20:46:41 wuwek vdr: [25420] VNSI: Requesting clients to reload channel list
Feb 21 20:46:41 wuwek vdr: [25420] VNSI: Requesting clients to reload channel list
Feb 21 20:46:42 wuwek vdr: [25420] VNSI: Requesting clients to reload channel list
Feb 21 20:47:22 wuwek vdr: [25420] VNSI: Requesting clients to reload channel list
Feb 21 20:47:22 wuwek vdr: [25420] VNSI: Requesting clients to reload channel list
Feb 21 20:47:23 wuwek vdr: [25420] VNSI: Requesting clients to reload channel list
Feb 21 20:47:23 wuwek vdr: [25420] VNSI: Requesting clients to reload channel list
Feb 21 20:47:43 wuwek vdr: [25420] VNSI: Requesting clients to reload channel list
Feb 21 20:47:44 wuwek vdr: [25420] VNSI: Requesting clients to reload channel list
Feb 21 20:47:44 wuwek vdr: [25420] VNSI: Requesting clients to reload channel list
Feb 21 20:47:44 wuwek vdr: [25420] VNSI: Requesting clients to reload channel list
Feb 21 20:47:45 wuwek vdr: [25420] VNSI: Requesting clients to reload channel list
Feb 21 20:48:25 wuwek vdr: [25420] VNSI: Requesting clients to reload channel list
Feb 21 20:48:25 wuwek vdr: [25420] VNSI: Requesting clients to reload channel list
Feb 21 20:48:26 wuwek vdr: [25420] VNSI: Requesting clients to reload channel list
Feb 21 20:48:26 wuwek vdr: [25420] VNSI: Requesting clients to reload channel list

[FernetMenta]

That means that your channels.conf changes which triggers an update in direction of XBMC. Whenever channels.conf changes there might have been a new channel added. This doesn't have any impact on the receiver.
What value do you have UpdateChannels set in setup.conf? Do yo use any other plugins which write to channels.conf? The question is what changes your channels.conf that frequently.

Note that a value of 5 for UpdateChannels (default) adds new channels automatically, like a channel scan. I use a value of 3.

[Marx1]

I also use
UpdateChannels = 3
I use VDR 1.7.28 together with

Code:

libvdr-conflictcheckonly.so.1.7.28
libvdr-epgsearch.so.1.7.28
libvdr-epgsearchonly.so.1.7.28
libvdr-iptv.so.1.7.28
libvdr-live.so.1.7.28
libvdr-markad.so.1.7.28
libvdr-noepg.so.1.7.28
libvdr-quickepgsearch.so.1.7.28
libvdr-streamdev-server.so.1.7.28
libvdr-svdrpservice.so.1.7.28
libvdr-vnsiserver.so.1.7.28

In my channels.conf I have DVB-T channels (working) and DVB-S channels (not working because device is disconnected currently). Maybe those unused but active channels causes problem? Or maybe there is newer VNSI than 14.01.2013 23:09?

[FernetMenta]

There's one weakness in the code of vnsi which may cause the channels.conf to be updated that often. Querying the modified flag of channles.conf does reset the flag. I need to think about a better solution for this.

[Marx1]

I will be happy to test it once finished