[mythtv-users] Fwd: Guidance to get Hauppauge WinTV-PVR 350 to work on PAL-N

Fri Apr 14 20:22:41 UTC 2006

Still lost ....

Spent another long night with this mythTV install with not much
progress. This is the new info on this topic:
- After importing
HKEY_LOCAL_MACHINE\SOFTWARE\Hauppauge\hcwPNP\Override]
"VideoFormat"=dword:0000003f on the registry and setting the program
WinTV2000 to use "PAL-N" as a format, video is displayed in colors,
perfect under Windows
- Trying to reproduce the same under Linux gives no good result. Using
mythtv-setup to set "TV-FORMAT" to PAL-N didn't help. Also using the
channel editor to set the format of specific channels to PAL-N doesn't
seem to do anything useful.

Finally, trying to tune and watch directly from the card using mplayer
/dev/video0 was not very fruitful:

0) ivtvctl -p 4 (set input to 4 = Tuner 0)
1) ivtvctl -u 0 (set standard = NTSC)
2) ptune.pl -c 2 (tune channel 2)
3) mplayer /dev/video0   --> Displays the channel in B&W (aka NTSC)

0) ivtvctl -p 4 (set input to 4 = Tuner 0)
1) ivtvctl -u 1 (set standard = PAL)
2) ptune.pl -c 2 (tune channel 2)
3) mplayer /dev/video0   --> Displays only garbage

At this point, I don't know what else can be done under Linux to get
PAL-N out of the WinTV PVR-350. Does anybody have any advice?

In particular, it'd be nice to know exactly what is mythTV doing with
the values set to "TV-FORMAT" and in the Channel editor configuration.
How can an equivalent thing be done manually from outside mythTV, just
to check everything is fine?

Just in case it helps, here is the modprobe.conf configuration:

------------------------------------------------------------------------------------------------
alias char-major-61 lirc_i2c
alias char-major-81 videodev
#alias char-major-81 -0 ivtv
#alias char-major-81 -1 bttv
#alias /dev/v4l ivtv
#options tveeprom debug=2
#options ivtv ivtv_debug=1 ivtv_std=2 tuner=20
#options ivtv tuner=5
#options tuner debug=1
#options saa7127 enable_output=1 output_select=0 pal=1
options saa7127 enable_output=1 output_select=0
options msp3400 once=1 simple=1
install ivtv /sbin/modprobe tuner; /sbin/modprobe msp3400; /sbin/modprobe saa711
5;  /sbin/modprobe --ignore-install  ivtv
remove ivtv /sbin/modprobe -r --ignore-remove ivtv && /sbin/modprobe -r saa7115
&& /sbin/modprobe -r msp3400 && /sbin/modprobe -r tuner
-------------------------------------------------------------------------------------------------------------

and below the output of the ITVT section in /var/log/messages:

--------------------------------------------------------------------------------------------------------------
Apr 13 21:08:38 mythtv0 kernel: ivtv:  ==================== START INIT IVTV ====
================
Apr 13 21:08:38 mythtv0 kernel: ivtv:  version 0.4.0 (tagged release) loading
Apr 13 21:08:38 mythtv0 kernel: ivtv:  Linux version: 2.6.13.2-chw-3 SMP preempt
 586 gcc-3.3
