[mythtv] Video Problems with BT848

Neil Whelchel koyama at firstlight.net
Sat Sep 18 14:25:47 EDT 2004


On Sat, 18 Sep 2004, [iso-8859-1] Torbj=F6rn Jansson wrote:

> mythtv-dev-bounces at mythtv.org <> wrote:
> > Hello,
> > Just wondering if anyone else is having problems with the
> > video with the
> > cvs version for the last couple of weeks.
> > After a random amount of time the video capture/compression
> > falls into a
> > failure mode. (Very dark image, everything else normal.) This can take
> > from one second to over an hour from the time of the
> > recording start, if
> > at all. Also the failure only seems to occur when the MPEG4 codec is
> > selected, I have not seen this failure with RTJPEG.
> >
> > -Neil Whelchel-
>
> This is not a mythtv problem, it's some kind of driver or kernel problem.
> I've had this for a very long time.
>
> If you take a look at /var/log/messages you probably have lines similar t=
o:
> kernel: bttv0: SCERR @ 077c101c,bits: HSYNC OFLOW SCERR*
> last message repeated 12 times
> kernel: bttv0: timeout: drop=3D0 irq=3D17829229/17829229, risc=3D077c101c=
, bits:
> HSYNC OFLOW
> kernel: bttv0: reset, reinitialize
> kernel: bttv0: PLL: 28636363 =3D> 35468950 . Ok
>
> I think it's when the "reset, reinitialize" part happends the picture is =
all
> black.
> I get this problem maybe a few times a week.
> I've always thought it was the crappy via chipset that caused it, but i'm
> not sure.
>
> When i was using linux 2.4 kernel instead if theese messages the computer
> locked up hard.
> But with 2.6 kernel it creates black picture instead.
>
> I've never found a solution to the problem.

Well, I can see that we are having the same problem as I found the same
errors. I am not sure that it is just related to the kernel/driver though
as I have been using this exact same hardware for the last 9 months with
Myth with no problems until two or three weeks ago. Why the change? Also,
I have not been able to reproduce the problem when encoding to RTJPEG, or
while using ffmpeg/MPEG4 instead of Myth. Seems like it is a kernel/driver
problem that is induced by something external to the kernel.
-Neil Whelchel-




More information about the mythtv-dev mailing list