summaryrefslogtreecommitdiff
path: root/HISTORY
diff options
context:
space:
mode:
authorFrank Schmirler <vdr@schmirler.de>2015-01-24 00:19:04 +0100
committerFrank Schmirler <vdr@schmirler.de>2015-01-24 00:19:04 +0100
commitb33d2631df753bf4918f7967404620d5e605f967 (patch)
tree2f86dac89add017c936c2b96d2523d0c73042ead /HISTORY
parent657c8bc49c7ed331e93041064452d8f0b01206e8 (diff)
downloadvdr-plugin-streamdev-b33d2631df753bf4918f7967404620d5e605f967.tar.gz
vdr-plugin-streamdev-b33d2631df753bf4918f7967404620d5e605f967.tar.bz2
Fixed problems related to VTP filter streaming like ringbuffer overflows,
stuttering or aborting video stream (refs #2045) Toerless Eckert wrote: This patch tries to resolve problems in streamdev-client that can occur when enabling "StreamFilters". Enabling this option is necessary to receive certain programs with dynamic PIDs such as some german "regional" broadcast (eg: NDR). Problem: Without this fix, the following behavior was observed on a Raspberry PI running streamdev-0.6.1-git with VDR-2.6.1: - Buffer overflows of filter data - Stop/go video on channels - Total stopping of video More logs in: http://www.vdr-portal.de/board16-video-disk-recorder/board55-vdr-plugins/125237- streamdev-client-filter-daten-streamen-ndr-raspberry-haengt/ Analysis: VDR expect section data from filters separately from the main program stream. Historically, it received each filter data via a separate file descriptor from the DVB card. In the streamdev-client module, a socketpair is used to feed filter data to the main VDR code. During certain operations in VDR, such as startup or channel change (depending also on the speed of initialization of the video output driver), VDR does not consume the filter data as fast as it is provided by streamdev-client, resulting in overflow of the default socket buffers used by streamdev-client. To add to the problem of overflowing the socketpair buffers, the streamdev-client code sends several times a second short packets into the socketpair to determine if the receiving side (VDR) has closed the socketpair (IsClosed(), CarbageCollect()). This further clogs up the socketpair() buffer. The raspberry PI socketpair buffering behavior seems to be the same as that of other 3.x linux systems, the socket buffer size is by default 163840, and it can be increased via sysctl net.core.wmem_max. During startup, it can take up to 10 seconds before VDR will consume filter data, so the socketpair buffer can fill up with 10 seconds worth of data. Solution 1. IsClosed()/CarbageCollect() where removed from client/filter.c and replaced by explicitly tracking when VDR closes a filter socket. This alone seems to already resolve the problem of hanging or stop&go video and seems to be sufficient to receive dynamic-PID channels reliably. 2. filter.c was enhanced to request a larger socket buffer size if config option FilterSockBufSize is set. 3. If supported (if streamdev-client runs on linux), the socketpair queue is "flushed" to reduce the amount of "random" packet drop messages and to rather drop sequential messages.
Diffstat (limited to 'HISTORY')
-rw-r--r--HISTORY4
1 files changed, 3 insertions, 1 deletions
diff --git a/HISTORY b/HISTORY
index dac9500..0a4f03a 100644
--- a/HISTORY
+++ b/HISTORY
@@ -1,8 +1,10 @@
VDR Plugin 'streamdev' Revision History
---------------------------------------
+- fixed problems related to VTP filter streaming like ringbuffer overflows,
+ stuttering or aborting video stream (thanks to Toerless Eckert)
- added Polish translation (thanks to Tomasz Maciej Nowak)
-- converted suspend.dat into proper PES format (thanks to te36)
+- converted suspend.dat into proper PES format (thanks to Toerless Eckert)
- implemented GetCurrentlyTunedTransponder() on client (thanks to Martin1234)
- added service call returning the number of clients (suggested by Martin1234)
- added SVDRP commands to list and disconnect clients (thanks to Guy Martin)