[alsa-devel] Alsa Support for Korg Pandora Mini, Vox ToneLab ST
Hi,
I am Ubuntu Studio user and I use also ALSA for driving my audio for recording etc... I have tested two devices with ALSA: 1. Vox Tonelab ST - works with ALSA out of the box as USB audio interface with no need of modifications, provides complete functionalities needed for recording and playing audio 2. Korg Pandora Mini - is detected as audio interface, but when selecting it information that no controls are available is displayed, this device can not work as audio interface in fact with Alsa.
Could you please advise what modifications in ALSA should be made to enable Korg Pandora Mini as audio interface with ALSA, is there any patch for this device? If you would need any information on Korg Pandora Mini please let know.
Thanks Pawel Siemienski
On Tue, Apr 19, 2011 at 9:39 AM, Pawel Siemienski pawel.siemienski@gmail.com wrote:
Hi,
I am Ubuntu Studio user and I use also ALSA for driving my audio for recording etc... I have tested two devices with ALSA:
- Vox Tonelab ST - works with ALSA out of the box as USB audio interface
with no need of modifications, provides complete functionalities needed for recording and playing audio 2. Korg Pandora Mini - is detected as audio interface, but when selecting it information that no controls are available is displayed, this device can not work as audio interface in fact with Alsa.
Could you please advise what modifications in ALSA should be made to enable Korg Pandora Mini as audio interface with ALSA, is there any patch for this device? If you would need any information on Korg Pandora Mini please let know.
Can you send a full "lsusb -v" output, please?
Daniel
Hi Pawel,
sorry for the long delay.
On Tue, Apr 19, 2011 at 9:39 AM, Pawel Siemienski pawel.siemienski@gmail.com wrote:
I am Ubuntu Studio user and I use also ALSA for driving my audio for recording etc... I have tested two devices with ALSA:
- Vox Tonelab ST - works with ALSA out of the box as USB audio interface
with no need of modifications, provides complete functionalities needed for recording and playing audio 2. Korg Pandora Mini - is detected as audio interface, but when selecting it information that no controls are available is displayed, this device can not work as audio interface in fact with Alsa.
The "Korg Pandora Mini" is no audio interface, according to both your lsusb dump and the Korg website. The device is described as "Ultra-compact pocket-size multi-effect designed for both guitar and bass "[1] and exposes only a MIDI interface on USB, presumably for controlling internal parameters, dumping the configuration etc. It specifically not an USB audio interface, and hence it can not be used in a way that you wanted to.
HTH, Daniel
Hi,
Thanks for information. Sorry for taking your time. I thought device will be able to work as audio interface because of following interview from NAMM 2011: http://www.youtube.com/watch?v=AHlSrLYslbQ
Cheers Pawel
2011/5/12 Daniel Mack zonque@gmail.com
Hi Pawel,
sorry for the long delay.
On Tue, Apr 19, 2011 at 9:39 AM, Pawel Siemienski pawel.siemienski@gmail.com wrote:
I am Ubuntu Studio user and I use also ALSA for driving my audio for recording etc... I have tested two devices with ALSA:
- Vox Tonelab ST - works with ALSA out of the box as USB audio interface
with no need of modifications, provides complete functionalities needed
for
recording and playing audio 2. Korg Pandora Mini - is detected as audio interface, but when selecting
it
information that no controls are available is displayed, this device can
not
work as audio interface in fact with Alsa.
The "Korg Pandora Mini" is no audio interface, according to both your lsusb dump and the Korg website. The device is described as "Ultra-compact pocket-size multi-effect designed for both guitar and bass "[1] and exposes only a MIDI interface on USB, presumably for controlling internal parameters, dumping the configuration etc. It specifically not an USB audio interface, and hence it can not be used in a way that you wanted to.
HTH, Daniel
On Fri, May 13, 2011 at 11:25 AM, Pawel Siemienski pawel.siemienski@gmail.com wrote:
Hi,
Thanks for information. Sorry for taking your time. I thought device will be able to work as audio interface because of following interview from NAMM 2011: http://www.youtube.com/watch?v=AHlSrLYslbQ
That's very strange, and most probably misleading. Can you achive that with any other OS, like Windows or Mac OS X? Is the device accessible as audio device from there?
Daniel
Daniel Mack <zonque <at> gmail.com> writes:
Hi Pawel,
sorry for the long delay.
On Tue, Apr 19, 2011 at 9:39 AM, Pawel Siemienski <pawel.siemienski <at> gmail.com> wrote:
I am Ubuntu Studio user and I use also ALSA for driving my audio for recording etc... I have tested two devices with ALSA:
- Vox Tonelab ST - works with ALSA out of the box as USB audio interface
with no need of modifications, provides complete functionalities needed for recording and playing audio 2. Korg Pandora Mini - is detected as audio interface, but when selecting it information that no controls are available is displayed, this device can not work as audio interface in fact with Alsa.
The "Korg Pandora Mini" is no audio interface, according to both your lsusb dump and the Korg website. The device is described as "Ultra-compact pocket-size multi-effect designed for both guitar and bass "[1] and exposes only a MIDI interface on USB, presumably for controlling internal parameters, dumping the configuration etc. It specifically not an USB audio interface, and hence it can not be used in a way that you wanted to.
HTH, Daniel
Hello,
I own a Korg Pandora PX5D, which is the one released before the Pandora Mini. It has a USB audio interface that works out of the box with Alsa, which is great! But it's a composite device and also has USB Midi (it contains a drum machine that can be triggered via midi, and I think the windows patch editor uses midi to communicate with the device too), unfortunately it is not recognized by Alsa (hence no midi or patch editor). From what I read on Korg forums, the Windows driver for USB-Midi is the same as for other Korg devices which are supported under Linux, so maybe it can work with Alsa too ? I'd be happy to help by sending logs or other infos.
Fred.
HI everyone
Is this possibly related to the usb midi regression felix and members of this list were discussing a while ago with the fast track ultra which is another usb composite device?
Grant
2011/5/15 Frédéric Jaume frederic.jaume@gmail.com
Daniel Mack <zonque <at> gmail.com> writes:
Hi Pawel,
sorry for the long delay.
On Tue, Apr 19, 2011 at 9:39 AM, Pawel Siemienski <pawel.siemienski <at> gmail.com> wrote:
I am Ubuntu Studio user and I use also ALSA for driving my audio for recording etc... I have tested two devices with ALSA:
- Vox Tonelab ST - works with ALSA out of the box as USB audio
interface
with no need of modifications, provides complete functionalities needed
for
recording and playing audio 2. Korg Pandora Mini - is detected as audio interface, but when
selecting it
information that no controls are available is displayed, this device
can not
work as audio interface in fact with Alsa.
The "Korg Pandora Mini" is no audio interface, according to both your lsusb dump and the Korg website. The device is described as "Ultra-compact pocket-size multi-effect designed for both guitar and bass "[1] and exposes only a MIDI interface on USB, presumably for controlling internal parameters, dumping the configuration etc. It specifically not an USB audio interface, and hence it can not be used in a way that you wanted to.
HTH, Daniel
Hello,
I own a Korg Pandora PX5D, which is the one released before the Pandora Mini. It has a USB audio interface that works out of the box with Alsa, which is great! But it's a composite device and also has USB Midi (it contains a drum machine that can be triggered via midi, and I think the windows patch editor uses midi to communicate with the device too), unfortunately it is not recognized by Alsa (hence no midi or patch editor). From what I read on Korg forums, the Windows driver for USB-Midi is the same as for other Korg devices which are supported under Linux, so maybe it can work with Alsa too ? I'd be happy to help by sending logs or other infos.
Fred.
Alsa-devel mailing list Alsa-devel@alsa-project.org http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
2011/5/14 Grant Diffey gdiffey@gmail.com:
HI everyone
Is this possibly related to the usb midi regression felix and members of this list were discussing a while ago with the fast track ultra which is another usb composite device?
Possibly, yes. A dump generated by "lsusb -v" with this device attached would help.
Thanks, Daniel
On Sat, May 14, 2011 at 7:24 PM, Daniel Mack zonque@gmail.com wrote:
2011/5/14 Grant Diffey gdiffey@gmail.com:
HI everyone
Is this possibly related to the usb midi regression felix and members of this list were discussing a while ago with the fast track ultra which is another usb composite device?
Possibly, yes. A dump generated by "lsusb -v" with this device attached would help.
And just guessing, but does reverting 7b6717e ("ALSA: usb-audio: Assume first control interface is for audio") help such devices?
Daniel
Hi!
Here's the "lsusb -v" for the Korg Pandora PX5D, attached. Hope this helps.
Fred.
2011/5/14 Daniel Mack zonque@gmail.com
On Sat, May 14, 2011 at 7:24 PM, Daniel Mack zonque@gmail.com wrote:
2011/5/14 Grant Diffey gdiffey@gmail.com:
HI everyone
Is this possibly related to the usb midi regression felix and members of this list were discussing a while ago with the fast track ultra which is another usb composite device?
Possibly, yes. A dump generated by "lsusb -v" with this device attached would help.
And just guessing, but does reverting 7b6717e ("ALSA: usb-audio: Assume first control interface is for audio") help such devices?
Daniel
2011/5/14 Frédéric Jaume frederic.jaume@gmail.com:
Hi!
Here's the "lsusb -v" for the Korg Pandora PX5D, attached. Hope this helps.
The MIDI part of the descriptors is clearly marked as vendor specific, so there is nothing the driver can do about this, except for adding a quirk.
Assuming the MIDI interface is class compliant, the following patch should help. Can you give it a try?
Thanks, Daniel
2011/5/15 Daniel Mack zonque@gmail.com:
2011/5/14 Frédéric Jaume frederic.jaume@gmail.com:
Hi!
Here's the "lsusb -v" for the Korg Pandora PX5D, attached. Hope this helps.
The MIDI part of the descriptors is clearly marked as vendor specific, so there is nothing the driver can do about this, except for adding a quirk.
Assuming the MIDI interface is class compliant, the following patch should help. Can you give it a try?
For the Pandora PX5D, we also have to use the USB_DEVICE_VENDOR_SPEC macro, so the class compliant audio interfaces are not ignored by adding the quirk.
Daniel
Hi Daniel,
I've just stumbled across this thread and saw that it relates to the Fast Track Ultra devices. I wanted to give your patch a try but the combination of alsa-driver/alsa-kernel from git won't build at the moment (error: implicit declaration of function 'fw_iso_resource_manage'). I let you know about the patch when this issue is resolved!
Regards,
Felix
Am 16.05.2011 08:56, schrieb Daniel Mack:
2011/5/15 Daniel Mackzonque@gmail.com:
2011/5/14 Frédéric Jaumefrederic.jaume@gmail.com:
Hi!
Here's the "lsusb -v" for the Korg Pandora PX5D, attached. Hope this helps.
The MIDI part of the descriptors is clearly marked as vendor specific, so there is nothing the driver can do about this, except for adding a quirk.
Assuming the MIDI interface is class compliant, the following patch should help. Can you give it a try?
For the Pandora PX5D, we also have to use the USB_DEVICE_VENDOR_SPEC macro, so the class compliant audio interfaces are not ignored by adding the quirk.
Daniel
Alsa-devel mailing list Alsa-devel@alsa-project.org http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
2011/5/16 Daniel Mack zonque@gmail.com
2011/5/15 Daniel Mack zonque@gmail.com:
2011/5/14 Frédéric Jaume frederic.jaume@gmail.com:
Hi!
Here's the "lsusb -v" for the Korg Pandora PX5D, attached. Hope this
helps.
The MIDI part of the descriptors is clearly marked as vendor specific, so there is nothing the driver can do about this, except for adding a quirk.
Assuming the MIDI interface is class compliant, the following patch should help. Can you give it a try?
For the Pandora PX5D, we also have to use the USB_DEVICE_VENDOR_SPEC macro, so the class compliant audio interfaces are not ignored by adding the quirk.
Daniel
A winner.
[ 115.420064] usb 4-1: new high speed USB device using ehci_hcd and address 3 [ 115.553783] usb 4-1: config 1 interface 3 altsetting 0 bulk endpoint 0x7 has invalid maxpacket 8 [ 115.553789] usb 4-1: config 1 interface 3 altsetting 0 bulk endpoint 0x87 has invalid maxpacket 8 [ 115.554896] usb 4-1: New USB device found, idVendor=0763, idProduct=2080 [ 115.554898] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 115.554901] usb 4-1: Product: Fast Track Ultra [ 115.554903] usb 4-1: Manufacturer: M-Audio nevyn@cetacea:~/linux$ amidi -l Dir Device Name IO hw:1,0,0 Fast Track Ultra MIDI 1
Huzzah! Please commit. your 8 character diff ;) oh. and you probably should change the 8R at the same time given it's essentially the same hardware with different analog bits. (8 pre's instead of 4)
diff --git a/sound/usb/quirks-table.h b/sound/usb/quirks-table.h index 196c753..6d7b357 100644 --- a/sound/usb/quirks-table.h +++ b/sound/usb/quirks-table.h @@ -1926,7 +1926,7 @@ YAMAHA_DEVICE(0x7010, "UB99"), } }, { - USB_DEVICE(0x0763, 0x2080), + USB_DEVICE_VENDOR_SPEC(0x0763, 0x2080), .driver_info = (unsigned long) & (const struct snd_usb_audio_quirk) { /* .vendor_name = "M-Audio", */ /* .product_name = "Fast Track Ultra", */ @@ -1993,7 +1993,7 @@ YAMAHA_DEVICE(0x7010, "UB99"), } }, { - USB_DEVICE(0x0763, 0x2081), + USB_DEVICE_VENDOR_SPEC(0x0763, 0x2081), .driver_info = (unsigned long) & (const struct snd_usb_audio_quirk) { /* .vendor_name = "M-Audio", */ /* .product_name = "Fast Track Ultra 8R", */
Grant
On Mon, May 16, 2011 at 5:20 PM, Grant Diffey gdiffey@gmail.com wrote:
A winner.
[ 115.420064] usb 4-1: new high speed USB device using ehci_hcd and address 3 [ 115.553783] usb 4-1: config 1 interface 3 altsetting 0 bulk endpoint 0x7 has invalid maxpacket 8 [ 115.553789] usb 4-1: config 1 interface 3 altsetting 0 bulk endpoint 0x87 has invalid maxpacket 8 [ 115.554896] usb 4-1: New USB device found, idVendor=0763, idProduct=2080 [ 115.554898] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 115.554901] usb 4-1: Product: Fast Track Ultra [ 115.554903] usb 4-1: Manufacturer: M-Audio nevyn@cetacea:~/linux$ amidi -l Dir Device Name IO hw:1,0,0 Fast Track Ultra MIDI 1
Huzzah! Please commit. your 8 character diff ;) oh. and you probably should change the 8R at the same time given it's essentially the same hardware with different analog bits. (8 pre's instead of 4)
Nice, thank for testing :)
Takashi, I'm currently collecting some patches and will send them in one go soonish.
And Frédéric, if you could report that the Pandora works with the patch I sent this morning, it will also be part of this series.
Daniel
Hi everyone!
Daniel, I successfully applied the patch for the Korg Pandora PX5D (USB_DEVICE_VENDOR_SPEC), and got both working USB Audio and USB Midi from the Pandora! Got audio from the Pandora and was able to send midi notes to it and get sound back. It's a winner!
Fred.
2011/5/16 Daniel Mack zonque@gmail.com
On Mon, May 16, 2011 at 5:20 PM, Grant Diffey gdiffey@gmail.com wrote:
A winner.
[ 115.420064] usb 4-1: new high speed USB device using ehci_hcd and
address
3 [ 115.553783] usb 4-1: config 1 interface 3 altsetting 0 bulk endpoint
0x7
has invalid maxpacket 8 [ 115.553789] usb 4-1: config 1 interface 3 altsetting 0 bulk endpoint
0x87
has invalid maxpacket 8 [ 115.554896] usb 4-1: New USB device found, idVendor=0763,
idProduct=2080
[ 115.554898] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 115.554901] usb 4-1: Product: Fast Track Ultra [ 115.554903] usb 4-1: Manufacturer: M-Audio nevyn@cetacea:~/linux$ amidi -l Dir Device Name IO hw:1,0,0 Fast Track Ultra MIDI 1
Huzzah! Please commit. your 8 character diff ;) oh. and you probably
should
change the 8R at the same time given it's essentially the same hardware
with
different analog bits. (8 pre's instead of 4)
Nice, thank for testing :)
Takashi, I'm currently collecting some patches and will send them in one go soonish.
And Frédéric, if you could report that the Pandora works with the patch I sent this morning, it will also be part of this series.
Daniel
On Sun, May 15, 2011 at 4:16 AM, Daniel Mack zonque@gmail.com wrote:
On Sat, May 14, 2011 at 7:24 PM, Daniel Mack zonque@gmail.com wrote:
2011/5/14 Grant Diffey gdiffey@gmail.com:
HI everyone
Is this possibly related to the usb midi regression felix and members of this list were discussing a while ago with the fast track ultra which is another usb composite device?
Possibly, yes. A dump generated by "lsusb -v" with this device attached would help.
And just guessing, but does reverting 7b6717e ("ALSA: usb-audio: Assume first control interface is for audio") help such devices?
Daniel
So I reverted 7b6717e and... Nope. still no midi ports.
Kernel messages are:
[ 131.484053] usb 3-1: new high speed USB device using ehci_hcd and address 3 [ 131.617753] usb 3-1: config 1 interface 3 altsetting 0 bulk endpoint 0x7 has invalid maxpacket 8 [ 131.617760] usb 3-1: config 1 interface 3 altsetting 0 bulk endpoint 0x87 has invalid maxpacket 8 [ 131.618750] usb 3-1: New USB device found, idVendor=0763, idProduct=2080 [ 131.618754] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 131.618756] usb 3-1: Product: Fast Track Ultra [ 131.618758] usb 3-1: Manufacturer: M-Audio [ 132.767312] usbcore: registered new interface driver snd-usb-audio
And amidi -l reports
nevyn@cetacea:~/linux$ amidi -l Dir Device Name
the hack mentioned earlier of setting the quirk STANDARD_MIDI_INTERFACE that clemens suggested does work but I'm not sure it's the "right" answer to the problem.
Grant
On Sun, May 15, 2011 at 7:54 PM, Grant Diffey gdiffey@gmail.com wrote:
So I reverted 7b6717e and... Nope. still no midi ports.
Kernel messages are:
[ 131.484053] usb 3-1: new high speed USB device using ehci_hcd and address 3 [ 131.617753] usb 3-1: config 1 interface 3 altsetting 0 bulk endpoint 0x7 has invalid maxpacket 8 [ 131.617760] usb 3-1: config 1 interface 3 altsetting 0 bulk endpoint 0x87 has invalid maxpacket 8 [ 131.618750] usb 3-1: New USB device found, idVendor=0763, idProduct=2080 [ 131.618754] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 131.618756] usb 3-1: Product: Fast Track Ultra [ 131.618758] usb 3-1: Manufacturer: M-Audio [ 132.767312] usbcore: registered new interface driver snd-usb-audio
And amidi -l reports
nevyn@cetacea:~/linux$ amidi -l Dir Device Name
the hack mentioned earlier of setting the quirk STANDARD_MIDI_INTERFACE that clemens suggested does work but I'm not sure it's the "right" answer to the problem.
For the Fasttrack, this shouldn't be necessary, no. Can you send the full output of "lsusb -v", please? The sniplet you posted in your orignial message only contained the interface.
For the Korg Pandora interface though, a quirk is certainly needed, as the interface is marked as vendor specific (0xff).
Daniel
On Sun, May 15, 2011 at 10:43 PM, Daniel Mack zonque@gmail.com wrote:
On Sun, May 15, 2011 at 7:54 PM, Grant Diffey gdiffey@gmail.com wrote:
So I reverted 7b6717e and... Nope. still no midi ports.
Kernel messages are:
[ 131.484053] usb 3-1: new high speed USB device using ehci_hcd and address 3 [ 131.617753] usb 3-1: config 1 interface 3 altsetting 0 bulk endpoint 0x7 has invalid maxpacket 8 [ 131.617760] usb 3-1: config 1 interface 3 altsetting 0 bulk endpoint 0x87 has invalid maxpacket 8 [ 131.618750] usb 3-1: New USB device found, idVendor=0763, idProduct=2080 [ 131.618754] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 131.618756] usb 3-1: Product: Fast Track Ultra [ 131.618758] usb 3-1: Manufacturer: M-Audio [ 132.767312] usbcore: registered new interface driver snd-usb-audio
And amidi -l reports
nevyn@cetacea:~/linux$ amidi -l
Attached is a patch that adds some debug output. If you could apply that and report what the kernel logs during the probe of the device, that would be appreciated.
Thanks, Daniel
On Mon, May 16, 2011 at 7:30 AM, Daniel Mack zonque@gmail.com wrote:
On Sun, May 15, 2011 at 10:43 PM, Daniel Mack zonque@gmail.com wrote:
On Sun, May 15, 2011 at 7:54 PM, Grant Diffey gdiffey@gmail.com wrote:
So I reverted 7b6717e and... Nope. still no midi ports.
Kernel messages are:
[ 131.484053] usb 3-1: new high speed USB device using ehci_hcd and
address
3 [ 131.617753] usb 3-1: config 1 interface 3 altsetting 0 bulk endpoint
0x7
has invalid maxpacket 8 [ 131.617760] usb 3-1: config 1 interface 3 altsetting 0 bulk endpoint
0x87
has invalid maxpacket 8 [ 131.618750] usb 3-1: New USB device found, idVendor=0763,
idProduct=2080
[ 131.618754] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 131.618756] usb 3-1: Product: Fast Track Ultra [ 131.618758] usb 3-1: Manufacturer: M-Audio [ 132.767312] usbcore: registered new interface driver snd-usb-audio
And amidi -l reports
nevyn@cetacea:~/linux$ amidi -l
Attached is a patch that adds some debug output. If you could apply that and report what the kernel logs during the probe of the device, that would be appreciated.
Nothing is leaping out at me after building with he patch above...
[ 1025.380150] usb 4-1: new high speed USB device using ehci_hcd and address 4 [ 1025.513756] usb 4-1: config 1 interface 3 altsetting 0 bulk endpoint 0x7 has invalid maxpacket 8 [ 1025.513771] usb 4-1: config 1 interface 3 altsetting 0 bulk endpoint 0x87 has invalid maxpacket 8 [ 1025.514863] usb 4-1: New USB device found, idVendor=0763, idProduct=2080 [ 1025.514873] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 1025.514881] usb 4-1: Product: Fast Track Ultra [ 1025.514886] usb 4-1: Manufacturer: M-Audio [ 1025.751285] usbcore: registered new interface driver snd-usb-audio
Grant
On Mon, May 16, 2011 at 4:55 AM, Grant Diffey gdiffey@gmail.com wrote:
On Mon, May 16, 2011 at 7:30 AM, Daniel Mack zonque@gmail.com wrote:
Attached is a patch that adds some debug output. If you could apply that and report what the kernel logs during the probe of the device, that would be appreciated.
Nothing is leaping out at me after building with he patch above...
Ok, so the reason is clear now to me and it has to do with the way the device is matched by the driver. Basically, the only thing the drivers matches on is a standard audio control interface. If that is found, the USB core calls it to handle that specific interface. Once a control header is found, it is iterated and MIDI devices are created when a specific interface associated to the control header is found.
The problem in your case is that the device is matched with a USB_DEVICE() macro now with no further hints in the quirks table, which makes the USB core hand over the whole device to the driver, and not individual interfaces. Because the assumption is that if a driver announces to handle the whole thing, it knows what it's doing.
In the USB audio driver though, we handle that case by defining a fix behaviour, which is that only interfaces listed in the quirk are actually being looked at.
In earlier versions of the driver, the whole quirk for this device was missing, and hence the last, more generic quirk to look for MIDI_STREAMING interfaces was applied (the last one in quirks-table.h). Hence it worked back then but not today.
The solution is most probably rather simple by handling the Fasttrack as composite device that has non-standard and standard interfaces mixed. There is a macro for that which we just need to use.
Can you give the attached patch a change?
HTH, Daniel
Hi Daniel,
Am 16.05.2011 08:48, schrieb Daniel Mack:
The solution is most probably rather simple by handling the Fasttrack as composite device that has non-standard and standard interfaces mixed. There is a macro for that which we just need to use.
Can you give the attached patch a change?
HTH, Daniel
as expected, the patch works for the Fast Track Ultra 8R (0x0763, 0x2081), too.
Thanks,
Felix
On Mon, May 16, 2011 at 6:43 AM, Daniel Mack zonque@gmail.com wrote:
On Sun, May 15, 2011 at 7:54 PM, Grant Diffey gdiffey@gmail.com wrote:
So I reverted 7b6717e and... Nope. still no midi ports.
the hack mentioned earlier of setting the quirk STANDARD_MIDI_INTERFACE
that
clemens suggested does work but I'm not sure it's the "right" answer to
the
problem.
For the Fasttrack, this shouldn't be necessary, no. Can you send the full output of "lsusb -v", please? The sniplet you posted in your orignial message only contained the interface.
Attached is a full lsusb -v of the fast track ultra.
I'm currently building a kernel with the usb-midi logging patch you attached
Grant.
participants (5)
-
Daniel Mack -
Felix Homann -
Frédéric Jaume -
Grant Diffey -
Pawel Siemienski