On Thursday 15 February 2007 17:42, Rich Kadel wrote:
> So far so good with 0.10.0rc1. At least, it hasn't crashed in a
> couple of days of continuous reading, 3 video streams, and 8 VBI.
>
> Now I have a new problem I'd like to resolve. My logs are getting
> filled up with the following message:
>
> Feb 12 16:00:00 server2 kernel: ivtv2 warning: encoder VBI: Couldn't
> find start
> of buffer within the first 256 bytes
>
> Occasionally, I'll notice some dropped characters in the VBI. Not
> often. But it could be a symptom.
>
> I'd like to fix the VBI problem if there's a way to do that. If not,
> is there a way to reduce the log messages?
How are you capturing VBI? Is it sliced VBI or raw VBI? And if it is
sliced VBI, is it embedded in the MPEG stream or captured as a separate
stream?
Do you always have these messages, or do they appear suddenly? It is
reproducable with a simple 'cat /dev/video0 >x.mpg' command?
BTW, there is no need to increase the mpeg buffers, it's not related to
that. Basically this message indicates that something weird is going on
with the VBI transfers. It can occur once in a while, but it shouldn't
happen continuously.
Regards,
Hans
_______________________________________________
ivtv-devel mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-devel
