On Wednesday 24 January 2007 23:42, Hans Verkuil wrote:
> On Wednesday 24 January 2007 23:22, Roger Depreeuw wrote:
> > On Wed, 2007-01-24 at 20:49 +0100, Hans Verkuil wrote:
> > > On Wednesday 24 January 2007 20:35, Sander Sweers wrote:
> > > > Roger Depreeuw wrote:
> > > > > On Wed, 2007-01-24 at 08:34 -0500, Ian Service wrote:
> > > > >> On 1/24/07, Hans Verkuil <[EMAIL PROTECTED]> wrote:
> > > > >>         Just verifying that I understand it correctly: this
> > > > >> also happens with a
> > > > >>         non-trunk ivtv release, correct? So it is not some
> > > > >> ivtv trunk bug that is
> > > > >>         hiding somehwere.
> > > > >>
> > > > >> Correct, this problem is the same with the trunk as it is
> > > > >> with recent ivtv-0.8
> > > > >>
> > > > >>
> > > > >>         With 16 MB of buffers that should give you somewhere
> > > > >> between 10-16 seconds
> > > > >>         of buffering I think. I find it hard to believe that
> > > > >> MythTV would take so
> > > > >>         much time! You can easily check how full the various
> > > > >> buffers are by
> > > > >>         running v4l2-ctl --log-status.
> > > > >>
> > > > >> While watching Live TV:
> > > > >> [EMAIL PROTECTED] ~]# v4l2-ctl --log-status
> > > > >> --device=/dev/video1
> > > > >
> > > > > Sorry to interfere in your discussion (i am still in learning
> > > > > mode) Shouldn't you see some traffic in the stream MPEG
> > > > > encoder? When i do the same test i get the following
> > > > >    ivtv0: Stream encoder MPEG: 14% in use
> > > > >    ivtv0: Stream encoder YUV: 0% in use
> > > > >    ivtv0: Stream encoder VBI: 0% in use
> > > > >    ivtv0: Stream encoder PCM audio: 0% in use
> > > >
> > > > I almost never see values higher than 0% being used. Only VBI
> > > > sometimes goes up to 2%. Only cat /dev/video33 > /dev/null will
> > > > show a 30% in yuv. However I am not sure how we should read
> > > > this. Is this the buffer?
> > >
> > > Yes. 0% is empty, 100% is full and the errors start appearing in
> > > the log. For YUV the buffers are fairly small and the YUV frames
> > > are big, so that shows up as a high percentage. The 14% for MPEG
> > > in the log above indicates either a slow machine or hiccups in
> > > reading. How does it fluctuate over time?
> >
> > Right it slowly increases. After roughly 90 min it is at 80%
>
> What is the CPU usage during capture? Close to 100% or much less? Can
> you post the output of --log-status and 'top -b -n1' at a point where
> the buffer is over 50% full? This is somewhat unexpected. Or is it a
> really slow box you're capturing on?

A quick follow up: make sure you use the latest ivtv trunk version! 

Thanks,

        Hans

_______________________________________________
ivtv-devel mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-devel

Reply via email to