Hi. I have an SB Audigy Rx and if i check PCM and Analog Mix in the KMix panel on Kicker then it shows the capture channels instead of playback. I tried to edit the rc-s, but no effect. There is a picture: http://oscomp.hu/depot/alsamixer_vs_kmix.png As it shows, ALSAMixer can control both capture and playback of PCM and the capture one is muted and down there KMix panel shows the capture one instead of playback.Is this a bug or a config error? - TCH
Ló Béla wrote:
Hi. I have an SB Audigy Rx and if i check PCM and Analog Mix in the KMix panel on Kicker then it shows the capture channels instead of playback. I tried to edit the rc-s, but no effect. There is a picture: http://oscomp.hu/depot/alsamixer_vs_kmix.png As it shows, ALSAMixer can control both capture and playback of PCM and the capture one is muted and down there KMix panel shows the capture one instead of playback.Is this a bug or a config error? - TCH
Can you do a proper screenshot please? I enjoy the tiger, but it is not the subject of the question. To me it looks like false mapping. Perhaps you must provide the correct model setting to your audio driver if it is supported
Identify your card here http://www.alsa-project.org/main/index.php/Matrix:Vendor-Creative_Labs and write back with exact model. The one you cited (SB Audigy Rx) is not in the list. You can get the model by lspci | grep Audio if it is pci card or better cat /proc/asound/cards
From the screenshot I assume you have: Sound Blaster Audigy2 ZS Value, so perhaps this here helps: http://www.alsa-project.org/main/index.php/Matrix:Module-emu10k1
in the screenshot ZS is missing however ... so might be something else.
regards
Can you do a proper screenshot please? I enjoy the tiger, but it is not the subject of the question.
What exactlty you would like to see? My problem is shown on the picture, the KMix panel shows the wrong PCM channel: capture instead of playback.
To me it looks like false mapping. Perhaps you must provide the correct model setting to your audio driver if it is supported > Identify your card here http://www.alsa-project.org/main/index.php/Matrix:Vendor-Creative_Labs and write back with exact model. The one you cited (SB Audigy Rx) is not in the list.
I have this exact card: https://ipon.hu/webshop/product/creative_sound_blaster_audigy_rx/530747
You can get the model by lspci | grep Audio if it is pci card or better cat /proc/asound/cards
root@Csabi:~# lspci | grep Audio 01:00.1 Audio device: NVIDIA Corporation GK208 HDMI/DP Audio Controller (rev a1)
The SB card does not appear like this. I do not use this at all and it does not appears if i hit F6 in alsamixer.
root@Csabi:~# lspci | grep audio 06:00.0 Multimedia audio controller: Creative Labs SB0400 Audigy2 Value
With small "a" the SB card appears but my card is not an Audigy 2.
root@Csabi:~# cat /proc/asound/cards 0 [Audigy2 ]: Audigy2 - SB Audigy 2 Value [Unknown] SB Audigy 2 Value [Unknown] (rev.0, serial:0x10241102) at 0xaf00, irq 18
ALSA does not recognize the Rx card?
From the screenshot I assume you have: Sound Blaster Audigy2 ZS Value, so perhaps this here helps: http://www.alsa-project.org/main/index.php/Matrix:Module-emu10k1
I don't understand. How this helps me, there is no information in this article about the Audigy Rx false recognition as Audigy 2. The soundcoure module is exists at my machine.
However a quick search shows that other people has this problem too: https://forums.linuxmint.com/viewtopic.php?t=199401But i have no problem with the sound or the MIDI, everything works fine, it's just an erroneous channel show in KMix. This article says it needs additional firmware: http://www.linux-hardware-guide.com/in/2014-08-26-creative-sound-blaster-aud... i install the Rx firmware? I installed alsa-firmware-loaders, but i have no firmware to the Rx. - TCH
Ló Béla wrote:
Can you do a proper screenshot please? I enjoy the tiger, but it is not the subject of the question.
What exactlty you would like to see? My problem is shown on the picture, the KMix panel shows the wrong PCM channel: capture instead of playback.
The screenshot is only partially visible. There is no master channel. It reports as Audigy2, so quite messy
To me it looks like false mapping. Perhaps you must provide the correct model setting to your audio driver if it is supported > Identify your card here http://www.alsa-project.org/main/index.php/Matrix:Vendor-Creative_Labs and write back with exact model. The one you cited (SB Audigy Rx) is not in the list.
I have this exact card: https://ipon.hu/webshop/product/creative_sound_blaster_audigy_rx/530747
You can get the model by lspci | grep Audio if it is pci card or better cat /proc/asound/cards
root@Csabi:~# lspci | grep Audio 01:00.1 Audio device: NVIDIA Corporation GK208 HDMI/DP Audio Controller (rev a1)
The SB card does not appear like this. I do not use this at all and it does not appears if i hit F6 in alsamixer.
root@Csabi:~# lspci | grep audio 06:00.0 Multimedia audio controller: Creative Labs SB0400 Audigy2 Value
With small "a" the SB card appears but my card is not an Audigy 2.
root@Csabi:~# cat /proc/asound/cards 0 [Audigy2 ]: Audigy2 - SB Audigy 2 Value [Unknown] SB Audigy 2 Value [Unknown] (rev.0, serial:0x10241102) at 0xaf00, irq 18
ALSA does not recognize the Rx card?
From the screenshot I assume you have: Sound Blaster Audigy2 ZS Value, so perhaps this here helps: http://www.alsa-project.org/main/index.php/Matrix:Module-emu10k1
I don't understand. How this helps me, there is no information in this article about the Audigy Rx false recognition as Audigy 2. The soundcoure module is exists at my machine.
If there is no information, as this is the alsa project page, it would mean it is probably not supported. So why would someone in TDE be able to help you. You better ask for help in the ALSA project/user list.
However a quick search shows that other people has this problem too:
I would bet they have
https://forums.linuxmint.com/viewtopic.php?t=199401But i have no problem with the sound or the MIDI, everything works fine, it's just an erroneous channel show in KMix. This article says it needs additional firmware:
http://www.linux-hardware-guide.com/in/2014-08-26-creative-sound-blaster-aud...
i install the Rx firmware? I installed alsa-firmware-loaders, but i have no firmware to the Rx. - TCH
Yes install the firmware and go to the ALSA people looking for further help.
regards
The screenshot is only partially visible. There is no master channel. It reports as Audigy2, so quite messy
I see. There are the full alsamixer channel list:
http://oscomp.hu/depot/alsamixer_playback_0.png http://oscomp.hu/depot/alsamixer_playback_1.png http://oscomp.hu/depot/alsamixer_playback_2.png http://oscomp.hu/depot/alsamixer_playback_3.png http://oscomp.hu/depot/alsamixer_playback_4.png http://oscomp.hu/depot/alsamixer_capture_0.png http://oscomp.hu/depot/alsamixer_capture_1.png
As you see, alsamixer can handle everything.
If there is no information, as this is the alsa project page, it would mean it is probably not supported. So why would someone in TDE be able to help you.
Because if alsamixer shows the channels correctly and KMix is not, then it's something with TDE and not ALSA.
You better ask for help in the ALSA project/user list.
I will, but still: if the card is recognized erroneously that is an ALSA bug. (Or lack of support.) If alsamixer shows the channels correctly and KMix not, then it's a TDE bug. (Or config problem.)
Yes install the firmware and go to the ALSA people looking for further help.
I will, but this is still a question that why alsamixer shows the channels correctly and why KMix is not.
- TCH
deloptes deloptes@gmail.com írta:
Ló Béla wrote:
Can you do a proper screenshot please? I enjoy the tiger, but it is not the subject of the question.
What exactlty you would like to see? My problem is shown on the picture, the KMix panel shows the wrong PCM channel: capture instead of playback.
The screenshot is only partially visible. There is no master channel. It reports as Audigy2, so quite messy
To me it looks like false mapping. Perhaps you must provide the correct model setting to your audio driver if it is supported > Identify your card here http://www.alsa-project.org/main/index.php/Matrix:Vendor-Creative_Labs and write back with exact model. The one you cited (SB Audigy Rx) is not in the list.
I have this exact card: https://ipon.hu/webshop/product/creative_sound_blaster_audigy_rx/530747
You can get the model by lspci | grep Audio if it is pci card or better cat /proc/asound/cards
root@Csabi:~# lspci | grep Audio 01:00.1 Audio device: NVIDIA Corporation GK208 HDMI/DP Audio Controller (rev a1)
The SB card does not appear like this. I do not use this at all and it does not appears if i hit F6 in alsamixer.
root@Csabi:~# lspci | grep audio 06:00.0 Multimedia audio controller: Creative Labs SB0400 Audigy2 Value
With small "a" the SB card appears but my card is not an Audigy 2.
root@Csabi:~# cat /proc/asound/cards 0 [Audigy2 ]: Audigy2 - SB Audigy 2 Value [Unknown] SB Audigy 2 Value [Unknown] (rev.0, serial:0x10241102) at 0xaf00, irq 18
ALSA does not recognize the Rx card?
From the screenshot I assume you have: Sound Blaster Audigy2 ZS Value, so perhaps this here helps: http://www.alsa-project.org/main/index.php/Matrix:Module-emu10k1
I don't understand. How this helps me, there is no information in this article about the Audigy Rx false recognition as Audigy 2. The soundcoure module is exists at my machine.
If there is no information, as this is the alsa project page, it would mean it is probably not supported. So why would someone in TDE be able to help you. You better ask for help in the ALSA project/user list.
However a quick search shows that other people has this problem too:
I would bet they have
https://forums.linuxmint.com/viewtopic.php?t=199401But i have no problem with the sound or the MIDI, everything works fine, it's just an erroneous channel show in KMix. This article says it needs additional firmware:
http://www.linux-hardware-guide.com/in/2014-08-26-creative-sound-blaster-aud...
i install the Rx firmware? I installed alsa-firmware-loaders, but i have no firmware to the Rx. - TCH
Yes install the firmware and go to the ALSA people looking for further help.
regards
To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
Ló Béla wrote:
I will, but this is still a question that why alsamixer shows the channels correctly and why KMix is not.
KMix is an interface to alsa, so very probably alsa is not recognizing it or reporting it correctly. You did not provide any information about kernel or OS. Are you not using pulse audio? On the alsa page there are some instruction how to configure the devices properly, so that you have consistent mapping. Example
username@hostname# pico /etc/modules.conf
# OSS/Free portion - card #1 alias sound-slot-0 snd-card-0 alias sound-service-0-0 snd-mixer-oss alias sound-service-0-1 snd-seq-oss alias sound-service-0-3 snd-pcm-oss alias sound-service-0-8 snd-seq-oss alias sound-service-0-12 snd-pcm-oss
# OSS/Free portion - card #2 (cmipci) alias sound-slot-1 snd-card-1 alias sound-service-1-0 snd-mixer-oss alias sound-service-1-3 snd-pcm-oss alias sound-service-1-12 snd-pcm-oss
Again, if your card is not supported by ALSA ... even if you see it somehow correct in alsamixer, does not mean it would work without issues. Output of following commands could be of interest though and ask ALSA if your card is fully supported and how it can be configured based on the chip you have
uname -a
lsmod | grep snd
amixer amixer -c 0 amixer -c 1
It could be something in kmix, but I doubt it.
regards
You did not provide any information about kernel or OS.
Debian 8, AMD64, 3.16
Are you not using pulse audio?
No, pulseaudio has been entirely removed from my machine.
On the alsa page there are some instruction how to configure the devices properly, so that you have consistent mapping.
Unfortunately i have no idea what kind of device numbers are exists on the Audigy Rx and if ALSA recognize it badly, then the current layout maybe only partially correct. So, i don't know what aliases should i make. As for the commands:
root@Csabi:~# uname -a Linux Csabi 3.16.0-4-amd64 #1 SMP Debian 3.16.36-1+deb8u2 (2016-10-19) x86_64 GNU/Linux
root@Csabi:~# lsmod | grep snd snd_emu10k1 148204 3 snd_util_mem 12747 1 snd_emu10k1 snd_hwdep 13148 1 snd_emu10k1 snd_rawmidi 27024 1 snd_emu10k1 snd_seq_device 13132 2 snd_rawmidi,snd_emu10k1 snd_ac97_codec 118711 1 snd_emu10k1 snd_pcm_oss 44798 0 snd_mixer_oss 22042 2 snd_pcm_oss snd_pcm 88662 3 snd_pcm_oss,snd_ac97_codec,snd_emu10k1 snd_timer 26668 2 snd_pcm,snd_emu10k1 snd 65338 13 snd_pcm_oss,snd_ac97_codec,snd_hwdep,snd_timer,snd_pcm,snd_rawmidi,snd_emu10k1,snd_seq_device,snd_mixer_oss soundcore 13026 2 snd ac97_bus 12510 1 snd_ac97_codec
root@Csabi:~# amixer Result is here: http://oscomp.hu/depot/amixer.log
root@Csabi:~# amixer -c 0
Result is here: http://oscomp.hu/depot/amixer_c0.log
root@Csabi:~# amixer -c 1 Invalid card number.
It could be something in kmix, but I doubt it.
Unless, it's really that ALSA reports badly something to KMix, it's a KMix issue.
- TCH
Ló Béla wrote:
You did not provide any information about kernel or OS.
Debian 8, AMD64, 3.16
Are you not using pulse audio?
No, pulseaudio has been entirely removed from my machine.
On the alsa page there are some instruction how to configure the devices properly, so that you have consistent mapping.
Unfortunately i have no idea what kind of device numbers are exists on the Audigy Rx and if ALSA recognize it badly, then the current layout maybe only partially correct. So, i don't know what aliases should i make. As for the commands:
root@Csabi:~# uname -a Linux Csabi 3.16.0-4-amd64 #1 SMP Debian 3.16.36-1+deb8u2 (2016-10-19) x86_64 GNU/Linux
root@Csabi:~# lsmod | grep snd snd_emu10k1 148204 3 snd_util_mem 12747 1 snd_emu10k1 snd_hwdep 13148 1 snd_emu10k1 snd_rawmidi 27024 1 snd_emu10k1 snd_seq_device 13132 2 snd_rawmidi,snd_emu10k1 snd_ac97_codec 118711 1 snd_emu10k1 snd_pcm_oss 44798 0 snd_mixer_oss 22042 2 snd_pcm_oss snd_pcm 88662 3 snd_pcm_oss,snd_ac97_codec,snd_emu10k1 snd_timer 26668 2 snd_pcm,snd_emu10k1 snd 65338 13
snd_pcm_oss,snd_ac97_codec,snd_hwdep,snd_timer,snd_pcm,snd_rawmidi,snd_emu10k1,snd_seq_device,snd_mixer_oss
soundcore 13026 2 snd ac97_bus 12510 1 snd_ac97_codec
root@Csabi:~# amixer Result is here: http://oscomp.hu/depot/amixer.log
root@Csabi:~# amixer -c 0
Result is here: http://oscomp.hu/depot/amixer_c0.log
root@Csabi:~# amixer -c 1 Invalid card number.
It could be something in kmix, but I doubt it.
Unless, it's really that ALSA reports badly something to KMix, it's a KMix issue.
- TCH
I looked briefly in the kmix code. There are few places that could be checked, but this will require enable debugging in the code (compiling etc)
But based on your input, this http://www.linux-hardware-guide.com/2014-08-26-creative-sound-blaster-audigy... and this http://alsa.opensrc.org/Emu10k1 https://wiki.debian.org/snd-emu10k1
I think you need at least custom setup to the driver (and perhaps newer kernel version). This way the chance for the driver reporting usable setup is higher.
I think you have to solve this and come back. Perhaps alsamixer can resolve some of the reported features better than kmix, which does not mean that what is reported is correct.
I see there is a lot of information on the web regarding your card. I am not an expert in alsa, but I would look first in this direction. Try at least setting up your device values properly.
I have for example
## ALSA portion alias char-major-116 snd alias snd-card-0 snd-hda-intel alias snd-card-1 snd-usb-audio
## module options should go here options snd-hda-intel index=0 model=ref enable_msi=1 enable=0,1
regards
But based on your input, this http://www.linux-hardware-guide.com/2014-08-26-creative-sound-blaster-audigy... and this http://alsa.opensrc.org/Emu10k1 https://wiki.debian.org/snd-emu10k1%3E I think you need at least custom setup to the driver (and perhaps newer kernel version). This way the chance for the driver reporting usable setup is higher.
I've already installed alsa firmwares and the test programs the articles mentions are running fine. Everything works.
I think you have to solve this and come back. Perhaps alsamixer can resolve some of the reported features better than kmix, which does not mean that what is reported is correct.>> I see there is a lot of information on the web regarding your card. I am not an expert in alsa, but I would look first in this direction. Try at least setting up your device values properly.
I can't solve this, since i have no idea what is the problem. The drivers, firmwares are installed, the card is working, all the channels can be handled from alsamixer... And i have no idea how i can set up my device values properly, because i don't know what are they. There are no documents about what should i alias to what. deloptes deloptes@gmail.com írta:
Ló Béla wrote:
You did not provide any information about kernel or OS.
Debian 8, AMD64, 3.16
Are you not using pulse audio?
No, pulseaudio has been entirely removed from my machine.
On the alsa page there are some instruction how to configure the devices properly, so that you have consistent mapping.
Unfortunately i have no idea what kind of device numbers are exists on the Audigy Rx and if ALSA recognize it badly, then the current layout maybe only partially correct. So, i don't know what aliases should i make. As for the commands:
root@Csabi:~# uname -a Linux Csabi 3.16.0-4-amd64 #1 SMP Debian 3.16.36-1+deb8u2 (2016-10-19) x86_64 GNU/Linux
root@Csabi:~# lsmod | grep snd snd_emu10k1 148204 3 snd_util_mem 12747 1 snd_emu10k1 snd_hwdep 13148 1 snd_emu10k1 snd_rawmidi 27024 1 snd_emu10k1 snd_seq_device 13132 2 snd_rawmidi,snd_emu10k1 snd_ac97_codec 118711 1 snd_emu10k1 snd_pcm_oss 44798 0 snd_mixer_oss 22042 2 snd_pcm_oss snd_pcm 88662 3 snd_pcm_oss,snd_ac97_codec,snd_emu10k1 snd_timer 26668 2 snd_pcm,snd_emu10k1 snd 65338 13
snd_pcm_oss,snd_ac97_codec,snd_hwdep,snd_timer,snd_pcm,snd_rawmidi,snd_emu10k1,snd_seq_device,snd_mixer_oss
soundcore 13026 2 snd ac97_bus 12510 1 snd_ac97_codec
root@Csabi:~# amixer Result is here: http://oscomp.hu/depot/amixer.log
root@Csabi:~# amixer -c 0
Result is here: http://oscomp.hu/depot/amixer_c0.log
root@Csabi:~# amixer -c 1 Invalid card number.
It could be something in kmix, but I doubt it.
Unless, it's really that ALSA reports badly something to KMix, it's a KMix issue.
- TCH
I looked briefly in the kmix code. There are few places that could be checked, but this will require enable debugging in the code (compiling etc)
But based on your input, this http://www.linux-hardware-guide.com/2014-08-26-creative-sound-blaster-audigy... and this http://alsa.opensrc.org/Emu10k1 https://wiki.debian.org/snd-emu10k1
I think you need at least custom setup to the driver (and perhaps newer kernel version). This way the chance for the driver reporting usable setup is higher.
I think you have to solve this and come back. Perhaps alsamixer can resolve some of the reported features better than kmix, which does not mean that what is reported is correct.
I see there is a lot of information on the web regarding your card. I am not an expert in alsa, but I would look first in this direction. Try at least setting up your device values properly.
I have for example
## ALSA portion alias char-major-116 snd alias snd-card-0 snd-hda-intel alias snd-card-1 snd-usb-audio
## module options should go here options snd-hda-intel index=0 model=ref enable_msi=1 enable=0,1
regards
To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
Ló Béla wrote:
I can't solve this, since i have no idea what is the problem. The drivers, firmwares are installed, the card is working, all the channels can be handled from alsamixer... And i have no idea how i can set up my device values properly, because i don't know what are they. There are no documents about what should i alias to what.
and this is the main problem here . I also do not know how it should be setup.
If you think it is a bug in kmix - open a bug ticket. You have to be at least cooperative to assist the developer to verify and investigate.
For example I see this function in kmix, and it will be interesting to know what your system reports. Especially the "Master" is of interest as you complain, you don't see it. It could be a problem in the kmix code, related to the values reported for this chipset. Assuming alsamixer does it right we have a reference, but someone should look and test. Preferably this is you :) But I can not do it here in the list. Either debug yourself or get a ticket opened. You can attach our discussion to the bug.
Mixer_ALSA::identify( snd_mixer_selem_id_t *sid ) { TQString name = snd_mixer_selem_id_get_name( sid );
if ( name == "Master" ) return MixDevice::VOLUME; if ( name == "Capture" ) return MixDevice::RECMONITOR; if ( name == "Master Mono" ) return MixDevice::VOLUME; if ( name == "PC Speaker" ) return MixDevice::VOLUME; if ( name == "Music" || name == "Synth" || name == "FM" ) return MixDevice::MIDI; if ( name.find( "Headphone", 0, false ) != -1 ) return MixDevice::HEADPHONE; if ( name == "Bass" ) return MixDevice::BASS; if ( name == "Treble" ) return MixDevice::TREBLE; if ( name == "CD" ) return MixDevice::CD; if ( name == "Video" ) return MixDevice::VIDEO; if ( name == "PCM" || name == "Wave" ) return MixDevice::AUDIO; if ( name == "Surround" ) return MixDevice::SURROUND_BACK; if ( name == "Center" ) return MixDevice::SURROUND_CENTERFRONT; if ( name.find( "ac97", 0, false ) != -1 ) return MixDevice::AC97; if ( name.find( "coaxial", 0, false ) != -1 ) return MixDevice::DIGITAL; if ( name.find( "optical", 0, false ) != -1 ) return MixDevice::DIGITAL; if ( name.find( "IEC958", 0, false ) != -1 ) return MixDevice::DIGITAL; if ( name.find( "Mic" ) != -1 ) return MixDevice::MICROPHONE; if ( name.find( "LFE" ) != -1 ) return MixDevice::SURROUND_LFE; if ( name.find( "Monitor" ) != -1 ) return MixDevice::RECMONITOR; if ( name.find( "3D", 0, false ) != -1 ) return MixDevice::SURROUND; // Should be probably some own icon
return MixDevice::EXTERNAL; }
then in the loop when setting up the mixer channels
int Mixer_ALSA::open() { ... ... ... MixDevice::ChannelType ct = (MixDevice::ChannelType)identify( sid ); /* if (!masterChosen && ct==MixDevice::VOLUME) { // Determine a nicer MasterVolume m_masterDevice = mixerIdx; masterChosen = true; } */
Okay, thanks for the tips. First, i'll try to debug myself (altough i barely "speak" C++), then if i won't succeed, then i'll open a bug ticket. (But i'm sure noone owns this card among the TDE developers.) If i'll succeed (which is not likely), then i'll send a patch in.
deloptes deloptes@gmail.com írta:
Ló Béla wrote:
I can't solve this, since i have no idea what is the problem. The drivers, firmwares are installed, the card is working, all the channels can be handled from alsamixer... And i have no idea how i can set up my device values properly, because i don't know what are they. There are no documents about what should i alias to what.
and this is the main problem here . I also do not know how it should be setup.
If you think it is a bug in kmix - open a bug ticket. You have to be at least cooperative to assist the developer to verify and investigate.
For example I see this function in kmix, and it will be interesting to know what your system reports. Especially the "Master" is of interest as you complain, you don't see it. It could be a problem in the kmix code, related to the values reported for this chipset. Assuming alsamixer does it right we have a reference, but someone should look and test. Preferably this is you :) But I can not do it here in the list. Either debug yourself or get a ticket opened. You can attach our discussion to the bug.
Mixer_ALSA::identify( snd_mixer_selem_id_t *sid ) { TQString name = snd_mixer_selem_id_get_name( sid );
if ( name == "Master" ) return MixDevice::VOLUME; if ( name == "Capture" ) return MixDevice::RECMONITOR; if ( name == "Master Mono" ) return MixDevice::VOLUME; if ( name == "PC Speaker" ) return MixDevice::VOLUME; if ( name == "Music" || name == "Synth" || name == "FM" ) returnMixDevice::MIDI; if ( name.find( "Headphone", 0, false ) != -1 ) return MixDevice::HEADPHONE; if ( name == "Bass" ) return MixDevice::BASS; if ( name == "Treble" ) return MixDevice::TREBLE; if ( name == "CD" ) return MixDevice::CD; if ( name == "Video" ) return MixDevice::VIDEO; if ( name == "PCM" || name == "Wave" ) return MixDevice::AUDIO; if ( name == "Surround" ) return MixDevice::SURROUND_BACK; if ( name == "Center" ) return MixDevice::SURROUND_CENTERFRONT; if ( name.find( "ac97", 0, false ) != -1 ) return MixDevice::AC97; if ( name.find( "coaxial", 0, false ) != -1 ) return MixDevice::DIGITAL; if ( name.find( "optical", 0, false ) != -1 ) return MixDevice::DIGITAL; if ( name.find( "IEC958", 0, false ) != -1 ) return MixDevice::DIGITAL; if ( name.find( "Mic" ) != -1 ) return MixDevice::MICROPHONE; if ( name.find( "LFE" ) != -1 ) return MixDevice::SURROUND_LFE; if ( name.find( "Monitor" ) != -1 ) return MixDevice::RECMONITOR; if ( name.find( "3D", 0, false ) != -1 ) return MixDevice::SURROUND; // Should be probably some own icon
return MixDevice::EXTERNAL;}
then in the loop when setting up the mixer channels
int Mixer_ALSA::open() { ... ... ... MixDevice::ChannelType ct = (MixDevice::ChannelType)identify( sid ); /* if (!masterChosen && ct==MixDevice::VOLUME) { // Determine a nicer MasterVolume m_masterDevice = mixerIdx; masterChosen = true; } */
To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
Ló Béla wrote:
Okay, thanks for the tips. First, i'll try to debug myself (altough i barely "speak" C++), then if i won't succeed, then i'll open a bug
if you can compile the code with debugging enabled and add additional debug in the function to see what exactly is returned when settings are identified, it will help.
ticket. (But i'm sure noone owns this card among the TDE developers.) If i'll succeed (which is not likely), then i'll send a patch in.
I would open bug anyway and co-work. This is why I said you must be ready to cooperate with the developers. It is still interesting what alsa people may say about this chip and setup.
regards
-
deloptes -
Ló Béla