Re: [vdr] Ring buffer overflows with streamdev and remux script
On Wed, Jul 13, 2011 at 12:05 PM, Luboš Doležel wrote: > Apart from simplifying the script to a single line I've found a solution: > I've tripled the size of the ring buffer in vdr-streamdev-server and the > problem is gone. No problems after hours of playback... Is there any reason why the ring buffer can't or shouldn't be dynamic aside of just not bothering to implement it? ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Ring buffer overflows with streamdev and remux script
On 9.7.2011 22:51, Luboš Doležel wrote:
Hello,
I'm experiencing ring buffer overflows with streamdev-server and the
following remux script:
tmpdir=${TMPDIR-/tmp}/externremux-${RANDOM:-$$}
FIFO=$tmpdir/out.mkv
OUTLOG=$tmpdir/out.log
mkdir -p $tmpdir || exit 1
mkfifo $FIFO
(cat $FIFO; rm -rf $tmpdir) &
ffmpeg -threads 2 -i - -deinterlace -vcodec libx264 -vpre veryfast -b
900k -bt 50k -maxrate 900k -s vga -acodec libfaac -async 1 -ac 2 -ar
44100 -aq 128 -sn -y $FIFO 2>/tmp/ffmpeg.log
My outgoing line is a VDSL2 line with a 2048kbps upload.
2011-07-09T21:05:46+02:00 localhost vdr: [553] buffer usage: 70% (tid=552)
2011-07-09T21:05:47+02:00 localhost vdr: [553] buffer usage: 80% (tid=552)
2011-07-09T21:05:47+02:00 localhost vdr: [553] buffer usage: 30% (tid=552)
2011-07-09T21:05:49+02:00 localhost vdr: [25625] ERROR: 76 ring buffer
overflows (14288 bytes dropped)
When this happens, the picture freezes and it never recovers. Sometimes,
there's also this suspicious extra error message (the first line):
2011-07-09T21:16:28+02:00 localhost vdr: [593] ERROR: read failed:
Resource temporarily unavailable
2011-07-09T21:16:29+02:00 localhost vdr: [25625] ERROR: 58 ring buffer
overflows (10904 bytes dropped)
2011-07-09T21:16:33+02:00 localhost vdr: [596] buffer usage: 70% (tid=595)
2011-07-09T21:16:33+02:00 localhost vdr: [596] buffer usage: 80% (tid=595)
2011-07-09T21:16:34+02:00 localhost vdr: [596] buffer usage: 90% (tid=595)
Any advice on how to fix the problem?
Thanks!
Apart from simplifying the script to a single line I've found a
solution: I've tripled the size of the ring buffer in
vdr-streamdev-server and the problem is gone. No problems after hours of
playback...
--
Luboš Doležel
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Transfer mode vs TS playback: any difference in TS streams for vdr.1.7.19?
On Monday 11 Jul 2011, Klaus Schmidinger wrote:
> On 11.07.2011, at 03:21, Laz wrote:
> > Hi,
> >
> > I'm currently updating the softdevice plugin to work with the changes
> > to TS format that started with vdr-1.7.1 and also current versions
> > of ffmpeg (libavcodec does the actual decoding).
> >
> > I've made some progress with vdr-1.7.19:
{snip}
> In Transfer Mode onlx one single PAT/PMT is generated at the very start
> of it, while a recording contains a PAT/PMT at the beginning of every
> GOP.
I've made good progress with this now: it all seems to work after a bit of
a shaky start-up! It will only run if run from a script to restart it
multiple times.
There is something with the startup of softdevice that causes a
segmentation fault: it's level of error checking in it's startup neesd
improving. It can restart about five times or so before it starts
properly. I need to track down the source of this.
It can also take a few seconds for the video to appear when starting up,
changing channel, or starting or stopping a recording. Audio instantly
changes on all of these so the streams are there and can be decoded. (The
audio is used presented "as is" and the video is delayed or speeded up to
keep in sync.)
Once it has managed to start up and the video has appeared, it all seems
pretty stable. I can play old and new format recordings too.
Cheers,
Laz
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
