Re: [Alsa-user] USB midi interface named 'USB Device 0x86a'

Am 04.06.19 um 08:54 schrieb Clemens Ladisch via Alsa-user: > Stefan Sauer wrote: >> 'lsusb' shows the device as: >> Bus 006 Device 003: ID 086a:0001 Emagic Soft- und Hardware GmbH Unitor8 >> >> 'amidi -l' shows a human readable name for all midi devices, but the 'Emagic >> Unitor amt 8' (hw:4,0) s

Re: [Alsa-user] USB midi interface named 'USB Device 0x86a'

On 6/4/19 20:22, Stefan Sauer wrote: > Am 04.06.19 um 08:54 schrieb Clemens Ladisch via Alsa-user: >> Stefan Sauer wrote: >>> 'lsusb' shows the device as: >>> Bus 006 Device 003: ID 086a:0001 Emagic Soft- und Hardware GmbH Unitor8 >>> >>> 'amidi -l' shows a human readable name for all midi devices,

Re: [Alsa-user] USB midi interface named 'USB Device 0x86a'

Am 04.06.19 um 08:54 schrieb Clemens Ladisch via Alsa-user: > Stefan Sauer wrote: >> 'lsusb' shows the device as: >> Bus 006 Device 003: ID 086a:0001 Emagic Soft- und Hardware GmbH Unitor8 >> >> 'amidi -l' shows a human readable name for all midi devices, but the 'Emagic >> Unitor amt 8' (hw:4,0) s

Re: [Alsa-user] USB midi interface named 'USB Device 0x86a'

Stefan Sauer wrote: > 'lsusb' shows the device as: > Bus 006 Device 003: ID 086a:0001 Emagic Soft- und Hardware GmbH Unitor8 > > 'amidi -l' shows a human readable name for all midi devices, but the 'Emagic > Unitor amt 8' (hw:4,0) show up with a generic name: > Dir DeviceName > IO hw:4,0,0 US

Re: [Alsa-user] USB MIDI problem with receiving large sysex files

Your advice was perfect ... it is pretty much embarrassing, but yeah, changing to another USB port helped :-) Did try that before, but just had catched the only other USB port of the machine that obviously has problems, too. All other USB ports are working fine - as I know now ... ;-) So, thanks

Re: [Alsa-user] USB MIDI problem with receiving large sysex files

je...@web.de wrote: > One thing I have seen while watching the data received by amidi with > the -d option as well as with the other tools was, that the "data > stream" sometimes seems to stop while the Axe-Fx II is still sending > data. Sometimes the stream continues after or short break, sometime

Re: [Alsa-user] USB MIDI problem with receiving large sysex files

egards, Joachim > Gesendet: Donnerstag, 11. April 2013 um 09:01 Uhr > Von: "Clemens Ladisch" > An: je...@web.de > Cc: alsa-user@lists.sourceforge.net > Betreff: Re: [Alsa-user] USB MIDI problem with receiving large sysex files > > je...@web.de wrote: > > Recently

Re: [Alsa-user] USB MIDI problem with receiving large sysex files

uot; An: je...@web.de Cc: alsa-user@lists.sourceforge.net Betreff: Re: [Alsa-user] USB MIDI problem with receiving large sysex files je...@web.de wrote: > Recently I encountered a problem with receiving large amounts of sysex > data. [...] the bank dumps never reach 830.336 bytes. The number

Re: [Alsa-user] USB MIDI problem with receiving large sysex files

je...@web.de wrote: > Recently I encountered a problem with receiving large amounts of sysex > data. [...] the bank dumps never reach 830.336 bytes. The number of > bytes received from a bank dump seems to be not predictable and varies > strongly each time. In theory, USB MIDI reception works just

Re: [Alsa-user] USB-MIDI, self-compiled alsa-driver

Fabio Rämi wrote: > modprobe: FATAL: Module snd-seq-midi not found. Then it wasn't compiled. It appears alsa-driver does not get the module configuration correct. Try making the change in the kernel source. Regards, Clemens --

Re: [Alsa-user] USB-MIDI, self-compiled alsa-driver

Hello! On 28.11.2012 15:52, Fabio Rämi wrote: > Clemens Ladisch wrote: >> "modprobe snd-seq-midi"? > > modprobe: FATAL: Module snd-seq-midi not found. I don't want to be annoying, but i'm getting quite desperate with this issue. Is there a way i can get snd-seq-midi? I found /usr/lib/modules/3.

