On Tue, 2006-11-07 at 21:03 +0100, Markus Herhoffer wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> ./alsasound status and the modules are ok. But this is *very* interesting:
>
> # cat /proc/asound/cards
> 0 [M2x2 ]: USB-Audio - MidiSport 2x2
> M-Audio MidiSport 2x2 at usb-0000:00:02.0-2, full speed
> 1 [USB ]: USB-Audio - MAYA44 USB
> AUDIOTRAK MAYA44 USB at usb-0000:00:02.1-1, full speed
>
> WTF? My soundcard is numberd as 1 while my MIDI device is 0. I've
> unplugged the MIDI dev, replugged it and everything worked fine :-)
>
> Thanks for the hint!
>
> Now I just need a solution that the MAYA44 stays number 0. I usually
> unplug and replug the devices to use them on other systems.
>
<pedantic>
Really should not matter - ALSA supports addressing devices by name
which is what apps should be doing.
</pedantic>
> Markus
>
>
>
> Christoph Eckert wrote:
> >> I've successfully run my Maya 44 USB together with the snd-usb-audio
> >> module for more than a year. But after the last update of ALSA some
> >> strange things are going on. "Alsaconf" doesn't find the USB
> >> soundcard although snd-usb-audio is loaded.
> >
> > AFAIR alsaconf is not able to configure USB cards at all.
> >
> > Check the following:
> > /etc/init.d/alsasound status
> > modprobe snd_usb_audio
> > cat /proc/asound/cards
> >
> > ce
> >
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.5 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iD8DBQFFUOaVuXdsp50C0vMRCClbAJ9TG05YrE6lFN6TWllJtlTj6WkgegCeKZB6
> OAMkUgoEf113boKklgPmCJw=
> =Ajhq
> -----END PGP SIGNATURE-----
>
Received on Wed Nov 8 12:15:03 2006
This archive was generated by hypermail 2.1.8 : Mon Nov 13 2006 - 12:19:40 EET