vnsi Recordings state changed.......
#31
Hi FernetMenta

Thanks for the fix an the fast reply

compiled and installed it right away
Looks good at the first glance testing on my macbook
Will run a more detailed test on the main livingroom client running kodibuntu tomorrow

Thanks again for your support
This community is simply awesome :-)

Martin
vdr 2.2.0 (yavdr/unstable-vdr) / TBS 6991 dvbs-2 - Twin Tuner plus CI / vdr-plugin-vnsiserver 1.3.0 (FernetMenta's GIT) / Ubuntu 14.04 LTS
Zotac CI520 / kodibuntu 14.04 / Helix 14.1 stable, vdr addon 1.9.23 (Opdenkamp's GIT), Skin Rapier 7.2.0
MacBook Pro / OSX 10.10 / Helix 14.1 stable, vdr addon 1.9.23 (Opdenkamp's GIT), Skin Rapier 7.2.0
MySQL MediaDB
Reply
#32
It seems I was bit hasty in claiming that upgrading VDR to 2.1.6 would fix the EPG issues.
While the "state changed" messages are gone, syslog is filled with lines stating
VNSI: Trigger EPG update for channel XYZ
Syslog clip here: http://pastebin.ca/2904241

The EPG triggers seem to occur every 10 seconds, one line for each channel in the channel list.
.
VDR seems to die semi frequently as well, not sure if that is related. I still have the debug lines in the VNSI module:
"
Jan 12 20:56:17 torni vdr: [28534] registered source parameters for 'A - ATSC'
Jan 12 20:56:17 torni vdr: [28534] registered source parameters for 'C - DVB-C'
Jan 12 20:56:17 torni vdr: [28534] registered source parameters for 'S - DVB-S'
Jan 12 20:56:17 torni vdr: [28534] registered source parameters for 'T - DVB-T'
Jan 12 20:56:17 torni vdr: [28534] probing /dev/dvb/adapter0/frontend0
Jan 12 20:56:17 torni vdr: [28534] creating cDvbDevice
Jan 12 20:56:17 torni vdr: [28534] new device number 1
Jan 12 20:56:17 torni vdr: [28535] video directory scanner thread started (pid=28534, tid=28535, prio=high)
Jan 12 20:56:17 torni vdr: [28537] epg data reader thread started (pid=28534, tid=28537, prio=high)
Jan 12 20:56:17 torni vdr: [28537] reading EPG data from /var/cache/vdr/epg.data
Jan 12 20:56:17 torni vdr: [28536] video directory scanner thread started (pid=28534, tid=28536, prio=high)
Jan 12 20:56:17 torni vdr: [28536] --------------- marker 3
Jan 12 20:56:17 torni vdr: [28536] video directory scanner thread ended (pid=28534, tid=28536)
Jan 12 20:56:17 torni vdr: [28535] --------------- marker 4
Jan 12 20:56:17 vdr: last message repeated 8 times
Jan 12 20:56:17 torni vdr: [28535] video directory scanner thread ended (pid=28534, tid=28535)
Jan 12 20:56:17 torni vdr: [28537] epg data reader thread ended (pid=28534, tid=28537)
"

The same VNSI EPG trigger update seem to affect also others:
http://www.vdr-portal.de/board16-video-d...r-problem/
http://www.vdr-portal.de/board16-video-d...g-problem/

Please let me know if I can help in debuggin this further.
Reply
#33
Do you allow epg updates during playback?
Reply
#34
No,I have "Prevent EPG updates during playback" selected.
Reply
#35
(2015-01-13, 20:32)salose Wrote: No,I have "Prevent EPG updates during playback" selected.

Exactly this is the problem. With this enabled PVR does not grab the updates and vnsi sends it again. Why do you have this enabled? IMO this setting is obsolete after backends were enabled to trigger updates.

I think I need to patch the generic PVR parts to get this right.
Reply
#36
I guess I have it selected as long time ago with MythTV EPG scanning during playback was causing issues. (= years ago, different HW & SW).
However, changing the "Prevent EPG updates during playback" has no effect on the VNSI: Trigger EPG update for channel XYZ messages,
I get one line in syslog for each channel in my channels.conf (just for TV channels) every 10 seconds.
Reply
#37
Really for each channel or just for particular ones? The logic is is follows:

- vnsi checks the time vdr las modified EPG
- if this time is later than last processing + 10 seconds, vnsi processes updates
- for every channel vnsi checks EPG start time for the last entry in the table
- if this time is later than last update time stored with this channel, vnsi triggers an update
- when pvr requests an EPG update for a channel, vnsi stores time of last EPG entry for this channel
Reply
#38
EPG update triggers happen for all channels I have in channels.conf.
I'm not sure if it is in any way related, but quite often the OSD timer that shows how much of the program currently playing has passed (on left side of the progress bar) is jumping back and forward few seconds very rapidly. The actual video stream does not seem to be affected.
Reply
#39
Does this also happen when nothing is playing?
Reply
#40
I just checked, and EPG update triggers occur even if I close kodi completely (but I may have other kodi clients running in the network, but they are not playing anything).
Does the VNSI VDR plugin have some kind of logging that I could enable?
I recreated my channesl.conf just to be sure that it wasnt corrupt, but that had no effect.
Reply
#41
The update messages in syslog are per connected client. So if you close one client, other still get updates. can you try with a single client?

I already have some ideas but more data would be great to understand the issue.
Reply
#42
@salose can you try this my epg branch?
https://github.com/FernetMenta/vdr-plugi...r/tree/epg

it stops triggering epg updates if the client does not fetch epg
Reply
#43
Done. Now I get this in the syslog instead of the EPG update trigger messages:

Jan 21 23:29:59 torni vdr: [19092] status: cStatusTest::ChannelSwitch 1 0 0
Jan 21 23:29:59 torni vdr: [19092] status: cStatusTest::ChannelSwitch 1 1 0
Jan 21 23:30:00 torni vdr: [19100] frontend 1/0 lost lock on channel 1, tp 562
Jan 21 23:30:00 torni vdr: [19100] frontend 1/0 regained lock on channel 1, tp 562
Jan 21 23:30:05 torni vdr: [19101] changing pids of channel 2 from 513+513=2:660=fin@4:2027=fin,2050=dut:5000 to 513+513=2:660=fin@4,664=dut@4:2027=fin,2050=dut:5000
Jan 21 23:30:20 torni vdr: [19092] status: cStatusTest::ChannelSwitch 1 0 0
Jan 21 23:30:20 torni vdr: [19092] status: cStatusTest::ChannelSwitch 1 3 0
Jan 21 23:30:41 torni vdr: [19092] status: cStatusTest::ChannelSwitch 1 0 0
Jan 21 23:30:41 torni vdr: [19092] status: cStatusTest::ChannelSwitch 1 14 0
Jan 21 23:31:02 torni vdr: [19092] status: cStatusTest::ChannelSwitch 1 0 0
Jan 21 23:31:02 torni vdr: [19092] status: cStatusTest::ChannelSwitch 1 19 0
Jan 21 23:31:23 torni vdr: [19092] status: cStatusTest::ChannelSwitch 1 0 0
Jan 21 23:31:23 torni vdr: [19092] status: cStatusTest::ChannelSwitch 1 1 0
Jan 21 23:31:44 torni vdr: [19092] status: cStatusTest::ChannelSwitch 1 0 0
Jan 21 23:31:44 torni vdr: [19092] status: cStatusTest::ChannelSwitch 1 3 0
Jan 21 23:32:05 torni vdr: [19092] status: cStatusTest::ChannelSwitch 1 0 0
Jan 21 23:32:05 torni vdr: [19092] status: cStatusTest::ChannelSwitch 1 14 0
Jan 21 23:32:26 torni vdr: [19092] status: cStatusTest::ChannelSwitch 1 0 0
Jan 21 23:32:26 torni vdr: [19092] status: cStatusTest::ChannelSwitch 1 19 0
Jan 21 23:32:47 torni vdr: [19092] status: cStatusTest::ChannelSwitch 1 0 0
Jan 21 23:32:47 torni vdr: [19092] status: cStatusTest::ChannelSwitch 1 1 0
Jan 21 23:33:08 torni vdr: [19092] status: cStatusTest::ChannelSwitch 1 0 0
Jan 21 23:33:08 torni vdr: [19092] status: cStatusTest::ChannelSwitch 1 3 0

I disable the other Kodi instance in the network. It had no effect on as far as I could notice.
Reply
#44
Those are no vnsi messages. Can you try to find out what other plugin is causing them?

EDIT: those messages come from vdr's status plugin. I don't see anything wrong here. vdr most likely switches channels for EPG scan.
Reply
#45
So having syslog filled with these cStatusTest::ChannelSwitch messages is normal behaviour? I seem to be getting four of them every 20 seconds.
Anyway, thanks for the EPG fix.
Reply

Logout Mark Read Team Forum Stats Members Help
vnsi Recordings state changed.......0