On Wednesday 15 November 2006 21:02, Simon Baxter wrote:
> Hi.
>
> I'm using ivtv 0.9 with a PVR-500 - with the pvrinput plugin for VDR.
>
> I'm getting a bunch of error messages when starting the app, and
> trying to record.
>
> When starting up:
> pvrinput: 11:39:05 Detected input 0: Tuner 1
> pvrinput: 11:39:05 Error setting vbi embedded mode, 22:Invalid
> argument pvrinput: 11:39:05 Error setting vbi mode, 22:Invalid
> argument pvrinput: 11:39:05 IVTV_IOC_G_CODEC failed, 22:Invalid
> argument pvrinput: 11:39:06 Detected input 0: Tuner 1
> pvrinput: 11:39:06 IVTV_IOC_G_CODEC failed, 22:Invalid argument
IVTV_IOC_G_CODEC is no longer supported in ivtv-0.8 and up. Instead the
new v4l2 API to set mpeg codec settings is used (see the v4l2 spec).
The big advantage is that the latter is valid for all types of mpeg
cards, not just ivtv. VDR needs to be updated (if it isn't already).
>
> When recording:
> pvrinput: 11:39:58 cPvrDevice::SetChannelDevice 1 4 KOMO 67250 0
> pvrinput: 11:39:58 VIDIOC_S_STD failed, 16:Device or resource busy
> pvrinput: 11:39:58 cPvrDevice::SetChannelDevice 1 4 KOMO 67250 0
> pvrinput: 11:39:58 VIDIOC_S_STD failed, 16:Device or resource busy
> pvrinput: 11:39:58 cPvrDevice::SetChannelDevice 1 4 KOMO 67250 0
> pvrinput: 11:39:58 VIDIOC_S_STD failed, 16:Device or resource busy
Someone is trying to change the TV standard while (probably) a capture
is in progres. That's not allowed and the driver will return a busy
error.
>
> Can anyone help me understand what these IVTV_IOC_G_CODEC and
> VIDIOC_S_STD messages mean?
Hope this helps.
Hans
_______________________________________________
ivtv-users mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-users
