On Monday 23 October 2006 15:14, [EMAIL PROTECTED] wrote:
> I posted an hour ago about the ivtv-enc-vbi related oops, and was
> further wondering:
>
> Is this sort of CPU utilization normal?
Yes, VBI processing takes a fair bit of CPU utilization. I've already
noticed that my beta driver greatly reduces this. So I expect that this
will be solved once the beta driver is stable and is released.
>
> snip from top cmd, cpu util. is 30% for ivtv-enc-vbi
>
> 1603 root 5 -10 0 0 0 S 30.0 0.0 1:57.95
> ivtv-enc-vbi
> 1963 root 10 -5 0 0 0 S 9.9 0.0 2:30.82
> md2_raid5 8697 root 32 17 105m 46m 13m R 9.5 4.7 0:28.55
> mythcommflag
> 1602 root 6 -10 0 0 0 S 3.0 0.0 0:10.47 ivtv-enc
> 1964 root 10 -5 0 0 0 D 1.0 0.0 0:16.64
> md2_resync 3090 root 15 0 331m 45m 15m S 0.7 4.5
> 1:32.14 mythbackend
>
> also, off topic a bit, but:
>
> I'm using the latest mythtv from atrpms, and there seems to be no way
> to turn off vbi once you've selected a pvr150,250,etc. type card.
>
> Is there some easy way I can force ivtv-enc-vbi to not run/not be
> available, since it seems to be causing me grief, and I don't care
> about closed captioning?
Really? That's not nice. Running 'v4l2-ctl --set-fmt-sliced-vbi=off'
might do the trick, but I suspect that MythTV turns it back on on the
next recording.
This is something that should be taken up with the MythTV people. At
this moment VBI is not yet reliable (that's what I'm trying to fix in
the beta driver) so you should be able to select whether you want it or
not.
>
> It seems to be off when querying it with ivtvctl:
>
> [EMAIL PROTECTED] ~]# ivtvctl -W -d /dev/video0
> ioctl IVTV_IOC_G_VBI_PASSTHROUGH ok
> VBI passthrough mode is 00000000
> [EMAIL PROTECTED] ~]# ivtvctl -W -d /dev/video1
> ioctl IVTV_IOC_G_VBI_PASSTHROUGH ok
> VBI passthrough mode is 00000000
> [EMAIL PROTECTED] ~]# ivtvctl -W -d /dev/video2
> ioctl IVTV_IOC_G_VBI_PASSTHROUGH ok
> VBI passthrough mode is 00000000
Wrong check. Run v4l2-ctl --get-fmt-sliced-vbi.
Regarding the Oops: I've never seen it myself, but I did see the
occasional report of this before. However, I'm not going to do anything
about it since this code is completely changed in the beta driver. Just
check this mailinglist and when the beta driver is a bit more stable
try switching to that one. There is a good chance that that will solve
your problems.
Regards,
Hans
>
> so I'm wondering why ivtv-enc-vbi need be running at all, and it's
> using 30% cpu?
>
> Thanks for any insight,
> Robert Zilcoski
>
>
>
> _______________________________________________
> ivtv-users mailing list
> [email protected]
> http://ivtvdriver.org/mailman/listinfo/ivtv-users
_______________________________________________
ivtv-users mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-users
