Re: [Alsa-user] missing input volume controls in MAYA44 USB
nightmixes wrote: > I bought a MAYA44 USB+ sound card to use in Linux and although is on > the list of compatible devices at http://www.alsa-project.org, I can > not make it work properly. Maybe something is missing because the site > says "under development" That entry was mistakenly copy from the MAYA44, which uses entirely different hardware. > The problem is that there's no volume control on the input lines, and > default volume is too low. [...] > In Windows, the soundcard works fine and have input volume controls. It is likely that these input/monitor controls require some vendor- specific commands (which nobody knows about), but it would be unusual that a device has both vendor-specific and USB class-compliant mixer controls. Please show the output of "lsusb -v" for this device. Regards, Clemens -- One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
[Alsa-user] missing input volume controls in MAYA44 USB
Hello everyone. I bought a MAYA44 USB+ sound card to use in Linux and although is on the list of compatible devices at http://www.alsa-project.org, I can not make it work properly. Maybe something is missing because the site says "under development", so I write hoping that someone can help me. MAYA44 USB+ is identical to MAYA44 USB, only adds a aluminum enclosure ( http://www.esi-audio.com/products/maya44usb+) In a quick search, I see that others have the same problem, but could not find a solution. If someone can put me in the right direction, I have no trouble doing the tests we need, recompile kernel modules or anything else. The problem is that there's no volume control on the input lines, and default volume is too low. In alsamixer, if I select "capture" for this soundcard it shows "This sound device does not have any capture controls". I tried turning up the volume on my sound source, but all I achieve is a saturated, low sound. In Windows, the soundcard works fine and have input volume controls. Specifically, have 12 volume controls, in pairs: INPUT 1, 2 INPUT 3, 4 MONITOR 1, 2 MONITOR 3, 4 OUTPUT 1, 2 OUTPUT 3, 4 Each pair, has a mute button. For comparison, I took a sample of sound from a external hardware mixer and recorded in Audacity with Linux. Later, on a Windows computer, I installed the original drivers, connect the soundcard and I repeated the process of recording the same sample also in Windows Audacity at same "hardware" volume. The result is that in Windows I reach a level of 0dB on the Audacity VU meter with clear audio. In Linux, the same sample not exceed -24dB. This gives me the idea that the Linux driver, as it has no volume control recording, leave the default volume of the soundcard, which is at the minimum. As a note, Audacity in Linux shows me options for record with 1, 2 and 4 input channels in MAYA and I can select it, but the volume input slider is grayed out. I did a search and try different configurations about .asoundrc, try build a module with quirks or even make a driver from scratch, but for now is out of my reach and all I got are errors or noises in my speakers. I also try installing the last kernel from sources, uninstalling pulseaudio, try on other computers, without luck. To make the long story short, the only thing missing are the input volume controls. No errors on syslog or dmesg. Here I copy the technical information that I have, hopefully someone can help me, If anyone needs any further detail, just ask: mint mint # uname -a Linux mint 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:11:08 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux mint mint # cat /proc/asound/version Advanced Linux Sound Architecture Driver Version k3.13.0-24-generic. mint mint # cat /proc/asound/devices 1:: sequencer 2: [29] : control 3: [ 0- 0]: digital audio playback 4: [ 0- 0]: digital audio capture 5: [ 0- 0]: hardware dependent 6: [ 0] : control 7: [ 2- 0]: digital audio playback 8: [ 2- 0]: digital audio capture 9: [ 2] : control 10: [ 1- 9]: digital audio playback 11: [ 1- 8]: digital audio playback 12: [ 1- 7]: digital audio playback 13: [ 1- 3]: digital audio playback 14: [ 1- 3]: hardware dependent 15: [ 1- 2]: hardware dependent 16: [ 1- 1]: hardware dependent 17: [ 1- 0]: hardware dependent 18: [ 1] : control 33:: timer mint mint # aplay -l List of PLAYBACK Hardware Devices card 0: MID [HDA Intel MID], device 0: CX20585 Analog [CX20585 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: NVidia [HDA NVidia], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: NVidia [HDA NVidia], device 7: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: NVidia [HDA NVidia], device 8: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: NVidia [HDA NVidia], device 9: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: USB [MAYA44 USB+], device 0: USB Audio [USB Audio] Subdevices: 1/1 Subdevice #0: subdevice #0 mint mint # aplay -L default Playback/recording through the PulseAudio sound server null Discard all samples (playback) or generate zero samples (capture) pulse PulseAudio Sound Server sysdefault:CARD=MID HDA Intel MID, CX20585 Analog Default Audio Device front:CARD=MID,DEV=0 HDA Intel MID, CX20585 Analog Front speakers surround40:CARD=MID,DEV=0 HDA Intel MID, CX20585 Analog 4.0 Surround output to Front and Rear speakers surround41:CARD=MID,DEV=0 HDA Intel MID, CX20585 Analog 4.1 Surround output to Front, Rear and Subwoofer speakers surround50:CARD=MID,DEV=0 HDA Intel MID, CX20585 Analog 5.0 Surround output to Front, Center and Rear speakers surround51:CARD=MID,DEV=0 HDA Intel MID, CX20585 Analog 5.1 Surround
Re: [Alsa-user] MB with long-standing problem but I really just want to understand what is going on . .
Hello Phil, I am no dev nor very experienced user, however, I'd try to isolate issue. See if alsamixer(console app) is changing in any way. If it shows all channels and everything after the reboot - problem could be with GUI tools. Regards Dmitri On Tue, May 12, 2015 at 10:24 AM, Philip Rhoades wrote: > People, > > I have been using this MotherBoard for years (it is probably the most > reliable one I have ever had): > >http://www.intel.com/p/en_US/support/highlights/dsktpboards/dg45id > > but from the beginning I had trouble with ALSA and the Line In port - > documented here: > > > > http://mailman.alsa-project.org/pipermail/alsa-devel/2009-February/014825.html > > Mostly this has not been a problem since I only use the Line In port on > infrequent occasions but it is annoying that when I do need to use it, > sometimes, the method I have found to activate the port does not work > and now using it seems to have permanently messed up the configuration > for Back Mic for normal use somehow. I have installed Fedora 22 on a > new drive (currently using 21) and booting on the new disk cures the > introduced problem so it appears not to be permanent sound card damage > at all and just some sort of caching or other issue. My procedure for > getting the Line In port used to be this (although it didn't work this > time and just caused a problem with the Back Mic): > > - uninstall PulseAudio (or rename /usr/bin/pulseaudio) > > - stop all apps auto starting that use ALSA > > - reboot > > - systemctl stop alsa-state.service > > - echo 0x0c 0x01813021 > /sys/class/sound/hwC0D2/user_pin_configs > > - echo 1 > /sys/class/sound/hwC0D2/reconfig > > - chmod -R 777 /dev/snd > > - systemctl start alsa-state.service > > Going through this procedure showed up new controls in xfce4-mixer and > everything worked fine for what I wanted to do - a reboot restored the > original setup (it could also be done with echoing the original values). > It has been some years since I used this technique but now I can't get > it to work and some of the new controls that show up in xfce4-mixer > ("Capture 1", "Input Source 1") > don't disappear with a reboot - even if I: > >rm .config/xfce4/xfconf/xfce-perchannel-xml/xfce4-mixer.xml > > !? Also, from Audacity I can now no longer select "Default" for the > microphone and I can't get any of the other options to record . . > > Is anybody able to tell me what is going on? I can just starting using > F22 on the new drive and forget about using this procedure in the future > but I don't like not knowing why things don't work reliably . . > > Any useful information would be appreciated! > > Regards, > > Phil. > -- > Philip Rhoades > > PO Box 896 > Cowra NSW 2794 > Australia > E-mail: p...@pricom.com.au > > > -- > One dashboard for servers and applications across Physical-Virtual-Cloud > Widest out-of-the-box monitoring support with 50+ applications > Performance metrics, stats and reports that give you Actionable Insights > Deep dive visibility with transaction tracing using APM Insight. > http://ad.doubleclick.net/ddm/clk/290420510;117567292;y > ___ > Alsa-user mailing list > Alsa-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/alsa-user > -- One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
[Alsa-user] MB with long-standing problem but I really just want to understand what is going on . .
People, I have been using this MotherBoard for years (it is probably the most reliable one I have ever had): http://www.intel.com/p/en_US/support/highlights/dsktpboards/dg45id but from the beginning I had trouble with ALSA and the Line In port - documented here: http://mailman.alsa-project.org/pipermail/alsa-devel/2009-February/014825.html Mostly this has not been a problem since I only use the Line In port on infrequent occasions but it is annoying that when I do need to use it, sometimes, the method I have found to activate the port does not work and now using it seems to have permanently messed up the configuration for Back Mic for normal use somehow. I have installed Fedora 22 on a new drive (currently using 21) and booting on the new disk cures the introduced problem so it appears not to be permanent sound card damage at all and just some sort of caching or other issue. My procedure for getting the Line In port used to be this (although it didn't work this time and just caused a problem with the Back Mic): - uninstall PulseAudio (or rename /usr/bin/pulseaudio) - stop all apps auto starting that use ALSA - reboot - systemctl stop alsa-state.service - echo 0x0c 0x01813021 > /sys/class/sound/hwC0D2/user_pin_configs - echo 1 > /sys/class/sound/hwC0D2/reconfig - chmod -R 777 /dev/snd - systemctl start alsa-state.service Going through this procedure showed up new controls in xfce4-mixer and everything worked fine for what I wanted to do - a reboot restored the original setup (it could also be done with echoing the original values). It has been some years since I used this technique but now I can't get it to work and some of the new controls that show up in xfce4-mixer ("Capture 1", "Input Source 1") don't disappear with a reboot - even if I: rm .config/xfce4/xfconf/xfce-perchannel-xml/xfce4-mixer.xml !? Also, from Audacity I can now no longer select "Default" for the microphone and I can't get any of the other options to record . . Is anybody able to tell me what is going on? I can just starting using F22 on the new drive and forget about using this procedure in the future but I don't like not knowing why things don't work reliably . . Any useful information would be appreciated! Regards, Phil. -- Philip Rhoades PO Box 896 Cowra NSW 2794 Australia E-mail: p...@pricom.com.au -- One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user