Open fsironman opened 7 years ago
did you try "Avoid EPG scan while streaming"?
Thx for the quick answer.
In my setup.conf there was no entry.
I was reading up a bit and there's a commit with saying its the default setting doesn't that mean it should already be active or is it only the default value for the the config tool which gets written into the setup.conf
2015-09-18: Version 1.3.0 [...]
- make avoid EPG scan while streaming default
Nevertheless I went into the VDR config and saved it:
cat /var/lib/vdr/setup.conf | grep vnsi
vnsiserver.AvoidEPGScan = 1
vnsiserver.DisableCamBlacklist = 0
vnsiserver.DisableScrambleTimeout = 0
vnsiserver.GroupRecordings = 1
vnsiserver.PlayRecording = 0
vnsiserver.PmtTimeout = 0
vnsiserver.Timeshift = 0
vnsiserver.TimeshiftBufferDir =
vnsiserver.TimeshiftBufferFileSize = 6
vnsiserver.TimeshiftBufferSize = 5
So for now I can just wait to see if it happens again or not.
Update: the problem still persists Heres the log with vdr loglevel 3: https://pastebin.com/7qzZWakv
What I can see from the log: Its always the same device VNSI picks 0x269f4e0 (2) when the error occurs. This device returns no data from anywhere from 40 sec to 6 min when it happens.
Switching channels during this time works as long as VNSI select another device for the channel.
Aug 13 01:36:39 easyvdr vdr: [25862] VNSI: Successfully found following device: 0x269f4e0 (2) for receiving, priority=0
Aug 13 01:36:39 easyvdr vdr: [25862] VNSI: Successfully switched to channel 1 - Das Erste HD
Aug 13 01:36:43 easyvdr vdr: [26019] VNSI: Channel: no data 16
Aug 13 01:36:47 easyvdr vdr: [25862] VNSI: Successfully found following device: 0x265d9e0 (1) for receiving, priority=0
Aug 13 01:36:47 easyvdr vdr: [25862] VNSI: Successfully switched to channel 4 - RTL Television
<- WORKING->
Aug 13 01:36:54 easyvdr vdr: [25862] VNSI: Successfully found following device: 0x269f4e0 (2) for receiving, priority=0
Aug 13 01:36:54 easyvdr vdr: [25862] VNSI: Successfully switched to channel 52 - Disney Channel
Aug 13 01:36:56 easyvdr vdr: [26023] VNSI: Channel: no data 16
So it seems that the device might be blocked by something? Also let me know if I'm wrong here and this a VDR related and not necessarily the VNSI plugin
This is not the complete log as pastebin limits the filesize
I did the following to show the errors over the course of the day:
grep -B 11 'no data' vdr2.log | egrep 'no data|Successfully' | grep -A 2 device
Aug 12 14:18:03 easyvdr vdr: [23827] VNSI: Successfully found following device: 0x21e4710 (2) for receiving, priority=5
Aug 12 14:18:04 easyvdr vdr: [23827] VNSI: Successfully switched to channel 12 - ONE HD
Aug 12 14:18:05 easyvdr vdr: [23832] VNSI: Channel: no data 16
--
Aug 12 18:47:52 easyvdr vdr: [24838] VNSI: Successfully found following device: 0x269f4e0 (2) for receiving, priority=0
Aug 12 18:47:52 easyvdr vdr: [24838] VNSI: Successfully switched to channel 12 - ONE HD
Aug 12 18:47:54 easyvdr vdr: [25196] VNSI: Channel: no data 16
--
Aug 12 18:47:59 easyvdr vdr: [24838] VNSI: Successfully found following device: 0x269f4e0 (2) for receiving, priority=0
Aug 12 18:47:59 easyvdr vdr: [24838] VNSI: Successfully switched to channel 11 - DMAX
Aug 12 18:48:01 easyvdr vdr: [25199] VNSI: Channel: no data 16
--
Aug 12 18:48:19 easyvdr vdr: [24838] VNSI: Successfully found following device: 0x269f4e0 (2) for receiving, priority=0
Aug 12 18:48:19 easyvdr vdr: [24838] VNSI: Successfully switched to channel 1 - Das Erste HD
Aug 12 18:48:21 easyvdr vdr: [25202] VNSI: Channel: no data 16
--
Aug 12 18:48:25 easyvdr vdr: [24838] VNSI: Successfully found following device: 0x269f4e0 (2) for receiving, priority=0
Aug 12 18:48:25 easyvdr vdr: [24838] VNSI: Successfully switched to channel 2 - ZDF HD
Aug 12 18:48:27 easyvdr vdr: [25205] VNSI: Channel: no data 16
--
Aug 12 18:48:32 easyvdr vdr: [24838] VNSI: Successfully found following device: 0x269f4e0 (2) for receiving, priority=0
Aug 12 18:48:32 easyvdr vdr: [24838] VNSI: Successfully switched to channel 3 - SAT.1
Aug 12 18:48:34 easyvdr vdr: [25208] VNSI: Channel: no data 16
Aug 12 18:49:58 easyvdr vdr: [24838] VNSI: Successfully found following device: 0x269f4e0 (2) for receiving, priority=0
Aug 12 18:49:58 easyvdr vdr: [24838] VNSI: Successfully switched to channel 11 - DMAX
Aug 12 18:50:00 easyvdr vdr: [25212] VNSI: Channel: no data 16
--
Aug 12 18:50:08 easyvdr vdr: [24838] VNSI: Successfully found following device: 0x269f4e0 (2) for receiving, priority=0
Aug 12 18:50:08 easyvdr vdr: [24838] VNSI: Successfully switched to channel 3 - SAT.1
Aug 12 18:50:10 easyvdr vdr: [25215] VNSI: Channel: no data 16
--
Aug 12 18:50:35 easyvdr vdr: [24838] VNSI: Successfully found following device: 0x269f4e0 (2) for receiving, priority=0
Aug 12 18:50:35 easyvdr vdr: [24838] VNSI: Successfully switched to channel 3 - SAT.1
Aug 12 18:50:37 easyvdr vdr: [25221] VNSI: Channel: no data 16
--
Aug 12 21:20:48 easyvdr vdr: [25255] VNSI: Successfully found following device: 0x269f4e0 (2) for receiving, priority=0
Aug 12 21:20:48 easyvdr vdr: [25255] VNSI: Successfully switched to channel 41 - rhein main tv
Aug 12 21:20:50 easyvdr vdr: [25458] VNSI: Channel: no data 16
--
Aug 12 21:20:56 easyvdr vdr: [25255] VNSI: Successfully found following device: 0x269f4e0 (2) for receiving, priority=0
Aug 12 21:20:56 easyvdr vdr: [25255] VNSI: Successfully switched to channel 42 - Schau TV
Aug 12 21:20:58 easyvdr vdr: [25461] VNSI: Channel: no data 16
--
Aug 12 21:21:14 easyvdr vdr: [25255] VNSI: Successfully found following device: 0x269f4e0 (2) for receiving, priority=0
Aug 12 21:21:14 easyvdr vdr: [25255] VNSI: Successfully switched to channel 6 - ProSieben
Aug 12 21:21:16 easyvdr vdr: [25465] VNSI: Channel: no data 16
--
Aug 12 21:21:44 easyvdr vdr: [25255] VNSI: Successfully found following device: 0x269f4e0 (2) for receiving, priority=0
Aug 12 21:21:44 easyvdr vdr: [25255] VNSI: Successfully switched to channel 8 - kabel eins
Aug 12 21:21:46 easyvdr vdr: [25469] VNSI: Channel: no data 16
--
Aug 12 21:22:10 easyvdr vdr: [25255] VNSI: Successfully found following device: 0x269f4e0 (2) for receiving, priority=0
Aug 12 21:22:10 easyvdr vdr: [25255] VNSI: Successfully switched to channel 6 - ProSieben
Aug 12 21:22:12 easyvdr vdr: [25474] VNSI: Channel: no data 16
--
Aug 12 21:22:26 easyvdr vdr: [25255] VNSI: Successfully found following device: 0x269f4e0 (2) for receiving, priority=0
Aug 12 21:22:26 easyvdr vdr: [25255] VNSI: Successfully switched to channel 3 - SAT.1
Aug 12 21:22:28 easyvdr vdr: [25479] VNSI: Channel: no data 16
--
Aug 12 21:22:52 easyvdr vdr: [25255] VNSI: Successfully found following device: 0x269f4e0 (2) for receiving, priority=0
Aug 12 21:22:52 easyvdr vdr: [25255] VNSI: Successfully switched to channel 6 - ProSieben
Aug 12 21:22:54 easyvdr vdr: [25484] VNSI: Channel: no data 16
--
Aug 12 21:24:47 easyvdr vdr: [25255] VNSI: Successfully found following device: 0x269f4e0 (2) for receiving, priority=0
Aug 12 21:24:47 easyvdr vdr: [25255] VNSI: Successfully switched to channel 44 - Welt der Wunder
Aug 12 21:24:49 easyvdr vdr: [25496] VNSI: Channel: no data 16
--
Aug 12 21:24:56 easyvdr vdr: [25255] VNSI: Successfully found following device: 0x269f4e0 (2) for receiving, priority=0
Aug 12 21:24:56 easyvdr vdr: [25255] VNSI: Successfully switched to channel 8 - kabel eins
Aug 12 21:24:58 easyvdr vdr: [25500] VNSI: Channel: no data 16
--
Aug 12 21:26:00 easyvdr vdr: [25255] VNSI: Successfully found following device: 0x269f4e0 (2) for receiving, priority=0
Aug 12 21:26:00 easyvdr vdr: [25255] VNSI: Successfully switched to channel 6 - ProSieben
Aug 12 21:26:02 easyvdr vdr: [25507] VNSI: Channel: no data 16
--
Aug 12 21:26:12 easyvdr vdr: [25255] VNSI: Successfully found following device: 0x269f4e0 (2) for receiving, priority=0
Aug 12 21:26:12 easyvdr vdr: [25255] VNSI: Successfully switched to channel 52 - Disney Channel
Aug 12 21:26:14 easyvdr vdr: [25511] VNSI: Channel: no data 16
--
Aug 12 21:26:22 easyvdr vdr: [25255] VNSI: Successfully found following device: 0x269f4e0 (2) for receiving, priority=0
Aug 12 21:26:22 easyvdr vdr: [25255] VNSI: Successfully switched to channel 50 - KiKA HD
Aug 12 21:26:24 easyvdr vdr: [25518] VNSI: Channel: no data 16
--
Aug 12 21:26:32 easyvdr vdr: [25255] VNSI: Successfully found following device: 0x269f4e0 (2) for receiving, priority=0
Aug 12 21:26:33 easyvdr vdr: [25255] VNSI: Successfully switched to channel 49 - Eurosport Deutschland
Aug 12 21:26:34 easyvdr vdr: [25520] VNSI: Channel: no data 16
--
Aug 12 21:26:43 easyvdr vdr: [25255] VNSI: Successfully found following device: 0x269f4e0 (2) for receiving, priority=0
Aug 12 21:26:43 easyvdr vdr: [25255] VNSI: Successfully switched to channel 48 - SPORT1
Aug 12 21:26:45 easyvdr vdr: [25523] VNSI: Channel: no data 16
--
Aug 13 01:35:26 easyvdr vdr: [25862] VNSI: Successfully found following device: 0x269f4e0 (2) for receiving, priority=0
Aug 13 01:35:26 easyvdr vdr: [25862] VNSI: Successfully switched to channel 47 - ORF2E
Aug 13 01:35:28 easyvdr vdr: [25992] VNSI: Channel: no data 16
--
Aug 13 01:35:33 easyvdr vdr: [25862] VNSI: Successfully found following device: 0x269f4e0 (2) for receiving, priority=0
Aug 13 01:35:33 easyvdr vdr: [25862] VNSI: Successfully switched to channel 46 - Zee One HD
Aug 13 01:35:35 easyvdr vdr: [25995] VNSI: Channel: no data 16
--
Aug 13 01:35:43 easyvdr vdr: [25862] VNSI: Successfully found following device: 0x269f4e0 (2) for receiving, priority=0
Aug 13 01:35:43 easyvdr vdr: [25862] VNSI: Successfully switched to channel 1 - Das Erste HD
Aug 13 01:35:45 easyvdr vdr: [25999] VNSI: Channel: no data 16
--
Aug 13 01:35:49 easyvdr vdr: [25862] VNSI: Successfully found following device: 0x269f4e0 (2) for receiving, priority=0
Aug 13 01:35:49 easyvdr vdr: [25862] VNSI: Successfully switched to channel 2 - ZDF HD
Aug 13 01:35:51 easyvdr vdr: [26002] VNSI: Channel: no data 16
--
Aug 13 01:35:54 easyvdr vdr: [25862] VNSI: Successfully found following device: 0x269f4e0 (2) for receiving, priority=0
Aug 13 01:35:54 easyvdr vdr: [25862] VNSI: Successfully switched to channel 3 - SAT.1
Aug 13 01:35:56 easyvdr vdr: [26005] VNSI: Channel: no data 16
--
Aug 13 01:36:17 easyvdr vdr: [25862] VNSI: Successfully found following device: 0x269f4e0 (2) for receiving, priority=0
Aug 13 01:36:17 easyvdr vdr: [25862] VNSI: Successfully switched to channel 44 - Welt der Wunder
Aug 13 01:36:19 easyvdr vdr: [26010] VNSI: Channel: no data 16
--
Aug 13 01:36:21 easyvdr vdr: [25862] VNSI: Successfully found following device: 0x269f4e0 (2) for receiving, priority=0
Aug 13 01:36:21 easyvdr vdr: [25862] VNSI: Successfully switched to channel 45 - BBC World News Europe HD
Aug 13 01:36:23 easyvdr vdr: [26013] VNSI: Channel: no data 16
--
Aug 13 01:36:39 easyvdr vdr: [25862] VNSI: Successfully found following device: 0x269f4e0 (2) for receiving, priority=0
Aug 13 01:36:39 easyvdr vdr: [25862] VNSI: Successfully switched to channel 1 - Das Erste HD
Aug 13 01:36:41 easyvdr vdr: [26019] VNSI: Channel: no data 16
--
Aug 13 01:36:54 easyvdr vdr: [25862] VNSI: Successfully found following device: 0x269f4e0 (2) for receiving, priority=0
Aug 13 01:36:54 easyvdr vdr: [25862] VNSI: Successfully switched to channel 52 - Disney Channel
Aug 13 01:36:56 easyvdr vdr: [26023] VNSI: Channel: no data 16
--
Aug 13 01:36:59 easyvdr vdr: [25862] VNSI: Successfully found following device: 0x269f4e0 (2) for receiving, priority=0
Aug 13 01:36:59 easyvdr vdr: [25862] VNSI: Successfully switched to channel 51 - Nickelodeon
Aug 13 01:37:01 easyvdr vdr: [26026] VNSI: Channel: no data 16
--
Aug 13 01:37:05 easyvdr vdr: [25862] VNSI: Successfully found following device: 0x269f4e0 (2) for receiving, priority=0
Aug 13 01:37:05 easyvdr vdr: [25862] VNSI: Successfully switched to channel 50 - KiKA HD
Aug 13 01:37:07 easyvdr vdr: [26030] VNSI: Channel: no data 16
--
Aug 13 01:37:11 easyvdr vdr: [25862] VNSI: Successfully found following device: 0x269f4e0 (2) for receiving, priority=0
Aug 13 01:37:11 easyvdr vdr: [25862] VNSI: Successfully switched to channel 49 - Eurosport Deutschland
Aug 13 01:37:13 easyvdr vdr: [26033] VNSI: Channel: no data 16
--
Aug 13 01:37:16 easyvdr vdr: [25862] VNSI: Successfully found following device: 0x269f4e0 (2) for receiving, priority=0
Aug 13 01:37:16 easyvdr vdr: [25862] VNSI: Successfully switched to channel 48 - SPORT1
Aug 13 01:37:18 easyvdr vdr: [26036] VNSI: Channel: no data 16
--
Aug 13 01:37:23 easyvdr vdr: [25862] VNSI: Successfully found following device: 0x269f4e0 (2) for receiving, priority=0
Aug 13 01:37:23 easyvdr vdr: [25862] VNSI: Successfully switched to channel 47 - ORF2E
Aug 13 01:37:25 easyvdr vdr: [26039] VNSI: Channel: no data 16
--
Aug 13 01:37:28 easyvdr vdr: [25862] VNSI: Successfully found following device: 0x269f4e0 (2) for receiving, priority=0
Aug 13 01:37:28 easyvdr vdr: [25862] VNSI: Successfully switched to channel 48 - SPORT1
Aug 13 01:37:30 easyvdr vdr: [26042] VNSI: Channel: no data 16
--
Aug 13 01:37:32 easyvdr vdr: [25862] VNSI: Successfully found following device: 0x269f4e0 (2) for receiving, priority=0
Aug 13 01:37:32 easyvdr vdr: [25862] VNSI: Successfully switched to channel 47 - ORF2E
Aug 13 01:37:34 easyvdr vdr: [26045] VNSI: Channel: no data 16
--
Aug 13 01:37:37 easyvdr vdr: [25862] VNSI: Successfully found following device: 0x269f4e0 (2) for receiving, priority=0
Aug 13 01:37:37 easyvdr vdr: [25862] VNSI: Successfully switched to channel 46 - Zee One HD
Aug 13 01:37:39 easyvdr vdr: [26048] VNSI: Channel: no data 16
--
Aug 13 01:39:59 easyvdr vdr: [25862] VNSI: Successfully found following device: 0x269f4e0 (2) for receiving, priority=0
Aug 13 01:39:59 easyvdr vdr: [25862] VNSI: Successfully switched to channel 35 - ANIXE HD
Aug 13 01:40:01 easyvdr vdr: [26099] VNSI: Channel: no data 16
--
Aug 13 02:02:06 easyvdr vdr: [25862] VNSI: Successfully found following device: 0x269f4e0 (2) for receiving, priority=0
Aug 13 02:02:06 easyvdr vdr: [25862] VNSI: Successfully switched to channel 31 - Radio Bremen TV
Aug 13 02:02:08 easyvdr vdr: [26190] VNSI: Channel: no data 16
--
Aug 13 02:02:16 easyvdr vdr: [25862] VNSI: Successfully found following device: 0x269f4e0 (2) for receiving, priority=0
Aug 13 02:02:16 easyvdr vdr: [25862] VNSI: Successfully switched to channel 30 - MDR Thüringen
Aug 13 02:02:18 easyvdr vdr: [26193] VNSI: Channel: no data 16
--
Aug 13 02:02:23 easyvdr vdr: [25862] VNSI: Successfully found following device: 0x269f4e0 (2) for receiving, priority=0
Aug 13 02:02:23 easyvdr vdr: [25862] VNSI: Successfully switched to channel 31 - Radio Bremen TV
Aug 13 02:02:25 easyvdr vdr: [26196] VNSI: Channel: no data 16
--
Aug 13 02:02:27 easyvdr vdr: [25862] VNSI: Successfully found following device: 0x269f4e0 (2) for receiving, priority=0
Aug 13 02:02:27 easyvdr vdr: [25862] VNSI: Successfully switched to channel 30 - MDR Thüringen
Aug 13 02:02:29 easyvdr vdr: [26199] VNSI: Channel: no data 16
--
Aug 13 02:02:38 easyvdr vdr: [25862] VNSI: Successfully found following device: 0x269f4e0 (2) for receiving, priority=0
Aug 13 02:02:38 easyvdr vdr: [25862] VNSI: Successfully switched to channel 32 - SR Fernsehen
Aug 13 02:02:40 easyvdr vdr: [26205] VNSI: Channel: no data 16
--
Aug 13 02:02:44 easyvdr vdr: [25862] VNSI: Successfully found following device: 0x269f4e0 (2) for receiving, priority=0
Aug 13 02:02:44 easyvdr vdr: [25862] VNSI: Successfully switched to channel 33 - Comedy Central / VIVA AT
Aug 13 02:02:46 easyvdr vdr: [26208] VNSI: Channel: no data 16
Also let me know if I'm wrong here and this a VDR related and not necessarily the VNSI plugin
I think this is VDR related. "no data" means that vnsi gets no data from vdr.
This Weekend there was a huge thunderstorm + rain going letting me debug the messages when theres an actual outage:
Sep 2 21:28:24 easyvdr vdr: [9752] VNSI: Successfully found following device: 0xd68dd0 (3) for receiving, priority=0
Sep 2 21:28:24 easyvdr vdr: [9752] VNSI: Dummy receiver (0x7f3f5c503670) activated
Sep 2 21:28:25 easyvdr vdr: [9799] device 3 TS buffer thread ended (pid=8347, tid=9799)
Sep 2 21:28:25 easyvdr vdr: [9798] buffer stats: 0 (0%) used
Sep 2 21:28:25 easyvdr vdr: [9798] device 3 receiver thread ended (pid=8347, tid=9798)
Sep 2 21:28:25 easyvdr vdr: [9800] device 3 receiver thread started (pid=8347, tid=9800, prio=high)
Sep 2 21:28:25 easyvdr vdr: [9752] VNSI: activate live receiver: 1
Sep 2 21:28:25 easyvdr vdr: [9752] VNSI: Successfully switched to channel 14 - zdf_neo HD
Sep 2 21:28:25 easyvdr vdr: [9752] VNSI: Started streaming of channel zdf_neo HD (timeout 2 seconds)
Sep 2 21:28:25 easyvdr vdr: [9801] cLiveStreamer stream processor thread started (pid=8347, tid=9801, prio=high)
Sep 2 21:28:25 easyvdr vdr: [9802] device 3 TS buffer thread started (pid=8347, tid=9802, prio=high)
Sep 2 21:28:26 easyvdr vdr: [9756] VNSI: Channel: no data 16
Sep 2 21:28:26 easyvdr vdr: [9801] VNSI: Channel: no data 16
Sep 2 21:28:29 easyvdr vdr: [9756] VNSI: Channel: no data 16
Sep 2 21:28:29 easyvdr vdr: [9801] VNSI: Channel: no data 16
Sep 2 21:28:31 easyvdr vdr: [9756] VNSI: Channel: no data 16
Sep 2 21:28:31 easyvdr vdr: [9801] VNSI: Channel: no data 16
Sep 2 21:28:33 easyvdr vdr: [9756] VNSI: Channel: no data 16
Sep 2 21:28:33 easyvdr vdr: [9801] VNSI: Channel: no data 16
Sep 2 21:28:34 easyvdr vdr: [8359] frontend 2/0 timed out while tuning to channel 14 (zdf_neo HD), tp 111361
So for I have concluded that on an actual outage vdr reports the frontend timing out while on my error this does not happen und somewhere between vdr and vnsi the data gets lost.
I also made a Thread at http://www.easy-vdr.de/thread-18130.html to get some more exposure and Ideas.
I'm getting the same error and then, after a few seconds, this one: VNSI-Error: cParser::AddPESPacket - max buffer size reached, pid: 201
Streamdev works just fine, but vnsi does not play even non-encrypted channels. Here is my setup: vdr 2.3.9 git ff4c0a8 vdr-plugin-vnsiserver 1.6.0 git 8c898d9 vdr-plugin-dvbapi 2.2.4 git 7d51cc4
VNSI-Error: cParser::AddPESPacket - max buffer size reached, pid: 201
means the parser is not able to detect beginning and end of a PES packet. is this a scrambled stream?
could you create a short recording of this channel and make this available to me?
Sorry for late reply, for some reason I did not receive a notification from github. It fails to play any stream, either scrambled or not. Please find the recordings attached.
I've fixed this issue by adding video codec =27: to all VPIDs in the list. If the codec is not specified, it's substituted with =2: and vnsi fails with the above error. Streamdev works properly in both cases.
vnsi uses the parameters it gets from vdr. vdr extracts it from PAT/PMT and updates channels.conf. do you allow vdr to update this file?
Hi
im still playing around with my 3 Boxes (Kodi) and since 1 Hour i have exact this issue - and i dont know why ...
I allow VDR to make Changes on Channels.conf - i have restarted VDR / Restartet all Boxes - tryed to delete Channels.conf - and replace it with a old one -
Jan 18 23:10:34 vdrserver vdr: [1159] VNSI: Client with ID 8 connected: 192.168.1.251:63374
Jan 18 23:10:34 vdrserver vdr: [1205] VNSI: Welcome client 'XBMC Media Center' with protocol version '13'
Jan 18 23:10:34 vdrserver vdr: [1160] VNSI: removing client with ID 8 from client list
Jan 18 23:10:34 vdrserver vdr: [1204] VNSI: Channel: no data 16
Jan 18 23:10:34 vdrserver vdr: [1204] VNSI: Created stream for pid=101 and type=7
Jan 18 23:10:34 vdrserver vdr: [1204] VNSI: Created stream for pid=106 and type=1
Jan 18 23:10:34 vdrserver vdr: [1204] VNSI: Created stream for pid=102 and type=2
Jan 18 23:10:34 vdrserver vdr: [1204] VNSI: Created stream for pid=103 and type=2
Jan 18 23:10:34 vdrserver vdr: [1204] VNSI: Created stream for pid=105 and type=10
Jan 18 23:10:34 vdrserver vdr: [1204] VNSI: Created stream for pid=104 and type=12
Jan 18 23:10:34 vdrserver vdr: [1204] VNSI: Audio stream change, pid: 103, channels: 2, samplerate: 48000
Jan 18 23:10:34 vdrserver vdr: [1204] VNSI: Audio stream change, pid: 102, channels: 2, samplerate: 48000
Jan 18 23:10:34 vdrserver vdr: [1204] VNSI: Channel: no data 16
Jan 18 23:10:34 vdrserver vdr: [1204] VNSI: Audio stream change, pid: 106, channels: 2, samplerate: 48000
Jan 18 23:10:34 vdrserver vdr: [1204] VNSI: Channel: no data 16
Jan 18 23:10:34 vdrserver vdr: [1204] VNSI: Channel: no data 16
Jan 18 23:10:34 vdrserver vdr: [1204] VNSI: Video stream change, pid: 101, width: 720, height: 576, aspect: 1,777778
Jan 18 23:10:34 vdrserver vdr: [1204] VNSI: Channel: no data 16
Jan 18 23:10:34 vdrserver vdr: [1204] VNSI: Channel: no data 16
Jan 18 23:10:34 vdrserver vdr: [1204] VNSI: Channel: no data 16
Jan 18 23:10:34 vdrserver vdr: [1204] VNSI: Channel: no data 16
Jan 18 23:10:35 vdrserver vdr: [1204] VNSI: Channel: no data 16
Jan 18 23:10:35 vdrserver vdr: [1204] VNSI: Channel: no data 16
Jan 18 23:10:35 vdrserver vdr: [1204] VNSI: Channel: no data 16
Jan 18 23:10:35 vdrserver vdr: [1204] VNSI: Channel: no data 16
Jan 18 23:10:35 vdrserver vdr: [1204] VNSI: Channel: no data 16
I dont Understand tis issue - i play around with Plugin and Kodi since some Weeks but never seen this messages on Kodi or on VDR log
I Hope anyone can help me
I have a Additional Information to this Issue:
This only happen when switching off "Add Transponder or add Channels" in VDR Setup. As soon you switch to "only UPdate PID and Names" then this Error will flood your Logfile and display on Kodi.
Hello, I recently made the switch from using EasyVDR 3.0 as a frontend to Kodi v17.2 with this the vnsi plugin newest version thats in the repo.
My headless server is easyvdr 3.0 (VDR-Version: 2.2.0) with this plugin:
I use a Digital Devices GmbH Max S8 with 8 tuners in unicable mode on Astra 19.2E
After I made the switch two weeks ago I started to encounter no data errors in Kodi when trying to tune to a channel. This is sometimes randomly only once sometimes for a few minutes in a row and then it magically resolves itself again. This happens on all clients and as far as I have seen it only on one client at the time. Recordings also work fine all the time there was not a single missed/unusable one from vdr.
VNSI Server Pluging is started with -Pvnsiserver -d -t 4 I changed it from the default 10 sec timeout and no -d to see if it makes a difference.
I uploaded the whole VDR log here: https://pastebin.com/gR7XFtTK
I tried to analyse it a bit already and my first guess was that the tuner its trying to tune to is not working somehow.
Since this was not issue for 2 years while watching with a VDR frontend my conclusion was that its somehow related to this plugin.
While writing this post and looking at all the other topics regarding the no data error I noticed that my VDR Loglevel was only on 2 I set to 3 now to get some more info out of it.
If it turns out that it is indeed an VDR problem and while the VDR frontend I never encountered the issue because it might just have switched to another tuner would it be possible for this plugin to do the same or does it rely on VDR giving out a tuner?
This is how it looks like in the logfile over the course of the evening: