Re: [vdr] SOLVED??? buffer overruns and sync probs after change of receivers

2016-02-07 Thread Harald Milz 
Richard, 

On Sun, Feb 07, 2016 at 12:34:17PM +, Richard F wrote:
> One of the things that the vnsi developer said to do set this in the VDR
> config
> 
> vnsiserver.AvoidEPGScan = 1
> (http://forum.kodi.tv/showthread.php?tid=203396)

Now that you mention it - I also see interruptions sometimes when Kodi appears
to update its timers. That is, when it scans through the timer list,
displaying the respective message windows bottom left. Sometimes, live
streaming just crashes, and needs to be restarted manually. 

I'll give AvoidEPGScan = 1 a try - thank you! 

> I don't know where PLAYERBUFSIZE is - Kodi config file - which one?

No, that's in vdr:

dvbplayer.c:#define PLAYERBUFSIZE  MEGABYTE(1)

and 

recorder.c:#define RECORDERBUFSIZE  (MEGABYTE(10) / TS_SIZE * TS_SIZE) //
multiple of TS_SIZE

Please not that it really cures only the symptom. If there is a problem with
filling any emptying the buffer, leading to an overrun, then it will
eventually happen, no matter what the size is. So far, I haven't seen this
yet with 50 megs each. 

-- 
A gift of a flower will soon be made to you.

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] SOLVED??? buffer overruns and sync probs after change of receivers

2016-02-07 Thread Richard F 
Harald,