Apr 13 21:08:38 mythtv0 kernel: ivtv:  In case of problems please include the de
bug info
Apr 13 21:08:38 mythtv0 kernel: ivtv:  between the START INIT IVTV and END INIT
IVTV lines when
Apr 13 21:08:38 mythtv0 kernel: ivtv:  mailing the ivtv-devel mailinglist.
Apr 13 21:08:38 mythtv0 kernel: ivtv0: Autodetected WinTV PVR 350 card (iTVC15 b
ased)
Apr 13 21:08:38 mythtv0 kernel: ACPI: PCI Interrupt 0000:00:12.0[A] -> Link [LNK
D] -> GSI 10 (level, low) -> IRQ 10
Apr 13 21:08:38 mythtv0 kernel: ivtv0: Unreasonably low latency timer, setting t
o 64 (was 32)
Apr 13 21:08:38 mythtv0 kernel: tuner (ivtv): chip found at addr 0xc2 i2c-bus iv
tv i2c driver #0
Apr 13 21:08:38 mythtv0 kernel: ivtv0: i2c attach to card #0 ok [client=(tuner u
nset), addr=61]
Apr 13 21:08:38 mythtv0 kernel: msp34xx: ivtv version
Apr 13 21:08:38 mythtv0 kernel: msp34xx: init: chip=MSP3448W-A2, has NICAM suppo
rt, simple (D) mode, simpler (G) no-thread mode
Apr 13 21:08:38 mythtv0 kernel: msp34xx: $Id$ compiled on: Oct  9 2005 22:52:16
Apr 13 21:08:38 mythtv0 kernel: ivtv0: i2c attach to card #0 ok [client=MSP3448W
-A2, addr=40]
Apr 13 21:08:38 mythtv0 kernel: saa7115 1-0021: saa7115 found @ 0x42 (ivtv i2c d
river #0)
Apr 13 21:08:38 mythtv0 kernel: ivtv0: i2c attach to card #0 ok [client=saa7115,
 addr=21]
Apr 13 21:08:38 mythtv0 kernel: tveeprom: ivtv version
Apr 13 21:08:38 mythtv0 kernel: tveeprom: Hauppauge: model = 48132, rev = K268,
serial# = 2914028
Apr 13 21:08:38 mythtv0 kernel: tveeprom: tuner = LG TAPE H001F MK3 (idx = 68, t
ype = 47)
Apr 13 21:08:38 mythtv0 kernel: tveeprom: tuner fmt = NTSC(M) (eeprom = 0x08, v4
l2 = 0x00001000)
Apr 13 21:08:38 mythtv0 kernel: tveeprom: audio processor = MSP4448 (type = 1b)
Apr 13 21:08:38 mythtv0 kernel: tveeprom: decoder processor = SAA7115 (type = 13
)
Apr 13 21:08:38 mythtv0 kernel: ivtv0: i2c attach to card #0 ok [client=tveeprom
, addr=50]
Apr 13 21:08:38 mythtv0 kernel: tda9885/6/7: (ivtv) chip found @ 0x86
Apr 13 21:08:38 mythtv0 kernel: ivtv0: i2c attach to card #0 ok [client=tda9887,
 addr=43]
Apr 13 21:08:38 mythtv0 kernel: ivtv0: loading /lib/modules/ivtv-fw-enc.bin
Apr 13 21:08:38 mythtv0 kernel: ivtv0: loading /lib/modules/ivtv-fw-dec.bin
Apr 13 21:08:38 mythtv0 kernel: ivtv0: Encoder revision: 0x02040011
Apr 13 21:08:38 mythtv0 kernel: ivtv0: Decoder revision: 0x02020023
Apr 13 21:08:38 mythtv0 kernel: ivtv0: Allocate DMA encoder MPEG stream: 128 x 3
2768 buffers (4096KB total)
Apr 13 21:08:38 mythtv0 kernel: ivtv0: Allocate DMA encoder YUV stream: 194 x 10
800 buffers (2048KB total)
Apr 13 21:08:38 mythtv0 kernel: ivtv0: Allocate DMA encoder VBI stream: 120 x 17
472 buffers (2048KB total)
Apr 13 21:08:38 mythtv0 kernel: ivtv0: Allocate DMA encoder PCM audio stream: 45
5 x 4608 buffers (2048KB total)
Apr 13 21:08:38 mythtv0 kernel: ivtv0: Create encoder radio stream
Apr 13 21:08:38 mythtv0 kernel: ivtv0: Allocate DMA decoder MPEG stream: 16 x 65
536 buffers (1024KB total)
Apr 13 21:08:38 mythtv0 kernel: ivtv0: Allocate DMA decoder VBI stream: 512 x 20
48 buffers (1024KB total)
Apr 13 21:08:38 mythtv0 kernel: ivtv0: Create decoder VOUT stream
Apr 13 21:08:38 mythtv0 kernel: ivtv0: Allocate DMA decoder YUV stream: 24 x 432
00 buffers (1024KB total)
Apr 13 21:08:38 mythtv0 kernel: ivtv0: loading /lib/modules/ivtv_init_mpeg.bin
Apr 13 21:08:38 mythtv0 kernel: tuner: type set to 47 (LG NTSC (TAPE series)) by
 ivtv i2c driver #0
