Windows mixer weird problem

Kero · Jan 18, 2008, 11:23 PM

Hello

A friend of mine is using kX 3539 under WinXP SP2, with a SB0102 5.1

He needs some kind of Windows Mixer for compatibility purpose with some programs that asks from which source it must record. However, it doesn't work correctly :

In the mixer options, when he chooses kX Wave SB012 5.1 (b800) 0/1

He has nothing in the Playback part (it stays greyed)
He has only "WaveIn" as a volume control in the recording part
In "Other" he can chose "Master Mixer", and then as "volume control" he has a few sliders that don't seem to do anything.

He needs to have at least Windows recognizing his AC97 in the Recording part, so that he can broadcast what comes from his line in with Oddcast (a shoutcast/icecast plugin for Winamp).

Do you have any clue ?

Kero · Jan 20, 2008, 02:26 AM

Finally we worked it around by using an older version of kX : We don't notice this problem with 3538i, so we're gonna stick with this one for now. It seems to do its job with no problem anyway.

Jan 18, 2008, 11:23 PM	#1
Kero HardwareHeaven Newbie Join Date: Dec 2004 Posts: 11 Rep Power: 0	Windows mixer weird problem Hello A friend of mine is using kX 3539 under WinXP SP2, with a SB0102 5.1 He needs some kind of Windows Mixer for compatibility purpose with some programs that asks from which source it must record. However, it doesn't work correctly : In the mixer options, when he chooses kX Wave SB012 5.1 (b800) 0/1 He has nothing in the Playback part (it stays greyed) He has only "WaveIn" as a volume control in the recording part In "Other" he can chose "Master Mixer", and then as "volume control" he has a few sliders that don't seem to do anything. He needs to have at least Windows recognizing his AC97 in the Recording part, so that he can broadcast what comes from his line in with Oddcast (a shoutcast/icecast plugin for Winamp). Do you have any clue ?

Jan 20, 2008, 02:26 AM	Thread Starter #2
Kero HardwareHeaven Newbie Join Date: Dec 2004 Posts: 11 Rep Power: 0	Finally we worked it around by using an older version of kX : We don't notice this problem with 3538i, so we're gonna stick with this one for now. It seems to do its job with no problem anyway.