I'm using a somewhat similar config to yours, though different receivers
(PCTV Nanostick 290e for DVB-T2, and very old "WideView USB DVB-T").  I
too have had problems with streaming live TV to Kodi for many, many
versions.  As you have noted, no issues recording, and no issues playing
back recordings,  it's just live TV streaming that's the problem, and
usually only after a few minutes of watching, not immediately (so
perhaps testers haven't noticed), and a bit worse in HD
unsurprisingly.   But I never see buffer or driver errors in the logs -
no errors from vnsi in fact, so I think in my case it's purely a Kodi
issue, perhaps something to do with PTS time stamps, and/or buffer
synchronisation.  It works very well, aside from live TV - just waiting
for a Kodi version that solves this issue.

One of the things that the vnsi developer said to do set this in the VDR
config

vnsiserver.AvoidEPGScan = 1
(http://forum.kodi.tv/showthread.php?tid=203396)

It prevents interruptions during streaming. It certainly helps, but not
a 100% fix.

I don't know where PLAYERBUFSIZE is - Kodi config file - which one?

Thanks

On 7/02/2016 07:18, Harald Milz wrote:
> OK - I think I have a stable configuration now, albeit weird. 
>
> - I upgraded the mobo BIOS to -latest, to no avail (hoping this would change
>   the MSI interrupt behaviour, but it only appears to add some more CPU
>   support. But you never know, BIOS changelogs haven't been well known for
>   being particularly verbose.)
> - I set pci=msi - no change. Will change this back to default for the next
>   reboot
> - I enlarged PLAYERBUFSIZE (and RECORDERBUFSIZE to be sure) to 50 megs, and
>   voilà, the setup has been stable for the last 4 days or so. I know this only
>   cures the symptom IF the buffer logic has an actual problem
>
> OK, the WAF has been saved for now, but the fix still does not explain why the
> buffer overrun problem only occurs when watching live TV with vnsiserver and
> kodi, and can only be cured by rebooting the machine. So ... :-/ 
>
>


___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] SOLVED??? buffer overruns and sync probs after change of receivers

2016-02-06 Thread Harald Milz 
OK - I think I have a stable configuration now, albeit weird. 

- I upgraded the mobo BIOS to -latest, to no avail (hoping this would change
  the MSI interrupt behaviour, but it only appears to add some more CPU
  support. But you never know, BIOS changelogs haven't been well known for
  being particularly verbose.)
- I set pci=nomsi - no change. Will change this back to default for the next
  reboot
- I enlarged PLAYERBUFSIZE (and RECORDERBUFSIZE to be sure) to 50 megs, and
  voilà, the setup has been stable for the last 4 days or so. I know this only
  cures the symptom IF the buffer logic has an actual problem

OK, the WAF has been saved for now, but the fix still does not explain why the
buffer overrun problem only occurs when watching live TV with vnsiserver and
kodi, and can only be cured by rebooting the machine. So ... :-/ 


On Mon, Feb 01, 2016 at 08:20:06AM +0100, Harald Milz wrote:
> Hi all, 
> 
> over the weekend I upgraded to vdr-2.2.0, and I'm still seeing the same
> problems. 
> 
> - vdr-2.2.0 from ftp://ftp.tvdr.de/vdr/vdr-2.2.0.tar.bz2
> - vnsiserver from git (from yesterday)
> - dddvb-0.9.22 (loaded as ddbridge msi=0)
> 
> Everything else is unchanged. 
> 
> Result: when the problem starts, 
> 1. switching channels does not help
> 2. restarting VDR does not help
> 3. stopping VDR, reloading driver, and restarting VDR does not help
> 4. only restarting the machine seems to help so far, for some time, until the
>problem occurs again. 
> 
> This is after 3.:
> 
> Feb  1 07:56:59 seneca vdr: [31887] VNSI: Client with ID 2 connected: 
> 192.168.20.200:37103
> Feb  1 07:56:59 seneca vdr: [31939] VNSI: Welcome client 'XBMC Media Center' 
> with protocol version '8'
> Feb  1 07:56:59 seneca vdr: [31939] VNSI: LiveStreamer::Close - close
> Feb  1 07:56:59 seneca vdr: [31939] VNSI: close video input ...
> Feb  1 07:56:59 seneca vdr: [31939] VNSI: Successfully found following 
> device: 0x8aaee00 (2) for receiving
> Feb  1 07:56:59 seneca vdr: [31940] device 2 receiver thread started 
> (pid=31867, tid=31940, prio=high)
> Feb  1 07:56:59 seneca vdr: [31939] VNSI: Successfully switched to channel 2 
> - ZDF HD
> Feb  1 07:56:59 seneca vdr: [31939] VNSI: Started streaming of channel ZDF HD 
> (timeout 10 seconds)
> Feb  1 07:56:59 seneca vdr: [31943] device 2 TS buffer thread started 
> (pid=31867, tid=31943, prio=high)
> Feb  1 07:56:59 seneca vdr: [31942] cLiveStreamer stream processor thread 
> started (pid=31867, tid=31942, prio=high)
> Feb  1 07:56:59 seneca vdr: [31941] VNSI: VideoInput: no pat/pmt within 
> timeout, falling back to channel pids
> Feb  1 07:56:59 seneca vdr: [31941] VNSI: Video Input - new pmt, attaching 
> receiver
> Feb  1 07:57:00 seneca vdr: [31942] VNSI: Created stream for pid=6110 and 
> type=8
> Feb  1 07:57:00 seneca vdr: [31942] VNSI: Created stream for pid=6122 and 
> type=1
> Feb  1 07:57:00 seneca vdr: [31942] VNSI: Created stream for pid=6120 and 
> type=2
> Feb  1 07:57:00 seneca vdr: [31942] VNSI: Created stream for pid=6121 and 
> type=2
> Feb  1 07:57:00 seneca vdr: [31942] VNSI: Created stream for pid=6123 and 
> type=2
> Feb  1 07:57:00 seneca vdr: [31942] VNSI: Created stream for pid=6131 and 
> type=9
> Feb  1 07:57:00 seneca vdr: [31942] VNSI: Created stream for pid=6130 and 
> type=11
> Feb  1 07:57:02 seneca vdr: [31943] i/o throttle activated, count = 1 
> (tid=31943)
> Feb  1 07:57:03 seneca vdr: [31943] buffer usage: 70% (tid=31940)
> Feb  1 07:57:03 seneca vdr: [31943] buffer usage: 60% (tid=31940)
> Feb  1 07:57:03 seneca vdr: [31943] buffer usage: 70% (tid=31940)
> Feb  1 07:57:04 seneca vdr: [31943] buffer usage: 80% (tid=31940)
> Feb  1 07:57:04 seneca vdr: [31943] buffer usage: 90% (tid=31940)
> Feb  1 07:57:05 seneca vdr: [31943] buffer usage: 100% (tid=31940)
> Feb  1 07:57:06 seneca vdr: [31943] buffer usage: 60% (tid=31940)
> Feb  1 07:57:06 seneca vdr: [31943] buffer usage: 70% (tid=31940)
> Feb  1 07:57:06 seneca vdr: [31943] buffer usage: 60% (tid=31940)
> Feb  1 07:57:06 seneca vdr: [31943] buffer usage: 70% (tid=31940)
> Feb  1 07:57:06 seneca vdr: [31943] buffer usage: 80% (tid=31940)
> Feb  1 07:57:07 seneca vdr: [31943] buffer usage: 90% (tid=31940)
> Feb  1 07:57:08 seneca vdr: [31943] buffer usage: 100% (tid=31940)
> Feb  1 07:57:09 seneca vdr: [31943] ERROR: driver buffer overflow on device 2
> Feb  1 07:57:19 seneca vdr: message repeated 6 times: [ [31943] ERROR: driver 
> buffer overflow on device 2]
> Feb  1 07:57:20 seneca vdr: [31940] ERROR: skipped 123 bytes to sync on TS 
> packet on device 2
> Feb  1 07:57:21 seneca vdr: [31943] ERROR: driver buffer overflow on device 2
> Feb  1 07:57:23 seneca vdr: [31943] ERROR: driver buffer overflow on device 2
> Feb  1 07:57:23 seneca vdr: [31943] buffer usage: 60% (tid=31940)
> Feb  1 07:57:23 seneca vdr: [31943] buffer usage: 70% (tid=31940)
> Feb  1 07:57:24 seneca vdr: [31943] buffer usage: 80% (tid=31940)
> Feb  1 07:57:25 seneca vdr: [31943] buffer usage: 90% (tid=31940)
>