Re: [Alsa-user] Odd problem with MIDI controller

2013-02-13 Thread Jonathan E. Brickman
If I plug in my MIDI controller (Yamaha MO8) *after* Yoshimi has been started, it connects via Jack patchbay perfectly. But if I have my MIDI controller plugged in at boot, it shows up in the patchbay So the driver works correctly. but won't connect Which patchbay is this? You should try t

Re: [Alsa-user] Alsa does not have any controls for iO4

2013-02-13 Thread Clemens Ladisch
Martin G wrote: > a discussion on the Audacity forums led me to believe > it would be normal to see controls in this interface. Most devices have mixer controls there. But controls that are implemented as hardware knobs typically aren't accessible through software. > My situation is that when I

[Alsa-user] Help! I have no way to report an ALSA bug that causes kernel panic

2013-02-13 Thread Aaron Wolf
We have isolated an ALSA bug in the snd_aloop system that causes a kernel panic in a predictable replicable fashion. However, the ALSA website bug tracker is offline and has been for weeks. I decided to try to join the alsa-devel mailing list. I posted a notice about this, but it was marked "Mode

Re: [Alsa-user] Alsa does not have any controls for iO4

2013-02-13 Thread Anders Genell
On 2013-02-13 17:30, Clemens Ladisch wrote: > Martin G wrote: >> in AlsaMixer, when I select the iO4, I get a text message >> that says "This sound device does not have any controls". >> >> Does this not indicate that ALSA is having trouble connecting to the iO4? > It does indicate that ALSA thinks

Re: [Alsa-user] Alsa does not have any controls for iO4

2013-02-13 Thread Clemens Ladisch
Martin G wrote: > in AlsaMixer, when I select the iO4, I get a text message > that says "This sound device does not have any controls". > > Does this not indicate that ALSA is having trouble connecting to the iO4? It does indicate that ALSA thinks that this sound device does not have any controls.

[Alsa-user] Alsa does not have any controls for iO4

2013-02-13 Thread Martin G
ALSA users, I posted a little while ago that there seemed to be a bug with ALSA that was preventing my Alesis iO4 from working properly. It turned I had made a mistake - the bug I was asking about was a Pulse audio bug. However, in AlsaMixer, when I select the iO4, I get a text message that says

Re: [Alsa-user] "Unknown field slaves" with virtual multi-channel device

2013-02-13 Thread Clemens Ladisch
Sheldon Hearn wrote: > On Wed, Feb 13, 2013 at 4:49 PM, Clemens Ladisch wrote: >>> ALSA lib pcm_hw.c:1466:(_snd_pcm_hw_open) Unknown field slaves >> >> The function _snd_pcm_hw_open is the "hw" plugin. >> Apparently, you have changed its definition somewhere. > > What sorts of places might such red

Re: [Alsa-user] "Unknown field slaves" with virtual multi-channel device

2013-02-13 Thread Sheldon Hearn
On Wed, Feb 13, 2013 at 4:49 PM, Clemens Ladisch wrote: >> ALSA lib pcm_hw.c:1466:(_snd_pcm_hw_open) Unknown field slaves > > The function _snd_pcm_hw_open is the "hw" plugin. > Apparently, you have changed its definition somewhere. Gosh, doesn't sound like something I want. It's my first Raspber

Re: [Alsa-user] "Unknown field slaves" with virtual multi-channel device

2013-02-13 Thread Clemens Ladisch
Sheldon Hearn wrote: > ALSA lib pcm_hw.c:1466:(_snd_pcm_hw_open) Unknown field slaves The function _snd_pcm_hw_open is the "hw" plugin. Apparently, you have changed its definition somewhere. Regards, Clemens -- Free Nex

[Alsa-user] "Unknown field slaves" with virtual multi-channel device

2013-02-13 Thread Sheldon Hearn
Hi there, I'm trying to set up a virtual multi-channel device as per this documentation: http://www.alsa-project.org/main/index.php/Asoundrc#Virtual_multi_channel_devices I've adapted the example for my hardware and put it in /etc/asound.conf (included inline below). When I try to test the conf

Re: [Alsa-user] Can't use Alesis iO4, even though a bug fix seems to exist

2013-02-13 Thread Clemens Ladisch
Martin G wrote: > Recently I purchased an Alesis iO4, 4 microphone USB input device for > use with my Ubuntu 12.10 laptop. > > I discovered it didn't work, and according to some very helpful advice > on the Audacity forums, it seems the problem is a bug in ALSA. > [...] > This is the ALSA bug that