Apr 13 21:08:38 mythtv0 kernel: ivtv0 warning: i2c client addr: 0x44 not found f
or command 0x40046502!
Apr 13 21:08:38 mythtv0 kernel: ivtv0: Initialized WinTV PVR 350, card #0
Apr 13 21:08:38 mythtv0 kernel: ivtv:  ====================  END INIT
IVTV  ====================
-----------------------------------------------------------------------------------------------

Any advice is appreciated.

Julian.

---------- Forwarded message ----------
From: Julian Cerruti <jcerruti at gmail.com>
Date: Apr 10, 2006 6:30 PM
Subject: Re: [mythtv-users] Guidance to get Hauppauge WinTV-PVR 350 to
work on PAL-N
To: mythtv-users at mythtv.org

Another piece of information.
I have a friend that reports being able to run the WinTV PVR 350 under
Windows after:
- Installing the drivers and apps. that come on the CD
- Making the following addition/change to the registry:
[HKEY_LOCAL_MACHINE\SOFTWARE\Hauppauge\hcwPNP\Override]
"VideoFormat"=dword:0000003f

It looks kind of similar to what ivtvctl does when it sets the
standard to PAL (as described below by myself). I wonder if this gives
any hint to anybody on the list about what is going on on my friend's
Windows box and how to reproduce it under Linux

Thanks,
Julian.

On 4/10/06, Julian Cerruti <jcerruti at gmail.com> wrote:
> Thanks for the tip Jeff.
>
> I'm very sorry I can't put my hands on the system right now (it is
> actually on a freind's house where I will go in a couple of days) so I
> can't provide with the particular log information and output of tests.
> I need to resort to my memory for now.
>
> I do remember that we played around quite a bit with ivtvctl. In
> particular, there was an option to "set standard" which would accept
> values "1-NTSC, 2-PAL and 3-SECAM", but that alone didn't appear to
> help.
>
> My conclusion that setting ivtvctl to PAL was not enough was based on
> tuning the board to a valid frequency with itvt-tune and then doing
> mplayer /dev/video0. Do you know if this a conclusive way to tell the
> tuner is working or not?
>
> I also noted that depending on the tuner type that I set on the driver
> options (either on module ivtv or in module tuner), then the
> "available options" for the "set standard" command in ivtvctl appear
> to change. Nevertheless, I don't know if I'm doing the right thing by
> changing the tuner type setting from what tveeprom detects.
>
> Do you know what would be the right strategy for the "tuner type"
> setting in the ivtv and/or tuner driver modules?
> Also, do you know if I should find and load a different firmware into the tuner?
>
> Thanks for the info
> Julian
>
> On 4/10/06, Jeff Simpson <jeffsimpson at alum.wpi.edu> wrote:
> > On 4/10/06, Julian Cerruti <jcerruti at gmail.com> wrote:
> > > Hello mythtv-users,
> > >
> > > I'm trying to get a Hauppauge WinTV-PVR 350 to work under KnoppMyth
> > > using PAL-N standard and would appreciate any guidance, pointers or
> > > tips on how to do this.
> > >
> > > In particular, I'm a little bit confused about which options should be
> > > set where and how to test a given step of the config is working
> > > properly.
> > >
> > > I've noticed that ivtv and associated drivers (tuner, tveeprom, etc.)
> > > have options that appear to be related to this configuration (i.e.:
> > > tuner=47 or type=5 or ivtv_std=2) but had no luck with the multiple
> > > configuration values I tried.
> > >
> > > Also, there are some configuration values in mythtv-setup (in the
> > > channel editor, for example) that appear to be related. Of course I
> > > tried setting them to PAL-N with no result.
> > >
> > > Finally, I noticed that .xawtv has some options related to tv standard
> > > and frequency table that appear to be affecting what mythtv shows.
> > >
> > > In short, I would greatly appreciate any orientation, pointer or
> > > information that can help me understand what I should do to get my
> > > WinTV-PVR 350 to tune PAL-N
> >
> > I don't know much of PAL setup, but I know that the utility ivtvctl
> > can be used to change to that format for encoding / decoding, so give
> > some of those options a try (type the command by itself for a listing
> > of options)
> >
> >  - Jeff
> >
> >
>