9 Sep
2012
9 Sep
'12
10:19 p.m.
On Sunday 09 September 2012 20:54, jy wrote:
2012/9/9 Nigel Henry <cave.dnb2m97pp(a)aliceadsl.fr>
> On Sunday 09 September 2012 18:57, jy wrote:
> > Hi all,
> >
> > I've recently installed ubuntustudio 12.04 and after trying it out, i
> > discovered that my M-Audio Oxygen8 v2 MIDI USB (yes it is class
>
> compliant)
>
> > keyboard is not recognised.
> > It was recognised out of the box on my previous setup based on ubuntu
> > 10.04.
> >
> > By not recognized, i mean that it doesn't appear in qjackctl
> > connexions. thus i cant route the connexions correctly...
> > Below are some logs !
> >
> > How come it doesn't work any more ? How can i correct this ?
> >
> > Thanks a lot
> >
> > Cheers,
> > jy
> >
> > ####LOGS####
> > $cat /proc/asound/cards
> > 0 [Intel ]: HDA-Intel - HDA Intel
> > HDA Intel at 0xf0400000 irq 45
>
> It's not showing up in the cards list above, which seems to indicate that
> the
> snd_usb_audio module isn't loaded, or you've forgotten to switch the
> keyboard
> on. Have a look in lsmod to see if the module is showing there.
>
> If not, load it with.
> sudo modprobe snd_usb_audio
>
> Then see if the keyboard shows up in the cards list.
>
> Nigel.
So :
* module snd_usb_audio is already loaded
* after running aj2midid -e, keyboard is still missing from ALSA and JACK
tabs...
It's true that I was surprised that the keyboard did not appear in
/proc/asound/cards but as it does appear in amidi -l, i'm thinking that
alsa is correctly recognizing the keyboard... Could i be wrong?
Thing is I'm not sure if this is an ALSA issue or jack/qjackctl one.
how could i troubleshoot this ?
jy
Please send replies to the list and put your replies at the bottom of the
post, which makes it easier to follow.
Ok. It does need to be listed as a card in /proc/asound/cards, just as a
webcam with built in mike (although not a soundcard as such) will have a card
entry and uses snd_usb_audio. So why isn't it there?
Does it need firmware loading? I know some M-audio keyboards do. My Evolution
keyboard doesn't, but someone with the same as yours will say.
Have you tried it in a different USB slot if you have spare ones? Not in a
hub as some USB things don't like hubs.
The only other thing I can think of is that both the sound card and the
keyboard are trying to grab card0 and the soundcard is winning, thus the
keyboard can't use it. Now I've seen this the other way round due to the USB
coming up early in the boot process and my keyboard grabbing card0 leaving no
place for the actual soundcard.
This is a very old problem, but may for some reason be happening in your case,
so I suggest putting some index options in /etc/modprobe.d/options, which
will at least confirm if that is the problem or not. See below.
options snd_hda_intel index=0
options snd_usb-audio index=1
Best to reboot and then see if /proc/asound/cards lists both.
If not I'm a bit perplexed.
Nigel.
> _______________________________________________
> Linux-audio-user mailing list
> Linux-audio-user(a)lists.linuxaudio.org
> http://lists.linuxaudio.org/listinfo/linux-audio-user
9 Sep
9 Sep
10:25 p.m.
New subject: MIDI keyboard not recognized
On Sun, Sep 9, 2012 at 4:19 PM, Nigel Henry <cave.dnb2m97pp(a)aliceadsl.fr>wrote;wrote:
[ ... ]
what is super-wierd about this is that amidi can see it, and lists it as
hw:1,0,0
10 Sep
10 Sep
4:31 p.m.
New subject: MIDI keyboard not recognized
On Sunday 09 September 2012 22:25, Paul Davis wrote:
On Sun, Sep 9, 2012 at 4:19 PM, Nigel Henry
<cave.dnb2m97pp(a)aliceadsl.fr>wrote;wrote: [ ... ]
what is super-wierd about this is that amidi can see it, and lists it as
hw:1,0,0
I must say that I didn't take much notice of that at the time, but was more
taken by the missing card in /proc/asound/cards.
I see his lsusb also lists an integrated webcam no doubt with a mike which
will be using snd_usb_audio, which if that is so, that's not showing in the
cards list. I know I'm clutching at straws but wonder if the webcams mike is
also trying for card1 and causing some sort of conflict with snd_usb_audio.
I suppose it's worth unplugging the keyboard and seeing if snd_usb_audio turns
up in /proc/asound/cards for the webcam mike as card1.
If it does I'm not sure how you set the index options for multiple devices
using snd_usb_audio.
Nigel.
4:40 p.m.
New subject: MIDI keyboard not recognized
2012/9/10 Nigel Henry <cave.dnb2m97pp(a)aliceadsl.fr>
Nigel.
On Sunday 09 September 2012 22:25, Paul Davis wrote:
I never had any trouble with the integrated webcam before. The mic was
properly recognised/
On Sun, Sep 9, 2012 at 4:19 PM, Nigel Henry
<cave.dnb2m97pp(a)aliceadsl.fr>wrote;wrote: [ ... ]
what is super-wierd about this is that amidi can see it, and lists it as
hw:1,0,0
I must say that I didn't take much notice of that at the time, but was more
taken by the missing card in /proc/asound/cards.
I see his lsusb also lists an integrated webcam no doubt with a mike which
will be using snd_usb_audio, which if that is so, that's not showing in the
cards list. I know I'm clutching at straws but wonder if the webcams mike
is
also trying for card1 and causing some sort of conflict with snd_usb_audio.
I suppose it's worth unplugging the keyboard and seeing if snd_usb_audio
turns
up in /proc/asound/cards for the webcam mike as card1.
From memory, it doesn't but i'm gonna check it out.
If it does I'm not sure how you set the index options for multiple devices
using snd_usb_audio.
if it's the case, i'll find a way :)
jy
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-user
9:51 a.m.
New subject: MIDI keyboard not recognized
2012/9/9 Nigel Henry <cave.dnb2m97pp(a)aliceadsl.fr>
On Sunday 09 September 2012 20:54, jy wrote:
Oups! Sorry i didn't mean to ! I assumed that the list would handle replies
but I made a mistake. My bad !
2012/9/9 Nigel Henry <cave.dnb2m97pp(a)aliceadsl.fr>
> On Sunday 09 September 2012 18:57, jy wrote:
> > Hi all,
> >
> > I've recently installed ubuntustudio 12.04 and after trying it out, i
> > discovered that my M-Audio Oxygen8 v2 MIDI USB (yes it is class
>
> compliant)
>
> > keyboard is not recognised.
> > It was recognised out of the box on my previous setup based on ubuntu
> > 10.04.
> >
> > By not recognized, i mean that it doesn't appear in qjackctl
> > connexions. thus i cant route the connexions correctly...
> > Below are some logs !
> >
> > How come it doesn't work any more ? How can i correct this ?
> >
> > Thanks a lot
> >
> > Cheers,
> > jy
> >
> > ####LOGS####
> > $cat /proc/asound/cards
> > 0 [Intel ]: HDA-Intel - HDA Intel
> > HDA Intel at 0xf0400000 irq 45
>
> It's not showing up in the cards list above, which seems to indicate
that
> the
> snd_usb_audio module isn't loaded, or you've forgotten to switch the
> keyboard
> on. Have a look in lsmod to see if the module is showing there.
>
> If not, load it with.
> sudo modprobe snd_usb_audio
>
> Then see if the keyboard shows up in the cards list.
>
> Nigel.
So :
* module snd_usb_audio is already loaded
* after running aj2midid -e, keyboard is still missing from ALSA and JACK
tabs...
It's true that I was surprised that the keyboard did not appear in
/proc/asound/cards but as it does appear in amidi -l, i'm thinking that
alsa is correctly recognizing the keyboard... Could i be wrong?
Thing is I'm not sure if this is an ALSA issue or jack/qjackctl one.
how could i troubleshoot this ?
jy
Please send replies to the list and put your replies at the bottom of the
post, which makes it easier to follow.
Ok. It does need to be listed as a card in /proc/asound/cards, just as a
webcam with built in mike (although not a soundcard as such) will have a
card
entry and uses snd_usb_audio. So why isn't it there?
Does it need firmware loading? I know some M-audio
keyboards do. My
Evolution
keyboard doesn't, but someone with the same as yours will say.
Nope. The very same keyboard was properly recognized with my previous setup
(ubuntu 10.04). Plus it's USB class compliant.
Have you tried it in a different USB slot if you have spare ones? Not in a
hub as some USB things don't like hubs.
I use the very same slot that I used on my previous setup.
The only other thing I can think of is that both the sound card and the
keyboard are trying to grab card0 and the soundcard is winning, thus the
keyboard can't use it. Now I've seen this the other way round due to the
USB
coming up early in the boot process and my keyboard grabbing card0 leaving
no
place for the actual soundcard.
This is a very old problem, but may for some reason be
happening in your
case,
so I suggest putting some index options in /etc/modprobe.d/options, which
will at least confirm if that is the problem or not. See below.
options snd_hda_intel index=0
options snd_usb-audio index=1
Best to reboot and then see if /proc/asound/cards lists both.
Seems a good idea ! I'll try that. I might not be able to do it before
tomorrow
though...
Still it's strange that the keyboard does not appear in /proc/asound/cards
The other thing that strikes me is that on my previous setup after
installing my soundcard drivers (Realtek ACL888), /proc/asound/cards listed
3 different ones : ACL888 anog, ACL888 digital and some kind of HDMI sound
card.
Here wiht my new setup, /proc/asound/cards only lists 1 sound card HDA
intel but aplay -l lists the 3 i was telling you about above...
That doesn't seem right to me... :-/
Thanks a lot
jy
If not I'm a bit perplexed.
Nigel.
>
_______________________________________________
> Linux-audio-user mailing list
> Linux-audio-user(a)lists.linuxaudio.org
> http://lists.linuxaudio.org/listinfo/linux-audio-user
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-user
5:04 p.m.
New subject: MIDI keyboard not recognized
On Monday 10 September 2012 09:50, jy wrote:
2012/9/9 Nigel Henry
<cave.dnb2m97pp(a)aliceadsl.fr>
Yeh, that's another little problem.
On Sunday 09 September 2012 20:54, jy wrote:
Please send replies to the list and put your replies at the bottom of the
post, which makes it easier to follow.
Oups! Sorry i didn't mean to ! I assumed that the list would handle replies
but I made a mistake. My bad !
2012/9/9 Nigel Henry
<cave.dnb2m97pp(a)aliceadsl.fr>
> On Sunday 09 September 2012 18:57, jy wrote:
> > Hi all,
> >
> > I've recently installed ubuntustudio 12.04 and after trying it out,
> > i discovered that my M-Audio Oxygen8 v2 MIDI USB (yes it is class
>
> compliant)
>
> > keyboard is not recognised.
> > It was recognised out of the box on my previous setup based on
> > ubuntu 10.04.
> >
> > By not recognized, i mean that it doesn't appear in qjackctl
> > connexions. thus i cant route the connexions correctly...
> > Below are some logs !
> >
> > How come it doesn't work any more ? How can i correct this ?
> >
> > Thanks a lot
> >
> > Cheers,
> > jy
> >
> > ####LOGS####
> > $cat /proc/asound/cards
> > 0 [Intel ]: HDA-Intel - HDA Intel
> > HDA Intel at 0xf0400000 irq 45
>
> It's not showing up in the cards list above, which seems to indicate
that
the
snd_usb_audio module isn't loaded, or you've forgotten to switch the
keyboard
on. Have a look in lsmod to see if the module is showing there.
If not, load it with.
sudo modprobe snd_usb_audio
Then see if the keyboard shows up in the cards list.
Nigel.
So :
* module snd_usb_audio is already loaded
* after running aj2midid -e, keyboard is still missing from ALSA and
JACK tabs...
It's true that I was surprised that the keyboard did not appear in
/proc/asound/cards but as it does appear in amidi -l, i'm thinking that
alsa is correctly recognizing the keyboard... Could i be wrong?
Thing is I'm not sure if this is an ALSA issue or jack/qjackctl one.
how could i troubleshoot this ?
jy Ok. It does need to be listed as a card in
/proc/asound/cards, just as a
webcam with built in mike (although not a soundcard as such) will have a
card
entry and uses snd_usb_audio. So why isn't it there?
Does it need firmware loading? I know some M-audio keyboards do. My
Evolution
keyboard doesn't, but someone with the same as yours will say.
Nope. The very same keyboard was properly recognized with my previous setup
(ubuntu 10.04). Plus it's USB class compliant.
Have you tried it in a different USB slot if you
have spare ones? Not in
a hub as some USB things don't like hubs.
I use the very same slot that I used on my previous setup.
The only other thing I can think of is that both
the sound card and the
keyboard are trying to grab card0 and the soundcard is winning, thus the
keyboard can't use it. Now I've seen this the other way round due to the
USB
coming up early in the boot process and my keyboard grabbing card0
leaving no
place for the actual soundcard.
This is a very old problem, but may for some reason be happening in your
case,
so I suggest putting some index options in /etc/modprobe.d/options, which
will at least confirm if that is the problem or not. See below.
options snd_hda_intel index=0
options snd_usb-audio index=1
Best to reboot and then see if /proc/asound/cards lists both.
Seems a good idea ! I'll try that. I might not be able to do it before
tomorrow though...
Still it's strange that the keyboard does not appear in /proc/asound/cards
The other thing that strikes me is that on my previous setup after
installing my soundcard drivers (Realtek ACL888), /proc/asound/cards listed
3 different ones : ACL888 anog, ACL888 digital and some kind of HDMI sound
card.
Here wiht my new setup, /proc/asound/cards only lists 1 sound card HDA
intel but aplay -l lists the 3 i was telling you about above...
That doesn't seem right to me... :-/
Thanks a lot
jy
Lets have a go at the USB problem. Your lsusb shows a webcam. I can't find any
details about it on the web, but presume there's a mike on the card which
will need to use snd_usb_audio. I'm guessing there may be a conflict where
both usb audio devices are trying to use snd_usb_audio in the same card slot.
So first thing to try is to remove the midi keyboard from the machine, then
see if anything turns up in /proc/asound/cards, like hopefully the webcam
mike using snd_usb_audio as card1.
If by some miracle it does, you need to add an options line
in /etc/modprobe,d/options to cover both devices, the webcam mike and the
midi keyboard.
Run lsusb -n and you should see the Vid/Pid's for both devices in hex. Add
the following options line, removing the snd_usb_audio options line I gave
you yesterday but leaving the one for the soundcard.
[courtesy of a post on Linux Musicians forum]
Look at the output of “lsusb” and “lsusb -n” for the vendor/product IDs of the
devices, then specify these IDs in the vid and/or pid options, in
hexadecimal. For exampe, if your first USB device has IDs 0123:4567 and the
second 89ab:cdef, use the line
options snd-usb-audio index=2,3 pid=0x4567,0xcdef
You will need to change the 4567 and cdef for whatever the pid's are for the
webcam and midi keyboard.
Right. Go for it! He says, not holding out much hope.
Nigel.
> _______________________________________________
> Linux-audio-user mailing list
> Linux-audio-user(a)lists.linuxaudio.org
> http://lists.linuxaudio.org/listinfo/linux-audio-user
7:09 p.m.
New subject: MIDI keyboard not recognized
ok so here are the result for the various logs but unfortunately, we're not
learning much here. the webcam does not show up when the keyboard is
plugged in or unplugged....
i might have another lead though. I looked into the system logs when
plugging/unplugging the device and here is what showed up
[ 782.208027] usb 7-1: new full-speed USB device number 8 using uhci_hcd
i was more or less expecting usb_snd_audio to be loaded. Any ideas ?
Other logs are below
cheers
jy
keyboard unplugged:
$ cat /proc/asound/cards
0 [Intel ]: HDA-Intel - HDA Intel
HDA Intel at 0xf0400000 irq 45
$ aplay -l
**** Liste des Périphériques Matériels PLAYBACK ****
carte 0: Intel [HDA Intel], périphérique 0: ALC888 Analog [ALC888 Analog]
Sous-périphériques: 1/1
Sous-périphérique #0: subdevice #0
carte 0: Intel [HDA Intel], périphérique 1: ALC888 Digital [ALC888 Digital]
Sous-périphériques: 1/1
Sous-périphérique #0: subdevice #0
carte 0: Intel [HDA Intel], périphérique 3: HDMI 0 [HDMI 0]
Sous-périphériques: 1/1
Sous-périphérique #0: subdevice #0
$ amidi -l
Dir Device Name
cannot determine device number: Inappropriate ioctl for device
keyboard plugged in
$ cat /proc/asound/cards
0 [Intel ]: HDA-Intel - HDA Intel
HDA Intel at 0xf0400000 irq 45
1 [v2 ]: USB-Audio - USB Oxygen 8 v2
M-Audio USB Oxygen 8 v2 at usb-0000:00:1d.1-1, full
speed
$ aplay -l
SAME OUTPUT
$ amidi -l
Dir Device Name
IO hw:1,0,0 USB Oxygen 8 v2 MIDI 1
$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 0bda:0158 Realtek Semiconductor Corp. USB 2.0
multicard reader
Bus 001 Device 004: ID 064e:a103 Suyin Corp. Acer/HP Integrated Webcam
[CN0314]
Bus 004 Device 002: ID 147e:1000 Upek Biometric Touchchip/Touchstrip
Fingerprint Sensor
Bus 007 Device 002: ID 046d:c062 Logitech, Inc. LS1 Laser Mouse, corded
Bus 007 Device 003: ID 0763:0195 Midiman Oxygen 8 v2
2012/9/10 Nigel Henry <cave.dnb2m97pp(a)aliceadsl.fr>
On Monday 10 September 2012 09:50, jy wrote:
replies
setup
the
/proc/asound/cards
2012/9/9 Nigel Henry
<cave.dnb2m97pp(a)aliceadsl.fr>
> On Sunday 09 September 2012 20:54, jy wrote:
> > 2012/9/9 Nigel Henry <cave.dnb2m97pp(a)aliceadsl.fr>
> >
> > > On Sunday 09 September 2012 18:57, jy wrote:
> > > > Hi all,
> > > >
> > > > I've recently installed ubuntustudio 12.04 and after trying it
out,
> > > > i discovered that my M-Audio
Oxygen8 v2 MIDI USB (yes it is class
> > >
> > > compliant)
> > >
> > > > keyboard is not recognised.
> > > > It was recognised out of the box on my previous setup based on
> > > > ubuntu 10.04.
> > > >
> > > > By not recognized, i mean that it doesn't appear in qjackctl
> > > > connexions. thus i cant route the connexions correctly...
> > > > Below are some logs !
> > > >
> > > > How come it doesn't work any more ? How can i correct this ?
> > > >
> > > > Thanks a lot
> > > >
> > > > Cheers,
> > > > jy
> > > >
> > > > ####LOGS####
> > > > $cat /proc/asound/cards
> > > > 0 [Intel ]: HDA-Intel - HDA Intel
> > > > HDA Intel at 0xf0400000 irq 45
> > >
> > > It's not showing up in the cards list above, which seems to
indicate
>
> that
>
> > > the
> > > snd_usb_audio module isn't loaded, or you've forgotten to switch
the
> > > keyboard
> > > on. Have a look in lsmod to see if the module is showing there.
> > >
> > > If not, load it with.
> > > sudo modprobe snd_usb_audio
> > >
> > > Then see if the keyboard shows up in the cards list.
> > >
> > > Nigel.
> >
> > So :
> >
> > * module snd_usb_audio is already loaded
> > * after running aj2midid -e, keyboard is still missing from ALSA and
> > JACK tabs...
> >
> > It's true that I was surprised that the keyboard did not appear in
> > /proc/asound/cards but as it does appear in amidi -l, i'm thinking
that
> > alsa is correctly recognizing the
keyboard... Could i be wrong?
> > Thing is I'm not sure if this is an ALSA issue or jack/qjackctl one.
> >
> > how could i troubleshoot this ?
> >
> > jy
>
> Please send replies to the list and put your replies at the bottom of
the
post,
which makes it easier to follow.
Oups! Sorry i didn't mean to ! I assumed that the list would handle but I made a mistake. My bad !
> Ok. It does need to be listed as a card in /proc/asound/cards, just as
a
> webcam with built in mike (although not a
soundcard as such) will have
a
card
entry and uses snd_usb_audio. So why isn't it there?
Does it need firmware loading? I know some M-audio keyboards do. My
Evolution
keyboard doesn't, but someone with the same as yours will say.
Nope. The very same keyboard was properly recognized with my previous (ubuntu 10.04). Plus it's USB class
compliant.
> Have you tried it in a different USB slot if you have spare ones? Not
in
a hub as
some USB things don't like hubs.
I use the very same slot that I used on my previous setup.
> The only other thing I can think of is that both the sound card and the
> keyboard are trying to grab card0 and the soundcard is winning, thus > keyboard can't use it. Now I've
seen this the other way round due to
the
> USB
> coming up early in the boot process and my keyboard grabbing card0
> leaving no
> place for the actual soundcard.
>
>
> This is a very old problem, but may for some reason be happening in
your
> case,
> so I suggest putting some index options in /etc/modprobe.d/options,
which
will at
least confirm if that is the problem or not. See below.
options snd_hda_intel index=0
options snd_usb-audio index=1
Best to reboot and then see if /proc/asound/cards lists both.
Seems a good idea ! I'll try that. I might not be able to do it before
tomorrow though...
Still it's strange that the keyboard does not appear in
The other thing that strikes me is that on my previous setup after
installing my soundcard drivers (Realtek ACL888), /proc/asound/cards
listed
3 different ones : ACL888 anog, ACL888 digital
and some kind of HDMI
sound
card.
Here wiht my new setup, /proc/asound/cards only lists 1 sound card HDA
intel but aplay -l lists the 3 i was telling you about above...
Yeh, that's another little problem.
That doesn't seem right to me... :-/
Thanks a lot
jy
Lets have a go at the USB problem. Your lsusb shows a webcam. I can't find
any
details about it on the web, but presume there's a mike on the card which
will need to use snd_usb_audio. I'm guessing there may be a conflict where
both usb audio devices are trying to use snd_usb_audio in the same card
slot.
So first thing to try is to remove the midi keyboard from the machine, then
see if anything turns up in /proc/asound/cards, like hopefully the webcam
mike using snd_usb_audio as card1.
If by some miracle it does, you need to add an options line
in /etc/modprobe,d/options to cover both devices, the webcam mike and the
midi keyboard.
Run lsusb -n and you should see the Vid/Pid's for both devices in hex. Add
the following options line, removing the snd_usb_audio options line I gave
you yesterday but leaving the one for the soundcard.
[courtesy of a post on Linux Musicians forum]
Look at the output of “lsusb” and “lsusb -n” for the vendor/product IDs of
the
devices, then specify these IDs in the vid and/or pid options, in
hexadecimal. For exampe, if your first USB device has IDs 0123:4567 and the
second 89ab:cdef, use the line
options snd-usb-audio index=2,3 pid=0x4567,0xcdef
You will need to change the 4567 and cdef for whatever the pid's are for
the
webcam and midi keyboard.
Right. Go for it! He says, not holding out much hope.
Nigel.
>
_______________________________________________
> Linux-audio-user mailing list
> Linux-audio-user(a)lists.linuxaudio.org
> http://lists.linuxaudio.org/listinfo/linux-audio-user
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-user
7:55 p.m.
New subject: MIDI keyboard not recognized
On Mon, Sep 10, 2012 at 1:09 PM, jy <jypllx(a)gmail.com> wrote:
[ ... ]
i don't really see what the problem is anymore ... the keyboard shows up.
10:41 p.m.
New subject: MIDI keyboard not recognized
2012/9/10 Paul Davis <paul(a)linuxaudiosystems.com>
On Mon, Sep 10, 2012 at 1:09 PM, jy <jypllx(a)gmail.com> wrote:
[ ... ]
i don't really see what the problem is anymore ... the keyboard shows up.
Yup but it still doesn't show up in qjackctl, which is really really
strange.
I really don't get why it doesn't since it's properly recognized by ALSA.
Does anyone know from where qjackctl gets its MIDI device list ?
jy
10:55 p.m.
New subject: MIDI keyboard not recognized
I'm tweaking around qjackctl's parameters right now.
I noticed that there is no MIDI driver (bottom left of setup panel)
selected in my setup. Is that usual or should I set it to another value
than none ?
cheers
jy
2012/9/10 jy <jypllx(a)gmail.com>
2012/9/10 Paul Davis <paul(a)linuxaudiosystems.com>
On Mon, Sep 10, 2012 at 1:09 PM, jy <jypllx(a)gmail.com> wrote:
[ ... ]
i don't really see what the problem is anymore ... the keyboard shows up.
Yup but it still doesn't show up in qjackctl, which is really really
strange.
I really don't get why it doesn't since it's properly recognized by ALSA.
Does anyone know from where qjackctl gets its MIDI device list ?
jy
10:57 p.m.
New subject: MIDI keyboard not recognized
On Mon, Sep 10, 2012 at 4:55 PM, jy <jypllx(a)gmail.com> wrote:
I'm tweaking around qjackctl's parameters
right now.
I noticed that there is no MIDI driver (bottom left of setup panel)
selected in my setup. Is that usual or should I set it to another value
than none ?
the MIDI driver selector only exists to start up a "builtin bridge" between
teh world of ALSA MIDI and JACK MIDI. neither of its options are good. you
should use, as mentioned way up-thread:
a2jmidid -e
and yes, some developer should fix this pathetic state of affairs.
11:13 p.m.
New subject: MIDI keyboard not recognized
On Mon, Sep 10, 2012 at 4:40 PM, jy <jypllx(a)gmail.com> wrote:
Yup but it still doesn't show up in qjackctl,
which is really really
strange.
I really don't get why it doesn't since it's properly recognized by ALSA.
Does anyone know from where qjackctl gets its MIDI device list ?
You'll still need to use a2jmidid -e to get Jack to see it.
--
Brett W. McCoy -- http://www.brettwmccoy.com
------------------------------------------------------------------------
"In the rhythm of music a secret is hidden; If I were to divulge it,
it would overturn the world."
-- Jelaleddin Rumi
11 Sep
11 Sep
9:37 a.m.
New subject: MIDI keyboard not recognized
2012/9/10 Brett McCoy <idragosani(a)gmail.com>
On Mon, Sep 10, 2012 at 4:40 PM, jy
<jypllx(a)gmail.com> wrote:
:(
still no appearance of the midi keyboard.
I also tried with all proposed audio cards in qjackctl setup but still no
midi keyboard (even though the keyboard is correctly listed as an interface
in the interface combo box)
I'm starting to feel like this is hopeless (i'm gonna shed a tear) :-)
just to know, how does jack know about the midi devices present. does it
rely on ALSA ?
Would a message found in dmesg like :
[ 782.208027] usb 7-1: new full-speed USB device number 8 using uhci_hcd
when plugging in the keyboard be of any interest in my case ?
cheers and thanks, guys !
jy
Yup but it still doesn't show up in qjackctl,
which is really really
strange.
I really don't get why it doesn't since it's properly recognized by ALSA.
Does anyone know from where qjackctl gets its MIDI device list ?
You'll still need to use a2jmidid -e to get Jack to see it.
i did use a2jmidid -e yesterday night but it didn't solve the problem.... --
Brett W. McCoy -- http://www.brettwmccoy.com
------------------------------------------------------------------------
"In the rhythm of music a secret is hidden; If I were to divulge it,
it would overturn the world."
-- Jelaleddin Rumi
10:57 a.m.
New subject: MIDI keyboard not recognized
Hi,
On Tuesday 11 September 2012, jy wrote:
still no appearance of the midi keyboard.
I also tried with all proposed audio cards in qjackctl setup but still no
midi keyboard (even though the keyboard is correctly listed as an
interface in the interface combo box)
I'm starting to feel like this is hopeless (i'm gonna shed a tear) :-)
just to know, how does jack know about the midi devices present. does it
rely on ALSA ?
Yes. Jack depends on ALSA drivers to work with hardware MIDI devices, just
like it depends on ALSA drivers to work with hardware audio devices, except
for FireWire devices where jack depends on ffado/freebob. Jack does not have
its own hardware drivers.
Would a message found in dmesg like :
[ 782.208027] usb 7-1: new full-speed USB device number 8 using uhci_hcd
when plugging in the keyboard be of any interest in my case ?
Yes, it is a good sign. Answering your previous question:
Does anyone know from where qjackctl gets its MIDI
device list ?
The ALSA tab is filled from the ALSA Sequencer list of ports, which can be
hardware devices or software applications.
The MIDI tab list comes from one of those bridges that provide MIDI support
to jack.
If you should solve the problem at the ALSA level, I guess that you will be
able to solve the problem with jack as well at the same time.
ALSA provides a number of kernel modules. You can list them with this
command:
$ lsmod | grep ^snd
My guess is that some modules are not automatically loaded in your system.
Summing up your previous diagnostics, the ALSA hardware driver (snd-usb-
audio) recognizes your device properly:
$ cat /proc/asound/cards
1 [v2 ]: USB-Audio - USB Oxygen 8 v2
M-Audio USB Oxygen 8 v2 at usb-0000:00:1d.1-1, full
And the ALSA raw MIDI interface (snd-rawmidi) is working properly as well:
$ amidi -l
Dir Device Name
IO hw:1,0,0 USB Oxygen 8 v2 MIDI 1
In your previous messages it is not clear if the ALSA Sequencer interface is
working or not for you. To verify, there are several tests that you can try.
$ cat /proc/asound/seq/drivers
snd-seq-midi,loaded,2
$ cat /proc/asound/seq/clients
Client info
cur clients : 4
peak clients : 5
max clients : 192
Client 0 : "System" [Kernel]
Port 0 : "Timer" (Rwe-)
Port 1 : "Announce" (R-e-)
Client 14 : "Midi Through" [Kernel]
Port 0 : "Midi Through Port-0" (RWe-)
Another way is the ALSA sequencer player (from the ALSA tools collection):
$ aplaymidi -l
Port Client name Port name
14:0 Midi Through Midi Through Port-0
20:0 MidiSport 2x2 MidiSport 2x2 MIDI 1
[...]
Or the ALSA Sequencer event monitor/receiver:
$ aseqdump -l
If some or all the above tests failed, my guess is that the ALSA Sequencer
modules aren't loaded. In that case, you may try this command:
$ sudo modprobe snd-seq-midi
Regards,
Pedro
11:07 a.m.
New subject: MIDI keyboard not recognized
Ok Pedro thanks a lot for the insight !
Very interesting to know how things work from the inside :)
I'll try the various commands tonight and give a report here as soon as
it's done
Thanks again and cheers
jy
2012/9/11 Pedro Lopez-Cabanillas <pedro.lopez.cabanillas(a)gmail.com>
Hi,
On Tuesday 11 September 2012, jy wrote:
still no appearance of the midi keyboard.
I also tried with all proposed audio cards in qjackctl setup but still no
midi keyboard (even though the keyboard is correctly listed as an
interface in the interface combo box)
I'm starting to feel like this is hopeless (i'm gonna shed a tear) :-)
just to know, how does jack know about the midi devices present. does it
rely on ALSA ?
Yes. Jack depends on ALSA drivers to work with hardware MIDI devices, just
like it depends on ALSA drivers to work with hardware audio devices,
except
for FireWire devices where jack depends on ffado/freebob. Jack does not
have
its own hardware drivers.
Would a message found in dmesg like :
[ 782.208027] usb 7-1: new full-speed USB device number 8 using uhci_hcd
when plugging in the keyboard be of any interest in my case ?
Yes, it is a good sign. Answering your previous question:
Does anyone know from where qjackctl gets its
MIDI device list ?
The ALSA tab is filled from the ALSA Sequencer list of ports, which can be
hardware devices or software applications.
The MIDI tab list comes from one of those bridges that provide MIDI support
to jack.
If you should solve the problem at the ALSA level, I guess that you will be
able to solve the problem with jack as well at the same time.
ALSA provides a number of kernel modules. You can list them with this
command:
$ lsmod | grep ^snd
My guess is that some modules are not automatically loaded in your system.
Summing up your previous diagnostics, the ALSA hardware driver (snd-usb-
audio) recognizes your device properly:
$ cat /proc/asound/cards
1 [v2 ]: USB-Audio - USB Oxygen 8 v2
M-Audio USB Oxygen 8 v2 at usb-0000:00:1d.1-1, full
And the ALSA raw MIDI interface (snd-rawmidi) is working properly as well:
$ amidi -l
Dir Device Name
IO hw:1,0,0 USB Oxygen 8 v2 MIDI 1
In your previous messages it is not clear if the ALSA Sequencer interface
is
working or not for you. To verify, there are several tests that you can
try.
$ cat /proc/asound/seq/drivers
snd-seq-midi,loaded,2
$ cat /proc/asound/seq/clients
Client info
cur clients : 4
peak clients : 5
max clients : 192
Client 0 : "System" [Kernel]
Port 0 : "Timer" (Rwe-)
Port 1 : "Announce" (R-e-)
Client 14 : "Midi Through" [Kernel]
Port 0 : "Midi Through Port-0" (RWe-)
Another way is the ALSA sequencer player (from the ALSA tools collection):
$ aplaymidi -l
Port Client name Port name
14:0 Midi Through Midi Through Port-0
20:0 MidiSport 2x2 MidiSport 2x2 MIDI 1
[...]
Or the ALSA Sequencer event monitor/receiver:
$ aseqdump -l
If some or all the above tests failed, my guess is that the ALSA Sequencer
modules aren't loaded. In that case, you may try this command:
$ sudo modprobe snd-seq-midi
Regards,
Pedro
13 Sep
13 Sep
7:39 a.m.
New subject: MIDI keyboard not recognized
Hi all,
So here are the results of the suggestions of Pedro !
2012/9/11 Pedro Lopez-Cabanillas <pedro.lopez.cabanillas(a)gmail.com>
Hi,
On Tuesday 11 September 2012, jy wrote:
Here is lsmod before plugging the keyboard in :
$ lsmod | grep snd
snd_hda_codec_hdmi 30352 1
snd_hda_codec_realtek 95198 1
snd_hda_intel 25788 5
snd_hda_codec 87980 3
snd_hda_codec_hdmi,snd_hda_codec_realtek,snd_hda_intel
snd_hwdep 12910 1 snd_hda_codec
snd_pcm_oss 39968 0
snd_mixer_oss 21707 2 snd_pcm_oss
snd_pcm 69043 4
snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_pcm_oss
snd_seq_dummy 12455 0
snd_seq_oss 32416 0
snd_seq_midi_event 13124 1 snd_seq_oss
snd_seq 51504 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event
snd_timer 22187 2 snd_pcm,snd_seq
snd_seq_device 12980 3 snd_seq_dummy,snd_seq_oss,snd_seq
snd 50814 21
snd_hda_codec_hdmi,snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_seq_dummy,snd_seq_oss,snd_seq,snd_timer,snd_seq_device
soundcore 12926 2 snd
snd_page_alloc 12841 2 snd_hda_intel,snd_pcm
and after :
$ lsmod | grep snd
snd_usb_audio 83446 0
snd_usbmidi_lib 22777 1 snd_usb_audio
snd_rawmidi 22278 1 snd_usbmidi_lib
snd_hda_codec_hdmi 30352 1
snd_hda_codec_realtek 95198 1
snd_hda_intel 25788 5
snd_hda_codec 87980 3
snd_hda_codec_hdmi,snd_hda_codec_realtek,snd_hda_intel
snd_hwdep 12910 2 snd_usb_audio,snd_hda_codec
snd_pcm_oss 39968 0
snd_mixer_oss 21707 2 snd_pcm_oss
snd_pcm 69043 5
snd_usb_audio,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_pcm_oss
snd_seq_dummy 12455 0
snd_seq_oss 32416 0
snd_seq_midi_event 13124 1 snd_seq_oss
snd_seq 51504 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event
snd_timer 22187 2 snd_pcm,snd_seq
snd_seq_device 12980 4
snd_rawmidi,snd_seq_dummy,snd_seq_oss,snd_seq
snd 50814 24
snd_usb_audio,snd_usbmidi_lib,snd_rawmidi,snd_hda_codec_hdmi,snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_seq_dummy,snd_seq_oss,snd_seq,snd_timer,snd_seq_device
soundcore 12926 2 snd
snd_page_alloc 12841 2 snd_hda_intel,snd_pcm
snd_usb_audio loads properly!
still no appearance of the midi keyboard.
I also tried with all proposed audio cards in qjackctl setup but still no
midi keyboard (even though the keyboard is correctly listed as an
interface in the interface combo box)
I'm starting to feel like this is hopeless (i'm gonna shed a tear) :-)
just to know, how does jack know about the midi devices present. does it
rely on ALSA ?
Yes. Jack depends on ALSA drivers to work with hardware MIDI devices, just
like it depends on ALSA drivers to work with hardware audio devices,
except
for FireWire devices where jack depends on ffado/freebob. Jack does not
have
its own hardware drivers.
Would a message found in dmesg like :
[ 782.208027] usb 7-1: new full-speed USB device number 8 using uhci_hcd
when plugging in the keyboard be of any interest in my case ?
Yes, it is a good sign. Answering your previous question:
Does anyone know from where qjackctl gets its
MIDI device list ?
The ALSA tab is filled from the ALSA Sequencer list of ports, which can be
hardware devices or software applications.
The MIDI tab list comes from one of those bridges that provide MIDI support
to jack.
If you should solve the problem at the ALSA level, I guess that you will be
able to solve the problem with jack as well at the same time.
ALSA provides a number of kernel modules. You can list them with this
command:
$ lsmod | grep ^snd
My guess is that some modules are not automatically loaded in your system.
Summing up your previous diagnostics, the ALSA hardware driver (snd-usb-
audio) recognizes your device properly:
$ cat /proc/asound/cards
1 [v2 ]: USB-Audio - USB Oxygen 8 v2
M-Audio USB Oxygen 8 v2 at usb-0000:00:1d.1-1, full
And the ALSA raw MIDI interface (snd-rawmidi) is working properly as well:
$ amidi -l
Dir Device Name
IO hw:1,0,0 USB Oxygen 8 v2 MIDI 1
In your previous messages it is not clear if the ALSA Sequencer interface
is
working or not for you. To verify, there are several tests that you can
try.
$ cat /proc/asound/seq/drivers
snd-seq-midi,loaded,2
here i have :
$ cat /proc/asound/seq/drivers
snd-seq-oss,loaded,0
snd-seq-midi,empty,0
$ cat /proc/asound/seq/clients
Client info
cur clients : 4
peak clients : 5
max clients : 192
Client 0 : "System" [Kernel]
Port 0 : "Timer" (Rwe-)
Port 1 : "Announce" (R-e-)
Client 14 : "Midi Through" [Kernel]
Port 0 : "Midi Through Port-0" (RWe-)
$ cat /proc/asound/seq/clients
Client info
cur clients : 3
peak clients : 3
max clients : 192
Client 0 : "System" [Kernel]
Port 0 : "Timer" (Rwe-)
Port 1 : "Announce" (R-e-)
Connecting To: 15:0
Client 14 : "Midi Through" [Kernel]
Port 0 : "Midi Through Port-0" (RWe-)
Client 15 : "OSS sequencer" [Kernel]
Port 0 : "Receiver" (-we-)
Connected From: 0:1
Another way is the ALSA sequencer player (from the
ALSA tools collection):
$ aplaymidi -l
Port Client name Port name
14:0 Midi Through Midi Through Port-0
20:0 MidiSport 2x2 MidiSport 2x2 MIDI 1
[...]
and
$ aplaymidi -l
Port Client name Port name
14:0 Midi Through Midi Through Port-0
Or the ALSA Sequencer event monitor/receiver:
$ aseqdump -l
$ aseqdump -l
Port Client name Port name
0:0 System Timer
0:1 System Announce
14:0 Midi Through Midi Through Port-0
If some or all the above tests failed, my guess is that the ALSA Sequencer
modules aren't loaded. In that case, you may try this command:
It seems clear that some of the previous ones failed (cat
/proc/asound/seq/drivers
did not show the keyboard) and lsmod | grep
snd-seq-midi gives no answer..
but lsmod | grep midi gives
$ lsmod | grep midi
snd_usbmidi_lib 22777 1 snd_usb_audio
snd_rawmidi 22278 1 snd_usbmidi_lib
snd_seq_midi_event 13124 1 snd_seq_oss
snd_seq 51504 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event
snd_seq_device 12980 4
snd_rawmidi,snd_seq_dummy,snd_seq_oss,snd_seq
snd 50814 24
snd_usb_audio,snd_usbmidi_lib,snd_rawmidi,snd_hda_codec_hdmi,snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_seq_dummy,snd_seq_oss,snd_seq,snd_timer,snd_seq_device
$ sudo modprobe snd-seq-midi
I tried loading this module but got
$ sudo mod
probe snd-seq-midi
[sudo] password for therockers:
FATAL: Module snd_seq_midi not found.
as a return !
Thanks a lot and cheers !!
jy
Regards,
Pedro
9:31 a.m.
New subject: MIDI keyboard not recognized
2012/9/13 Jeremy Jongepier <jeremy(a)autostatic.com>
On 09/13/12 07:38, jy wrote:
0_0, I'm not sure you've read the full thread: it's a fresh ubuntustudio
install.
Hi all,
So here are the results of the suggestions of Pedro !
Looks like you've either done something with OSS or you're missing ALSA stuff.
I noticed.
Do you have any suggestions ?
jy
Best,
Jeremy
______________________________**_________________
Linux-audio-user mailing list
Linux-audio-user@lists.**linuxaudio.org<Linux-audio-user@lists.linuxaudio.org>
http://lists.linuxaudio.org/**listinfo/linux-audio-user<http://lists.lin…
9:41 a.m.
New subject: MIDI keyboard not recognized
On 09/13/12 09:31, jy wrote:
What does
dpkg --list | grep -e alsa -e asound
amixer -v
return?
And how does /etc/modprobe.d/alsa-base.conf look like?
Best,
Jeremy
0_0, I'm not sure you've read the full
thread: it's a fresh ubuntustudio
install.
Oops my bad, sorry. I just noticed there are a lot of OSS related
modules showing up in your lsmod output.
>or you're missing ALSA stuff.
>
I noticed.
Do you have any suggestions ?
jy
7:23 p.m.
New subject: MIDI keyboard not recognized
2012/9/13 Jeremy Jongepier <jeremy(a)autostatic.com>
On 09/13/12 09:31, jy wrote:
What does
dpkg --list | grep -e alsa -e asound
$ dpkg --list | grep -e alsa -e asound
ii alsa-base
1.0.25+dfsg-0ubuntu1 ALSA driver configuration files
ii alsa-tools
1.0.25-1ubuntu1 Console based ALSA utilities for
specific hardware
ii alsa-tools-gui
1.0.25-1ubuntu1 GUI based ALSA utilities for
specific hardware
ii alsa-utils
1.0.25-1ubuntu5 Utilities for configuring and using
ALSA
ii bluez-alsa
4.98-2ubuntu7 Bluetooth ALSA support
ii gstreamer0.10-alsa
0.10.36-1ubuntu0.1 GStreamer plugin for ALSA
ii libasound2
1.0.25-1ubuntu10.1 shared library for ALSA applications
ii libasound2-plugins
1.0.25-1ubuntu1 ALSA library additional plugins
ii libclalsadrv2
2.0.0-3 ALSA driver C++ access library
ii libsox-fmt-alsa
14.3.2-3 SoX alsa format I/O library
0_0, I'm not sure you've read the full
thread: it's a fresh ubuntustudio
install.
Oops my bad, sorry. I just noticed there are a lot of OSS related modules
showing up in your lsmod output.
or
you're missing ALSA stuff.
I noticed.
Do you have any suggestions ?
jy
amixer -v
$ amixer -v
amixer version 1.0.25
return?
And how does /etc/modprobe.d/alsa-base.conf look like?
$ cat /etc/modprobe.d/alsa-base.conf
# autoloader aliases
install sound-slot-0 /sbin/modprobe snd-card-0
install sound-slot-1 /sbin/modprobe snd-card-1
install sound-slot-2 /sbin/modprobe snd-card-2
install sound-slot-3 /sbin/modprobe snd-card-3
install sound-slot-4 /sbin/modprobe snd-card-4
install sound-slot-5 /sbin/modprobe snd-card-5
install sound-slot-6 /sbin/modprobe snd-card-6
install sound-slot-7 /sbin/modprobe snd-card-7
# Cause optional modules to be loaded above generic modules
install snd /sbin/modprobe --ignore-install snd $CMDLINE_OPTS && {
/sbin/modprobe --quiet --use-blacklist snd-ioctl32 ; /sbin/modprobe --quiet
--use-blacklist snd-seq ; }
#
# Workaround at bug #499695 (reverted in Ubuntu see LP #319505)
install snd-pcm /sbin/modprobe --ignore-install snd-pcm $CMDLINE_OPTS && {
/sbin/modprobe --quiet --use-blacklist snd-pcm-oss ; : ; }
install snd-mixer /sbin/modprobe --ignore-install snd-mixer $CMDLINE_OPTS
&& { /sbin/modprobe --quiet --use-blacklist snd-mixer-oss ; : ; }
install snd-seq /sbin/modprobe --ignore-install snd-seq $CMDLINE_OPTS && {
/sbin/modprobe --quiet --use-blacklist snd-seq-midi ; /sbin/modprobe
--quiet --use-blacklist snd-seq-oss ; : ; }
#
install snd-rawmidi /sbin/modprobe --ignore-install snd-rawmidi
$CMDLINE_OPTS && { /sbin/modprobe --quiet --use-blacklist snd-seq-midi ; :
; }
# Cause optional modules to be loaded above sound card driver modules
install snd-emu10k1 /sbin/modprobe --ignore-install snd-emu10k1
$CMDLINE_OPTS && { /sbin/modprobe --quiet --use-blacklist snd-emu10k1-synth
; }
install snd-via82xx /sbin/modprobe --ignore-install snd-via82xx
$CMDLINE_OPTS && { /sbin/modprobe --quiet --use-blacklist snd-seq ; }
# Load saa7134-alsa instead of saa7134 (which gets dragged in by it anyway)
install saa7134 /sbin/modprobe --ignore-install saa7134 $CMDLINE_OPTS && {
/sbin/modprobe --quiet --use-blacklist saa7134-alsa ; : ; }
# Prevent abnormal drivers from grabbing index 0
options bt87x index=-2
options cx88_alsa index=-2
options saa7134-alsa index=-2
options snd-atiixp-modem index=-2
options snd-intel8x0m index=-2
options snd-via82xx-modem index=-2
options snd-usb-audio index=-2
options snd-usb-caiaq index=-2
options snd-usb-ua101 index=-2
options snd-usb-us122l index=-2
options snd-usb-usx2y index=-2
# Ubuntu #62691, enable MPU for snd-cmipci
options snd-cmipci mpu_port=0x330 fm_port=0x388
# Keep snd-pcsp from being loaded as first soundcard
options snd-pcsp index=-2
# Keep snd-usb-audio from beeing loaded as first soundcard
options snd-usb-audio index=-2
options snd-hda-intel model=acer
options snd-usb-audio index=-2 ???
Hum i don't like the -2 index....
What do you think of this ?
jy
Best,
Jeremy
______________________________**_________________
Linux-audio-user mailing list
Linux-audio-user@lists.**linuxaudio.org<Linux-audio-user@lists.linuxaudio.org>
http://lists.linuxaudio.org/**listinfo/linux-audio-user<http://lists.lin…
9:52 p.m.
New subject: MIDI keyboard not recognized
On 09/13/2012 07:23 PM, jy wrote:
options snd-usb-audio index=-2 ???
Hum i don't like the -2 index....
What do you think of this ?
Thanks for the info! Looks all pretty standard to me. And -2 is the
default. So no breakthrough here ;)
Did you try a different USB cable? A different USB port maybe?
Best,
Jeremy
9:55 p.m.
New subject: MIDI keyboard not recognized
On 09/13/2012 09:52 AM, Jeremy Jongepier wrote:
On 09/13/2012 07:23 PM, jy wrote:
I saw that in my alsa conf, too, for items like the on-board sound
drivers. I think there was also a comment in it saying that this was to
prevent the device from taking index 0.
--
David
gnome(a)hawaii.rr.com
authenticity, honesty, community
http://clanjones.org/david/
http://dancing-treefrog.deviantart.com/
options snd-usb-audio index=-2 ???
Hum i don't like the -2 index....
What do you think of this ?
Thanks for the info! Looks all pretty standard to me. And -2 is the
default.
4483
days inactive
4487
days old
linux-audio-user@lists.linuxaudio.org
21 comments
7 participants
participants (7)
-
Brett McCoy -
david -
Jeremy Jongepier -
jy -
Nigel Henry -
Paul Davis -
Pedro Lopez-Cabanillas