logo       

[ tvtime-Bugs-711966 ] Mute/Unmute while in Comp/S-Video switches sound to : msg#00057

video.tvtime.devel

Subject: [ tvtime-Bugs-711966 ] Mute/Unmute while in Comp/S-Video switches sound to tuner

Bugs item #711966, was opened at 2003-03-29 17:30
Message generated for change (Comment added) made by vektor
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=506987&aid=711966&group_id=64301

Category: Capture and tuner related
Group: Open bugs in driver/lib deps
Status: Open
Resolution: None
Priority: 8
Submitted By: Scott Van Wart (silvaran)
Assigned to: Billy Biggs (vektor)
Summary: Mute/Unmute while in Comp/S-Video switches sound to tuner

Initial Comment:
ATI TV Wonder PCI (capture card)
VisionTek GeForce 4 MX420 4xAGP (primary)
Using RH 8.0.94 (Phoebe)

When the input is set to Composite or S-Video, and I
mute, then unmute, I end up with sound coming in from
the tuner (whatever channel it was set to), instead of
the appropriate input, even though the video is still
coming from Composite or S-Video. If no one else can
confirm this, I should be able to give more info, I
hope... thanks..

Ohh, one more thing... Composite/S-Video get their
audio from the same cables, so when this problem occurs
and I am on Composite, when I switch inputs, the next
one is S-Video, and it still doesn't change the sound
to what it's supposed to be (the one in S-Video mode).
The only way to fix it is to switch to tuner, then
switch back to one of the other two modes.

----------------------------------------------------------------------

>Comment By: Billy Biggs (vektor)
Date: 2004-06-23 23:47

Message:
Logged In: YES
user_id=153320

Is this still an issue?

----------------------------------------------------------------------

Comment By: Scott Van Wart (silvaran)
Date: 2003-09-09 09:51

Message:
Logged In: YES
user_id=679666

Am now running CVS-2003-Sep-08. I can't reproduce it
exactly as above, however:

1) Set input to teleivision.
2) Mute.
3) Set input to Composite or S-Video
4) Unmute

You get the audio from the television input. It seems that
swapping 3 and 2 (as was originally reported) no longer
causes a problem...


----------------------------------------------------------------------

Comment By: Scott Van Wart (silvaran)
Date: 2003-04-06 00:54

Message:
Logged In: YES
user_id=679666

>> Maybe newer versions of the bttv driver fix this?
>> I'm using bttv from 2.4.20, and it looks like you are too.

I've had a chance to install RH9. It comes with 2.4.20, but
it has a good deal of backported features, etc. I'm not so
sure about the bttv driver, but since I installed RH9 this
problem has disappeared. So maybe vanilla 2.4.20 still has
the bug, but not the kernel shipped with RH9. I can't
reproduce it anymore. Good thing? Bad thing? :)

Ohhh.. during my last comment, I was running Phoebe (pre-9),
but now I'm running Shrike (9):

# uname -a
Linux hostname.domainname 2.4.20-8 #1 Thu Mar 13 17:18:24
EST 2003 i686 athlon i386 GNU/Linux

Ohhh... RH also backported stuff not only from the 2.5.x
series but from the 2.4.21-pre? kernels. Check out the
changelog:
http://www.kernel.org/pub/linux/kernel/v2.4/testing/patch-2.4.21.log

Search for bttv/tuner/video4linux (pre5, pre4, ..., pre1).
There are quite a few entries... none of them are really
specific though.

----------------------------------------------------------------------

Comment By: Billy Biggs (vektor)
Date: 2003-04-05 23:01

Message:
Logged In: YES
user_id=153320

I played around alot today with my TV wonder and have
decided that it definitely has some bugs. A work around for
some of my problems seemed to be to toggle mute/unmute on
startup, but it's annoying (you hear a tick of audio as
tvtime loads!), and furthermore, after fooling with the
mute/unmute a bit, I was able to get the driver into a bad
state where unmute didn't work at all.

We need to determine where the mute handling code is for
this card, and figure out what part of the driver is at
fault. Maybe newer versions of the bttv driver fix this?
I'm using bttv from 2.4.20, and it looks like you are too.

----------------------------------------------------------------------

Comment By: Scott Van Wart (silvaran)
Date: 2003-03-30 00:31

Message:
Logged In: YES
user_id=679666

