Posts: 6,810
Joined: Jul 2010
Reputation:
198
I don't think this is vnsi related. Looks more like ani issue with Kodi. I will have a look when I hopefully get some time this weekend.
Posts: 415
Joined: Jul 2011
Reputation:
2
2015-12-01, 15:16
(This post was last modified: 2015-12-01, 15:18 by username145.)
I just realised that this re-scanning of channels also broke recordings. On older builds (#1109) nothing is written to disk, on the latest build (#1130) the index/info files are written, and the TS file is 0 bytes while Kodi throws error messages about channels being locked, and continually crashing/re-connecting to server. Not sure if a Kodi log will be helpful, how do I go about getting a VDR log?
Are these new channels/new configurations non-standard in some way? If I go back to an old image containing my old channels (the same channels, just before the re-scan) it works great.
Posts: 6,810
Joined: Jul 2010
Reputation:
198
vdr writes to syslog. you get the most out of it if you set logging level of vdr to 3
Posts: 6,810
Joined: Jul 2010
Reputation:
198
you encounter this issue:
Dec 02 00:06:38 Kodi-rPi vdr[962]: [1041] ERROR: video data stream broken
Dec 02 00:06:38 Kodi-rPi vdr[962]: [1041] initiating emergency exit
Dec 02 00:06:38 Kodi-rPi vdr[962]: [962] emergency exit requested - shutting down
either cause by some plugin like "live" or issues of the dvb card or driver. I would first disable all plugins but vnsi. there are some plugins that pretend to have a decoder.
Posts: 6,810
Joined: Jul 2010
Reputation:
198
That is symbol rate and only valid for DVB-S/C. I guess it has to be zero then for DVB-T