[vdr] Re: softdevice 0.0.7 cvs crash tests...

[Nicolas Huillard <nhuillard@ghs.fr>]

Stefan Lucke wrote:
> Quoting Nicolas Huillard <nhuillard@ghs.fr>:
>
> > Stefan Lucke wrote:
> >
> > ...
> >
> > > I tested my change with your three streams (took only 001.vdr files). The only
> > > difference I see is ffmpeg (vdr1.3.12, gcc 3.3.1) mine is:
> > > [softdevice] ffmpeg version(0.4.8) build(4700)
I'll check tonight if the errors I see are the same as previously.

> My cvs checkout was about early february. But I found another hint
> in avcodec.h (search for PADDING) .
The build number is statically defined in libavcodec/avcodec.h as 
LIBAVCODEC_BUILD. It must then be generated at "automake/autoconf" 
stage, and thus reflects the date at which you checkout from CVS.

The PADDING stuff in libavcodec/avcodec.h is the same in 0.4.8 build 
4680 and 0.4.9-pre1 build 4718 :

/**
 * Required number of additionally allocated bytes at the end of the 
input bitstream for decoding.
 * this is mainly needed because some optimized bitstream readers read
 * 32 or 64 bit at once and could read over the end<br>
 * Note, if the first 23 bits of the additional bytes are not 0 then 
damaged
 * MPEG bitstreams could cause overread and segfault
 */
#define FF_INPUT_BUFFER_PADDING_SIZE 8

Does this means that softdevice must be sure to add 23 bits with zeros 
to each paquet ?

> [ .. ]
>
> > http://www.epiawiki.org/wiki/tiki-download_file.php?fileId=8 
> I think I followed those patch instructions but have to check
> exact kernel version later.
>
> > Aug 11 08:22:24 vdr kernel: check x:720  y:576  bpp:32
> > Aug 11 08:22:24 vdr kernel: selmode :75
> > Aug 11 08:22:24 vdr kernel: setmode x:720 y:576 bpp:32
> > Aug 11 08:22:24 vdr kernel: pan_display offset:0 0
...

> I got tons of similar messages. Perhaps they differ in x and y since
> i use vga out (my LCD doesn't support 720x576).
OK. I'll assume that we have the same kernel.
Don't you experience some flickering with the OSD ? ie. the OSD some 
times go half the screen to the left or right for a single (or so) frame 
(fast flash) ? I particularly affects the play recording OSD (timing bar).

Thank you for all your hard work.

--
NH