tvtime: Running tvtime 0.9.7.
speedycode: CPU AMD Athlon(tm) XP 1600+, family 6, model 6,
stepping 2.
speedycode: CPU measured at 1394.758MHz.
speedycode: Using MMXEXT optimized functions.
deinterlace: Loading Greedy - Low motion (DScaler)...
deinterlace: Loading Bob (DScaler)...
deinterlace: Loading Greedy - 2-frame (DScaler)...
deinterlace: Loading TwoFrame (DScaler)...
deinterlace: Loading Linear Blend (idea from mplayer)...
deinterlace: Loading Linear interpolation...
deinterlace: Loading Weave last field...
deinterlace: Loading Line doubler...
deinterlace: Loading XVideo Bob...
config: Reading configuration from
/home/silvaran/.tvtime/tvtimerc
# Band Channel Freq Name
1 US Cable 1 73250 1
2 US Cable 2 55250 2
...
videoinput: Using video4linux driver 'BT878(ATI TV-Wonder)'.
videoinput: Card type is eb, audio 1.
videoinput: tuner.tuner = 0
videoinput: tuner.name = Television
videoinput: tuner.rangelow = 0
videoinput: tuner.rangehigh = -1
videoinput: tuner.signal = 0
videoinput: tuner.flags = PAL NTSC SECAM
videoinput: tuner.mode = NTSC
videoinput: Brightness 38036, hue 32896, colour 30330,
contrast 26547
videoinput: Whiteness 0, depth 16, palette 7.
videoinput: V4LWIN set to (0,0/720x480), chromakey 0, flags
1, clips 0.
videoinput: tuner.tuner = 0
videoinput: tuner.name = Television
videoinput: tuner.rangelow = 0
videoinput: tuner.rangehigh = -1
videoinput: tuner.signal = 65535
videoinput: tuner.flags = PAL NTSC SECAM
videoinput: tuner.mode = NTSC
tvtime: V4L sampling 720 pixels per scanline.
tvtime: Luma correction disabled.
tvtime: Luma correction value: 1.0
tvtime: Changing to channel 2.
tvtime: Attempting to aquire performance-enhancing features.
tvtime: Disabling VGA port polling.
tvtime: Done stealing resources.
tvtime: could not connect to socket
tvtime: No such file or directory
tvtime: Can't connect to lircd. Lirc disabled.
xvoutput: Display :0.0, vendor The XFree86 Project, Inc,
XFree86 4.2.99.901
xvoutput: Using XVIDEO adaptor 54: NV Video Overlay.

My card has the following ports:
Audio output (jack)
Video in (w/cable)
Cable in
It came with a purple box with attached cable that you plug
into the video in. On the box, there's the composite (A/V,
3 plugs) and S-Video. I plug one end of a jack into the
audio out, and plug the other into the line in on my sound
card (piece of garbage AC97 on-board thing, but hey, it
works)...

# cat /proc/pci
...
Bus 0, device 9, function 0:
Multimedia video controller: Brooktree Corporation Bt878
Video Capture (rev
17).
IRQ 5.
Master Capable. Latency=64. Min Gnt=16.Max Lat=40.
Prefetchable 32 bit memory at 0xcddfe000 [0xcddfefff].
Bus 0, device 9, function 1:
Multimedia controller: Brooktree Corporation Bt878 Audio
Capture (rev 17).
IRQ 5.
Master Capable. Latency=64. Min Gnt=4.Max Lat=255.
Prefetchable 32 bit memory at 0xcddff000 [0xcddfffff].
...

# lsmod | awk '{ print $1 }'
Module
i810_audio
ac97_codec
tuner
msp3400
bttv
videodev
soundcore
i2c-algo-bit
i2c-core
...

# uname -a
Linux hostname.domainname 2.4.20-2.48 #1 Thu Feb 13 11:52:40
EST 2003 i686 athlon i386 GNU/Linux

# dmesg | grep '^bttv'
bttv: driver version 0.7.96 loaded
bttv: using 4 buffers with 2080k (8320k total) for capture
bttv: Host bridge is Silicon Integrated Systems [SiS] 735 Host
bttv: Bt8xx card found (0).
bttv0: Bt878 (rev 17) at 00:09.0, irq: 5, latency: 64, mmio:
0xcddfe000
bttv0: detected: ATI TV Wonder [card=63], PCI subsystem ID
is 1002:0001
bttv0: using: BT878(ATI TV-Wonder) [card=63,autodetected]
bttv0: using tuner=19
bttv0: i2c: checking for MSP34xx @ 0x80... found
bttv0: i2c attach [client=MSP3430G-B6,ok]
bttv0: i2c: checking for TDA9875 @ 0xb0... not found
bttv0: i2c: checking for TDA7432 @ 0x8a... not found
bttv0: i2c attach [client=Philips NTSC (FI1236 and compati,ok]
bttv0: registered device video0
bttv0: registered device vbi0
bttv0: PLL: 28636363 => 35468950 ... ok
bttv0: PLL: switching off

# dmesg | grep '^tuner'
i2c-core.o: driver i2c TV tuner driver registered.
tuner: probing bt848 #0 i2c adapter [id=0x10005]
tuner: chip found @ 0xc0

# dmesg | grep '^msp' # whatever this is
msp34xx: init: chip=MSP3430G-B6, has NICAM support
msp3410: daemon started

Strange... btaudio and tvaudio aren't loaded... ohh well,
sound works anyways...

----------------------------------------------------------------------

Comment By: Billy Biggs (vektor)
Date: 2003-03-29 19:12

Message:
Logged In: YES
user_id=153320

I've reproduced a similar problem though. Start running
tvtime on the non-tuner input and you get the tuner audio.
Argh. These bugs are probably related.

----------------------------------------------------------------------

Comment By: Billy Biggs (vektor)
Date: 2003-03-29 17:47

Message:
Logged In: YES
user_id=153320

What version of tvtime are you running? Can you show me the
output of 'tvtime -v'?

I'm surprised by your post. First of all, I also have an
ATI TV Wonder card, and I cannot reproduce your first
problem about getting audio from the tuner when on a
separate input. Maybe that is a bug in your tuner driver?
Which tuner are you using?

Regarding the composite/s-video, are you using the audio
input on the ATI TV Wonder? I've never used it before, and
did not even know I could switch to that input. I do
nothing special in tvtime, I just set the audio mute/unmute,
I did not think there were multiple channels. I'll look
into this though and try and figure out what's up.

Thanks for your bug report.

----------------------------------------------------------------------

You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=506987&aid=711966&group_id=64301


-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
digital self defense, top technical experts, no vendor pitches,
unmatched networking opportunities. Visit www.blackhat.com


<Prev in Thread] Current Thread [Next in Thread>
Google Custom Search

News | FAQ | advertise