Re: [Alsa-user] USB-MIDI, self-compiled alsa-driver

> Clemens Ladisch wrote: > "modprobe snd-seq-midi"? modprobe: FATAL: Module snd-seq-midi not found. cheers Fabio dynaMIX Fabio Rämi Tontechniker fa...@dynamix-tontechnik.ch http://www.dynamix-tontechnik.ch On 28.11.2012 15:47, Clemens Ladisch wrote: > Fabio Rämi wrote: >> If i change the set

Re: [Alsa-user] USB-MIDI, self-compiled alsa-driver

Fabio Rämi wrote: > If i change the settings in QjackCtl to MIDI-driver: "raw", i see the > devices in the connections-tab "JACK-MIDI". But i'm not able to use "seq". "modprobe snd-seq-midi"? Regards, Clemens -- Keep yo

Re: [Alsa-user] USB midi device (UM1SX) not listed by aconnect (but works as rawmidi)

oh, I discovered today [thanks to my friend Sirio!] that the problem was silly the snd-seq-midi was not loaded, so I wasn't seeing the raw midi device as an alsa sequencer device! modprobe snd-seq-midi solved the problem I don't know why snd-seq-midi always autoloaded with alsa in the past, an

Re: [Alsa-user] USB midi device (UM1SX) not listed by aconnect (but works as rawmidi)

[EMAIL PROTECTED] wrote: > hi all, > > I've got a strange problem today. > I attach the Edirol UM1-SX, and it doesn't get recognized as an alsa > sequencer device > > I look in /proc/asound/cards and it's listed: > ... > 2 [UM1]: USB-Audio - UM-1 > EDIROL UM-1 at

Re: [Alsa-user] USB midi

"Clemens Ladisch" <[EMAIL PROTECTED]> writes: > Immanuel Litzroth wrote: >> I am trying to get USB midi to work with a JUNO-G synthesiser. > > If the device has an "Advanced Driver" switch, select "Standard". The device has only one setting for usb midi > Otherwise, add the following entry to the

Re: [Alsa-user] USB midi

Immanuel Litzroth wrote: > I am trying to get USB midi to work with a JUNO-G synthesiser. If the device has an "Advanced Driver" switch, select "Standard". Otherwise, add the following entry to the sound/usb/usbquirks.h file and recompile the snd-usb-audio driver: { USB_DEVICE(0x0582, 0x0

Re: [Alsa-user] USB midi interface under ALSA recommendations

Geoff Beasley wrote: > which one to get ? HTH Clemens --- This SF.Net email is sponsored by: Oracle 10g Get certified on the hottest thing ever to hit the market... Orac

Re: [Alsa-user] USB Midi support in ALSA?

Joe Emenaker wrote: > 1 - Is snd-usb-audio supposed to be driving usb midi interfaces? Yes. > If so, does anyone have any idea why it's failing? Because the usb-midi driver grabs the device first. Remove usb-midi.o, or add usb-midi to the /etc/hotplug/blacklist file. > ALSA ../alsa-kernel/usb

RE: [Alsa-user] usb midi configuration

Brilliant, this worked perfectly. Thanks a lot. On Wed, 19 Feb 2003 08:40:28 +0100 (MET) Clemens Ladisch <[EMAIL PROTECTED]> wrote: carlos ramirez wrote: > Recompiling from the rc7 sources didn't fix it -- > perhaps the cvs sources then? Yes, it has been fixed after rc7. You could get the curren

RE: [Alsa-user] usb midi configuration

carlos ramirez wrote: > Recompiling from the rc7 sources didn't fix it -- > perhaps the cvs sources then? Yes, it has been fixed after rc7. You could get the current CVS version, or apply the following patch: Index: usbmidi.c === RCS

RE: [Alsa-user] usb midi configuration

Recompiling from the rc7 sources didn't fix it -- perhaps the cvs sources then? I wonder if this http://member.nifty.ne.jp/Breeze/softwares/unix/usbmidi-e.html driver is any better. It has module parameters for defining the separate ports, I have been trying to get it running but now am working

RE: [Alsa-user] usb midi configuration

Carlos, This is apparently a bug in Alsa before the end of January. (rc7) You have to update Alsa to fix it, or so I'm told. I tried the 'Use Windows firmware' suggestion but didn't get any change in this problem. Good luck, Mark > -Original Message- > From: [EMAIL PROTECTED] > [mailto