Re: [Mjpeg-users] lavrec crash

[Derek F. <der...@ya...>]

> > Nov  2 18:28:06 monkey kernel: DC10plus[0]: JPEG error
> > stat=0x400002cf(0x40000000) queue_state=17378/17378/17380/17442 seq=34758
> > frame=34. Codec stopped. stat_com frames: 1->34 2->35 3->35
> > Nov  2 18:28:06 monkey kernel: DC10plus[0]: Restart
> > Nov  2 18:28:12 monkey kernel: DC10plus[0]: timeout: codec isr=0xcf,
> > csr=0x00
>
> well, this is probably the interesting part. If only I knew a bit more
> about how the hardware works on the PCI bus I might actually be able to
> explain this ;-). Maybe someone else knows a bit more about what could
> cause this timeout? What hardware (specifically: mainbord/pci-bus) are
> you using to capture? I'm getting the feeling that this is not so much
> lavrec-related but more hardware-related.

I've got a Supermicro P6DGU with dual PIII-500s. No overclocking or anything 
like that. 1GB RAM.

> > The command used was:
> >  lavrec -f a -i P -d 2 -g 768x576 -l 80 -q 40 -a 16 -s ac1%0d.avi
>
> Seems like reasonable sober settings to me, that's certainly not the
> problem. Btw, using -g768x576 shouldn't be necessary anymore if you're
> using a current CVS version - it should be able to detect the correct
> full-frame-size automatically.

I'm one of the not-so-elite bunch for whom building the CVS version resulted 
in nothing but compile time errors. I still on 1.4.1 and am eagerly awaiting 
1.5 (or CVS snapshots!).

_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com