Re: [Alsa-user] missing input volume controls in MAYA44 USB
nightmixes wrote: Alsamixer still telling: This sound device does not have any capture controls. What is the output of amixer -c cardnumber controls? Exactly those controls from the mixer map should show up. # amixer -c 1 Simple mixer control 'Master',0 Capabilities: pvolume pswitch pswitch-joined Simple mixer control 'Line',0 Capabilities: pvolume pswitch pswitch-joined Simple mixer control 'Line',1 Capabilities: pvolume pswitch pswitch-joined The controls for ID 10 are missing. Any error messages in the system log? Try adding #define DEBUG at the very beginning of mixer.c to enable the usb_audio_dbg() calls, or adding more logging to the parse_audio_unit() or parse_audio_feature_unit() functions to see where it aborts creating the controls for unit 10. 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
Re: [Alsa-user] missing input volume controls in MAYA44 USB
Hi Clemens! 2015-05-20 5:47 GMT-03:00 Clemens Ladisch cladi...@googlemail.com: nightmixes wrote: I compiled and installed the kernel How exactly? This is different for each distribution. (And the kernel configuration is another problem; it might be a good idea to start with your distribution's kernel source package.) I did 2 tests in different computers, both with Linux Mint 17, in one of them I copied the configuration with make oldconfig in the other I did make menuconfig leaving all as default: in PC 1 wget https://www.kernel.org/pub/linux/kernel/v4.x/linux-4.0.4.tar.xz uncompress, cd linux-4.0.4... make oldconfig make make modules_install install reboot in PC 2 wget https://www.kernel.org/pub/linux/kernel/v4.x/linux-4.0.4.tar.xz uncompress, cd linux-4.0.4... make menuconfig make make modules_install install reboot I took instructions from http://community.linuxmint.com/tutorial/view/1718 I check with uname -a Did you reboot? Did you have a different kernel version previously? Of course I rebooted, both original kernel are 3.13, new is 4.0.4 Alsamixer still telling: This sound device does not have any capture controls. What is the output of amixer -c cardnumber controls? Exactly those controls from the mixer map should show up. mint mint # amixer -c 1 Simple mixer control 'Master',0 Capabilities: pvolume pswitch pswitch-joined Playback channels: Front Left - Front Right Limits: Playback 0 - 255 Mono: Front Left: Playback 0 [0%] [0.00dB] [on] Front Right: Playback 0 [0%] [0.00dB] [on] Simple mixer control 'Line',0 Capabilities: pvolume pswitch pswitch-joined Playback channels: Front Left - Front Right Limits: Playback 0 - 255 Mono: Front Left: Playback 191 [75%] [0.74dB] [off] Front Right: Playback 191 [75%] [0.74dB] [off] Simple mixer control 'Line',1 Capabilities: pvolume pswitch pswitch-joined Playback channels: Front Left - Front Right Limits: Playback 0 - 255 Mono: Front Left: Playback 191 [75%] [0.74dB] [off] Front Right: Playback 191 [75%] [0.74dB] [off] I hope we can solve, I can not wait! ;) Regards. 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
Re: [Alsa-user] missing input volume controls in MAYA44 USB
Hello Clemens, I thought I knew what had to be done, but apparently not.
That's what I did:
- I downloaded the kernel source 4.0.4 from kernel.org
- Then I edited the mixer_maps.c file, I found an entry like this:
static struct usbmix_name_map maya44_map[] = {
/* 1: IT line */
{ 2, Line Playback }, /* FU */
/* 3: IT line */
{ 4, Line Playback }, /* FU */
/* 5: IT pcm playback */
/* 6: MU */
{ 7, Master Playback }, /* FU */
/* 8: OT speaker */
/* 9: IT line */
{ 10, Line Capture }, /* FU */
/* 11: MU */
/* 12: OT pcm capture */
{ }
};
And I duplicated, but this time I called her maya44p_map
I did the same with this entry:
{
.id = USB_ID(0x0a92, 0x0091),
.map = maya44_map,
},
I duplicated it well, but additionally I changed de USB ID:
{
.id = USB_ID(0x2573, 0x0008),
.map = maya44p_map,
},
I compiled and installed the kernel, I check with uname -a, connected the
sound card, I checked the logs and no errors.
Alsamixer still telling: This sound device does not have any capture
controls.
I do not know how to continue, there is a recommendation that steps go from
here?
Thanks again for your time!
Regards.
2015-05-18 12:12 GMT-03:00 nightmixes nightmi...@gmail.com:
Thanks Clemens, I think I understand what to do. I will try to do it
myself, if I have a problem, I tell you.
If I have success, I will also tell you!
Thank you very much!
Regards.
2015-05-18 6:12 GMT-03:00 Clemens Ladisch cladi...@googlemail.com:
nightmixes wrote:
I wondered if the vendor:product id that appears in lsusb may be wrong
and makes fail the Alsa or USB system to identified the device properly.
The MAYA44 indeed indeed has a workaround to change some of its mixer
controls.
What if the device is correctly identified some years ago because I
had a correct ID, but later the manufacturer changed the ID, leaving
the device as unknown or configured as generic.
Your device is not called MAYA44 USB but MAYA44 USB+. I don't know
what actually changed, but this would be a reason for the different ID.
The lsusb output shows that your device uses the same mixer control IDs
as the older device, so the same workaround should work.
You need to add a new entry to the file sound/usb/mixer_maps.c in the
kernel source, and recompile the kernel. Do you know how to do this in
your distribution?
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
Re: [Alsa-user] missing input volume controls in MAYA44 USB
Thanks Clemens, I think I understand what to do. I will try to do it myself, if I have a problem, I tell you. If I have success, I will also tell you! Thank you very much! Regards. 2015-05-18 6:12 GMT-03:00 Clemens Ladisch cladi...@googlemail.com: nightmixes wrote: I wondered if the vendor:product id that appears in lsusb may be wrong and makes fail the Alsa or USB system to identified the device properly. The MAYA44 indeed indeed has a workaround to change some of its mixer controls. What if the device is correctly identified some years ago because I had a correct ID, but later the manufacturer changed the ID, leaving the device as unknown or configured as generic. Your device is not called MAYA44 USB but MAYA44 USB+. I don't know what actually changed, but this would be a reason for the different ID. The lsusb output shows that your device uses the same mixer control IDs as the older device, so the same workaround should work. You need to add a new entry to the file sound/usb/mixer_maps.c in the kernel source, and recompile the kernel. Do you know how to do this in your distribution? 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
Re: [Alsa-user] missing input volume controls in MAYA44 USB
nightmixes wrote: I wondered if the vendor:product id that appears in lsusb may be wrong and makes fail the Alsa or USB system to identified the device properly. The MAYA44 indeed indeed has a workaround to change some of its mixer controls. What if the device is correctly identified some years ago because I had a correct ID, but later the manufacturer changed the ID, leaving the device as unknown or configured as generic. Your device is not called MAYA44 USB but MAYA44 USB+. I don't know what actually changed, but this would be a reason for the different ID. The lsusb output shows that your device uses the same mixer control IDs as the older device, so the same workaround should work. You need to add a new entry to the file sound/usb/mixer_maps.c in the kernel source, and recompile the kernel. Do you know how to do this in your distribution? 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
Re: [Alsa-user] missing input volume controls in MAYA44 USB
Today I discovered something interesting. I wondered if the vendor:product id that appears in lsusb may be wrong and makes fail the Alsa or USB system to identified the device properly. Let me explain better: Apparently the ESI Maya-44 USB must have worked in the past, it is a fairly old and popular soundcard. What if the device is correctly identified some years ago because I had a correct ID, but later the manufacturer changed the ID, leaving the device as unknown or configured as generic. So I began to search the list of IDs in /var/lib/usbutils/usb.ids to find the manufacturer ESI and I not find it. Then, if I search for MAYA and I find this: 0a92 EGO Systems, Inc. 0011 SYS Waveterminal U2A 0021 GIGAPort 0031 GIGAPortAG 0053 Audiotrak Optoplay 0061 U24 Waveterminal 0071 MAYA EX7 0091 Maya 44 00b1 MAYA EX5 1000 MIDI Mate 1010 Romi / O 1020 M4U 1030 M8U 1090 KeyControl49 10A0 KeyControl25 If I search EGO Systems, Inc. without quotes in Google, the first result is www.ego-systems.com and second www.esi-audio.com! All devices listed in the usb.ids file as EGO Systems vendor are products that you can find on the ESI website, in the section product or product archive (http://www.esi-audio.com/products/archive /). In my case, my sound card appears as: Bus 001 Device 003: ID 2573: 0008 It is possible to rename the USB ID to be identified as 0a92:0091 and test if it works properly? Thanks! 2015-05-13 13:44 GMT-03:00 nightmixes nightmi...@gmail.com: Hi Clement, thanks for your time. The lsusb -v output is too long for this list and is rejected with a message: Message body is too big: 80770 bytes with a limit of 60 KB. So, I discard parts as optical mouse, Linux Foundation 2.0 root hub and Intel Corp. Integrated Rate Matching Hub to make a little short message. If you need a complete lsusb -v output, I post it in pastebin: http://pastebin.com/r45pbtFZ Here is my lsusb -v output (only MAYA section): Bus 001 Device 004: ID 2573:0008 ... Regards. -- 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
Re: [Alsa-user] missing input volume controls in MAYA44 USB
Hi Clement, thanks for your time. The lsusb -v output is too long for this list and is rejected with a message: Message body is too big: 80770 bytes with a limit of 60 KB. So, I discard parts as optical mouse, Linux Foundation 2.0 root hub and Intel Corp. Integrated Rate Matching Hub to make a little short message. If you need a complete lsusb -v output, I post it in pastebin: http://pastebin.com/r45pbtFZ Here is my lsusb -v output (only MAYA section): Bus 001 Device 004: ID 2573:0008 Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 1.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x2573 idProduct 0x0008 bcdDevice3.01 iManufacturer 1 ESI Audiotechnik GmbH iProduct2 MAYA44 USB+ iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 295 bNumInterfaces 4 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x00 (Missing must-be-set bit!) (Bus Powered) MaxPower 250mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 0 bInterfaceClass 1 Audio bInterfaceSubClass 1 Control Device bInterfaceProtocol 0 iInterface 0 AudioControl Interface Descriptor: bLength10 bDescriptorType36 bDescriptorSubtype 1 (HEADER) bcdADC 1.00 wTotalLength 142 bInCollection 2 baInterfaceNr( 0) 1 baInterfaceNr( 1) 2 AudioControl Interface Descriptor: bLength12 bDescriptorType36 bDescriptorSubtype 2 (INPUT_TERMINAL) bTerminalID 5 wTerminalType 0x0101 USB Streaming bAssocTerminal 0 bNrChannels 2 wChannelConfig 0x0003 Left Front (L) Right Front (R) iChannelNames 0 iTerminal 0 AudioControl Interface Descriptor: bLength12 bDescriptorType36 bDescriptorSubtype 2 (INPUT_TERMINAL) bTerminalID 3 wTerminalType 0x0603 Line Connector bAssocTerminal 0 bNrChannels 2 wChannelConfig 0x0003 Left Front (L) Right Front (R) iChannelNames 0 iTerminal 0 AudioControl Interface Descriptor: bLength10 bDescriptorType36 bDescriptorSubtype 6 (FEATURE_UNIT) bUnitID 4 bSourceID 3 bControlSize1 bmaControls( 0) 0x01 Mute Control bmaControls( 1) 0x02 Volume Control bmaControls( 2) 0x02 Volume Control iFeature0 AudioControl Interface Descriptor: bLength12 bDescriptorType36 bDescriptorSubtype 2 (INPUT_TERMINAL) bTerminalID 1 wTerminalType 0x0603 Line Connector bAssocTerminal 9 bNrChannels 2 wChannelConfig 0x0003 Left Front (L) Right Front (R) iChannelNames 0 iTerminal 0 AudioControl Interface Descriptor: bLength10 bDescriptorType36 bDescriptorSubtype 6 (FEATURE_UNIT) bUnitID 2 bSourceID 1 bControlSize1 bmaControls( 0) 0x01 Mute Control bmaControls( 1) 0x02 Volume Control bmaControls( 2) 0x02 Volume Control iFeature0 AudioControl Interface Descriptor: bLength15 bDescriptorType36 bDescriptorSubtype 4 (MIXER_UNIT) bUnitID 6 bNrInPins 3 baSourceID( 0) 5 baSourceID( 1) 4 baSourceID( 2) 2 bNrChannels 2 wChannelConfig 0x0003 Left Front (L) Right Front (R) iChannelNames 0 bmControls 0x00 iMixer 0 junk at descriptor end: 00 AudioControl Interface Descriptor: bLength10 bDescriptorType36 bDescriptorSubtype
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 output
