On 12/12/06, Mitch Hulscher <[EMAIL PROTECTED]> wrote:
> Hans Verkuil wrote:
> > On Sunday 10 December 2006 23:40, Hans Verkuil wrote:
> >> On Sunday 10 December 2006 21:12, Mitch Hulscher wrote:
> >>> I'm using the following: Debian sid with kernel 2.6.18, ivtv0.8.2,
> >>> mythtv (version ?), a WinTV PVR-150 MCE and a nintendo gamecube on
> >>> PAL-60 mode.
> >>>
> >>> I'm trying to record a gamecube game using my capture card's
> >>> composite input. On 50hz mode this work fine, on 60hz this doesn't
> >>> work so well. I've tried using "v4l2-ctl PAL-60" and "v4l2-ctl pal"
> >>> as well as all pal-x modes. pal-m comes closest to a good image.
> >>> The problem is basically always the colours being wrong. They're
> >>> mostly greyish. There's also some disturbances around moving
> >>> objects and there's an overall blur.
> >>>
> >>> I've also tried using mythtv and set the mode to PAL-60, to which
> >>> "v4l2-ctl -S" yields "Video standard = 0x00000800 PAL-60". However,
> >>> "v4l2-ctl -s PAL-60" sets it to 0x0000000f. The image however, is
> >>> still the same. All capturing was done with "cat /dev/video0 >
> >>> vid.mpg".
> >>>
> >>> At first I used the debian packages and module-assistant to install
> >>> ivtv, but due to this problem I downloaded the source for 0.8.2 and
> >>> installed it manually. Nothing's changed, though.
> >>>
> >>> Is there anyway I can resolve this issue? I will gladly provide
> >>> more information if required.
> >> Ah nice, someone with the elusive PAL-60 standard :-)
> >>
> >> I'm not surprised this isn't supported, it's quite rare. Can you
> >> start by giving me the IVTV INIT messsages from the kernel log?
> >>
> >> You also will have to setup your environment so you are able to apply
> >> patches to the kernel and to compile it. Personally I would
> >> appreciate it if you could upgrade to 2.6.19 first, but if it is too
> >> much work then 2.6.18 is also fine.
> >
> > A follow-up: I've added the command line option to v4l2-ctl to actually
> > set pal-60. If you get the latest ivtv-0.8 or ivtv-0.9 branch of ivtv
> > then you can set pal-60 with 'v4l2-ctl -s pal-60'. Tomorrow I hope to
> > have a gamecube on loan for the evening from a colleague, so I should
> > be able to test it myself.
>
> Thanks, that would be great! I'm preparing to install the 2.6.19 kernel
> on the capture computer, it's a bit slow so it takes quite a while.
> After doing so I'll eagerly test it out and, should it fail, post the
> ivtv init message and apply patches.
>

I installed both the 2.6.19 kernel and ivtv svn r3678. It's nice to
see "v4l2-ctl -s pal-60" works, except that the colours are still far
from acceptable. Below is the ivtv init message.

ivtv:  ==================== START INIT IVTV ====================
ivtv:  version 0.10.0 (development revision 3678) loading
ivtv:  Linux version: 2.6.19 SMP mod_unload K7 REGPARM
ivtv:  In case of problems please include the debug info between
ivtv:  the START INIT IVTV and END INIT IVTV lines, along with
ivtv:  any module options, when mailing the ivtv-users mailinglist.
ivtv0: Autodetected Hauppauge card (cx23416 based)
ivtv0: loaded v4l-cx2341x-enc.fw firmware (262144 bytes)
ivtv0: Encoder revision: 0x02050032
tveeprom 1-0050: The eeprom says no radio is present, but the tuner type
tveeprom 1-0050: indicates otherwise. I will assume that radio is present.
tveeprom 1-0050: Hauppauge model 26559, rev C260, serial# 2993071
tveeprom 1-0050: tuner model is LG S001D MK3 (idx 60, type 38)
tveeprom 1-0050: TV standards PAL(B/G) PAL(I) SECAM(L/L') PAL(D/D1/K)
(eeprom 0x74)
tveeprom 1-0050: audio processor is CX25843 (idx 37)
tveeprom 1-0050: decoder processor is CX25843 (idx 30)
tveeprom 1-0050: has radio, has no IR remote
ivtv0: Autodetected Hauppauge WinTV PVR-150
tuner 1-0043: chip found @ 0x86 (ivtv i2c driver #0)
tda9887 1-0043: tda988[5/6/7] found @ 0x43 (tuner)
tuner 1-0061: chip found @ 0xc2 (ivtv i2c driver #0)
cx25840 1-0044: cx25843-23 found @ 0x88 (ivtv i2c driver #0)
cx25840 1-0044: loaded v4l-cx25840.fw firmware (16382 bytes)
wm8775 1-001b: chip found @ 0x36 (ivtv i2c driver #0)
ivtv0: Registered device video0 for encoder MPEG (4 MB)
ivtv0: Registered device video32 for encoder YUV (2 MB)
ivtv0: Registered device vbi0 for encoder VBI (1 MB)
ivtv0: Registered device video24 for encoder PCM audio (1 MB)
ivtv0: Registered device radio0 for encoder radio
tuner 1-0061: type set to 38 (Philips PAL/SECAM multi (FM1216ME MK3))
ivtv0: Initialized Hauppauge WinTV PVR-150, card #0
ivtv:  ====================  END INIT IVTV  ====================

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

Reply via email to