Re: video4linux-list Digest, Vol 11, Issue 59

Clinton Herget <csherg@xxxxxx> · Sat, 29 Jan 2005 10:44:58 -0500

Cyrus,
I have fought and won a battle with this card (box says "PlayTV 
MPEG-2"). At first, like you, I couldn't tune ANYTHING, then after 
massaging my modules.conf and adding some v4lctl settings to rc.local, 
got video working relatively well, but with the awful high-pitched noise 
in the background. Eventually got that working too, but the exact step 
that solved the problem is of course long forgotten. I do remember it 
got much better when I switched from my on-board sound controller to a 
cheap Envy24HT board, but it does sound in your case like it has little 
to do with the sound card. I'm running 2.6.10.
relevant /etc/modules.conf:
options bttv tuner=2 card=70 radio=0
relevant /etc/rc.local:
v4lctl -c /dev/video0 setattr "norm" NTSC
v4lctl -c /dev/video0 setattr "input" Television
v4lctl -c /dev/video0 setattr "audio mode" stereo
v4lctl -c /dev/video0 setattr "mute" off
v4lctl -c /dev/video0 setattr "chroma agc" on
v4lctl -c /dev/video0 setattr "combfilter" on
v4lctl -c /dev/video0 setattr "automute" on
v4lctl -c /dev/video0 setattr "luma decimation filter" on
v4lctl -c /dev/video0 setattr "agc crush" on
v4lctl -c /dev/video0 volume mute off
v4lctl -c /dev/video0 volume 75%
v4lctl -c /dev/video0 setchannel 23
You can obviously ignore chroma/comb/luna/agc filters, but I find they 
make for better quality recordings. What's important, I believe, are 
audio mode, mute, automute, volume, and setchannel. It seems like this 
card won't start recognizing audiomux correctly until it's already been 
tuned to a channel and then changed again, so I solve that by tuning it 
to an arbitrary channel (23 is CNN in my neighborhood :-P) at bootup.
Finally, here is my record script:
#!/bin/sh
#Usage: tvrecord [channel] [duration] [title]
mencoder tv:// -tv driver=v4l2:channel=$1:device=/dev/video0:normid=1:\
width=640:height=480:chanlist=us-cable:adevice=/dev/dsp:amode=1 \
-vf hqdn3d,lavcdeint \
-ovc lavc -lavcopts vcodec=mpeg4:vhq:vbitrate=1200 \
-oac mp3lame -lameopts cbr:br=128:vol=8 \
-ofps 29.97 -endpos $2 -o $3.avi
Pay attention to amode and vol. I recall they both had some mitigating 
effect on the high pitched noise.
In any case, since I fought the same battle I thought I'd throw all of 
this out there, but who knows what will work for you. I've seen so many 
different posts on this card it's hard to keep track. It really seems 
like each person dealing with it has got to find their own solution!
Best,
Clinton
Subject:
Re: pixelview pro (new unsupported revision?)
From:
Cyrus Adkisson <lists@xxxxxxxxxxxxxxxxxx>
Date:
Wed, 26 Jan 2005 15:24:28 -0500
To:
Linux and Kernel Video <video4linux-list@xxxxxxxxxx>
To:
Linux and Kernel Video <video4linux-list@xxxxxxxxxx>

So, I finally got some action out of these new cards. My final 
modprobe.conf configuration was along the lines of
options bttv card=37 tuner=43
options tuner addr=0x61
However, when I tried to capture video (with audio) from these new 
devices, I would always get a high-pitched, shrill noise on top of the 
audio track. The audio seemed fine when just watching TV in xawtv but 
coming directly from the video capture card itself and also when piped 
through an audio card. I have three different types of audio devices, 
and the shrill noise would be produced on all three types. I tried an 
old Winfast 2000 card and the shrill noise was NOT there. I also tried 
multiple versions of both ffmpeg and ALSA, but the problem remained. 
Furthermore, I tried encoding in mpeg2audio and mpeg4 video and mp3 
and mp2 audio. The same issue still came through. I tried recording 
different channels: same thing. All signs point to the problem being 
with the video cards in some way, even though the audio sounds fine 
when used alone with xawtv.
And, in order to exhaust as many possibilities as I could, I tried the 
bttv options card=72 and card=70. With card=72 and xawtv, as I flipped 
through channels, the sound would be mute half the time. One channel 
would have sound, another would not. But, you could scroll up and down 
through the channels and get sound out of stations that had none 
before and vice-versa. With card=70, I got no sound at all.
So.... I'm abandoning these cards for right now. I can't have that 
shrill noise over top of the recordings the computer makes. If anyone 
has any ideas as to why that noise might be happening, I'd appreciate 
some advice.
Cyrus
p.s. Sorry for hijacking the thread earlier. I replied to the message, 
but I thought it would start a new thread if I cleared out the subject 
line, which I did. I guess I was wrong. My bad.
Colin Cross wrote:
Cyrus Adkisson wrote:
Neither setting works to correct my problem. I'm not very 
experienced with bttv, and thus there are two main things that are 
bothering me about this: first, I'm not sure how the 0x60 from the 
"force" parameter translates into 0xc2. Second, what is up with the 
I2C "not found" errors? That can't be good.
Any further help would be appreciated, especially how to force the 
0xc2 part since I can't seem to get that to work right.
Thanks.
Cyrus

The force and ignore parameters seem to appear and disappear.  I 
didn't know about the addr option, that sounds much better.
0x61 is 0xC2 divided by 2, I don't know why, maybe to conserve the 
LSB if its always 0?  The ignore=0x60 tells bttv to ignore the tuner 
found at 0xC0, and the force=0x61 tells bttv to assume a tuner is at 
0xC2.  I guess the addr=0x61 does both.
--

Unsubscribe 
mailto:video4linux-list-request@xxxxxxxxxx?subject=unsubscribe

https://www.redhat.com/mailman/listinfo/video4linux-list

--

Unsubscribe mailto:video4linux-list-request@xxxxxxxxxx?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list