On Wed, 24 Apr 2002, Gunther Thoenes wrote:
>
> option tuner type=37 brings snow noise on xawtv without any acoustics.
I think your tuner is Phillips PAL (this is the default, you don't have to
set the tuner type explictly).
> I use the SB-Live line input with output from my Hifi-amp long time
> bevore I use TV on the PC, it works well in time.
>
Ok. That means it's a FlyVideo issue not a soundcard issue then.
> > After that, if audio still doesn't work, see if 'debug_audio=1' for
> > saa7134 gives you any info on audio detection (dmesg |fgrep saa7134).
>
> # dmesg |fgrep saa7134
> saa7134[0]: found at 02:0d.0, rev: 1, irq: 9, latency: 32, mmio:
> 0xed000000
> saa7134[0]: subsystem: 1131:0000, board: LifeView FlyVIDEO3000
> saa7134[0]/audio: ctl_mute=1 automute=0 input=Television => mute=1
> input=Television
> i2c-core.o: adapter saa7134[0] registered as adapter 0.
> saa7134[0]/audio: tvaudio thread scan start [0]
> saa7134[0]: Huh, no eeprom present (err=-5)?
> saa7134[0]/video: DCSDT: no signal
> saa7134[0]/video: DCSDT: no signal
> tuner: probing saa7134[0] i2c adapter [id=0x90000]
> i2c-core.o: client [Philips PAL] registered to adapter [saa7134[0]](pos.
> 0).
> saa7134[0]: registered device video0 [???]
> saa7134[0]: registered device vbi0
> saa7134[0]: registered device radio0
> saa7134[0]: registered device dsp2
> saa7134[0]: registered device mixer1
> saa7134[0]/video: DCSDT: no signal
> saa7134[0]/video: DCSDT: found PAL
> saa7134[0]/audio: tvaudio thread scan start [1]
> saa7134[0]/audio: scanning 5.500 MHz => dc is 0 [0/0]
> saa7134[0]/audio: scanning 6.000 MHz => dc is 0 [0/0]
> saa7134[0]/audio: scanning 6.500 MHz => dc is 0 [0/0]
Do you still see dc = 0 when you've tuned into a specific channel?
> saa7134[0]/audio: ctl_mute=0 automute=0 input=Television => mute=0
> input=Television
> saa7134[0]/audio: found PAL-BGHI main sound carrier @ 0.000 MHz
>
^^^^^
it shouldn't be zero if you're tuning into a specific channel
Mute = 0 means that sound is enabled.
> Next line comes after start radio and stereo-sound is on xawtv.
>
> saa7134[0]/audio: ctl_mute=0 automute=0 input=Radio => mute=0
> input=Radio
>
> > Last resort, look at the entry for FlyVideo 2000 in saa7134-cards.c, and
> > change the FlyVideo 3000 entry and modify the gpiomask, as well as
> > the entry for TV input to use the amux and gpio values from FV2K,
> > recompile the saa7134 module and reinstall.
>
> This brings all in confusion, I can't change the channels and the sound
> is mono.
>
Ok. Never mind.
> Normal compiled saa7134-0.1.6 without any changes:
> [procedure]
First, run aumix or some other sound mixer to load your sound drivers and
make sure that you get audio output. Then run xawtv.
> 1.0 Starting xawtv-3.74 with a terminel it display motion pictures but
> no
> sound. Then starting radio with an other terminel, sound from the
> right channel comes up in stereo.
I'm not sure if you can tune into both TV and radio channels at the same
time? Anyone knows for sure (Gerd) ?
>
> 1.2 When I switch channels in xawtv sound don't change with.
>
> 1.3 Quit xawtv sound don't quit to.
>
That may be due to your radio application is still active?
> 1.4 Start again xawtv sound goes quit.
> 1.4.1 Radio is dead, I quit it.
>
> 1.6 Select channel MTV in xawtv (this works but no sound).
>
> 1.7 Start radio again MTV-sound comes up.
>
> 2.0 Radio play not radiostations it play TV-sound.
>
>
> I hope this describtion is well to understand.
>
> I've read previous discussion in the video4linux-list
> concerning the saa7134 driver, this is very specialistic
> discussion for me to practise.
>
You can check your dmesg output and see the condition of the mute flag
mute=0 should give you sound, mute=1 means muted. When you first start
xawtv or switch to a new channel, it mutes the audio automatically and
unmutes after it has detected an audio signal. so, you'll see mute=1
-> mute=0 after a channel change. However, in your case, your audio
setting is not right if it has a dc value of 0 after successfully tuning
into a station. (You didn't show your dmesg output after tuning in with
xawtv, so I can't be sure).
Since you managed to get TV sound to work when you enable the radio,
try this:
Change
amux: TV,
to
amux: LINE2,
in the FlyVideo3000 name_tv (TV input) configuration.
(When you select the radio input, it switches the FV3K audio input to
LINE2, which would be done automatically for the TV input in your case
after changing the amux line. However, if this does fix your problem, it
means that the FlyVideo3000 design is different from board to board!!! :( )
T.C.
----
Wan Tat Chee (Lecturer)
School of Computer Science, Univ. Science Malaysia,
11800 Minden, Penang, Malaysia. Ofc Ph: +604 657-7888 x 3617
Internet: tcwan@xxxxxxxxx Web: http://nrg.cs.usm.my/~tcwan
GPG Key : http://nrg.cs.usm.my/~tcwan/tcw_gpg.asc
F'print : FB0F CED7 85A5 ECF9 DEF0 50E8 A550 A0D2 8638 B1EB
