This repository has been archived by the owner on Dec 21, 2020. It is now read-only.
no data error with VNSI #97
Comments
|
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
Nevertheless I went into the VDR config and saved it: So for now I can just wait to see if it happens again or not. |
|
Update: the problem still persists What I can see from the log: Switching channels during this time works as long as VNSI select another device for the channel. So it seems that the device might be blocked by something? 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:
|
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: 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: Streamdev works just fine, but vnsi does not play even non-encrypted channels. |
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. |
|
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 - 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. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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:
The text was updated successfully, but these errors were encountered: