Midi keyboard not working

This is my summary on the issue i'm having with my MOTU Fastlane MIDI interface and 64Studio 2.0. As i stated earlier i would test other OS's to see if the issue is with the USB MIDI interface or 64studio OS. I tried a couple other OS and had success and failures. Dynebolic 2.3 Dhoruba Loaded snd-usb-audio, same deficiency no MIDI access to system from MIDI controller via interface. But system and applications recognizes the devices. JAD 1.0 Loaded snd-usb-audio, same deficiency no MIDI access to system from MIDI controller via interface. But system and applications recognizes the devices. Home Brewed Gentoo 2006.0 2.6.17-rc1 kernel This is the only GNU/Linux system that i tested that the MIDI interface worked on. This is my initial system i built for multi-track audio recording, mixing and mastering, before using Debian Etch/64Studio for MIDI recording on a laptop. The quagmire with this system is that muse is at version 0.6.12-r1 on it which seems to be incompatible with muse 0.8.1a.4 because it doesn't open the files that were already recorded on the laptop. Results: amidi -l Device Name hw:1,0,0 Fastlane MIDI A hw:1,0,1 Fastlane MIDI B cat /dev/dmmidi1 and /dev/midi1 �9J�G�> �@B�@ �?I�? �CR�C �EB�E �CC�C Probable solution: Now that i know the interface does work. It seems that either i would have to compare the kernel configs for both systems and re-compile the 64Studio kernel or use another MIDI interface with it. This MIDI interface has two ports so i would definitely like to get it working on 64Studio. I know for sure it works in windows as well. Once again Big Up to the 64Studio Developers and all FOSS Developers for a great Distro for us Musicians. Any help appreciated. PEACE jawara

I got the Edirol UM-1SX for about R400, That's about $57... It's got only one IO pair, so I would not complain too much about the price of the UM-3EX which has three! Edirol was bought by Roland, so you can bank on a class compliant usb device - That spells "Universal Support"! I basically plugged my device in for the first time, and seconds later it appears in Jack Control, ready for action.

I had trouble with MIDI as well, mine unfortunately came down to a defective sound card... I got a cheap usb MIDI interface and it worked straight out of the box. I had to do the sound card order trick tough, (see USER FAQ 10) to keep the midi interface from becoming HW0 (silly). It is because the USB bus gets probed before the rest, and this caused the midi device to take the place of my default audio device. Cheers,

I'm having a similar issue with 64Studio 2.0. With my set up it seems as though 64studio 2.0 32 bit is not accepting any external MIDI information from my Studiologic SL-61 MIDI Controller via a MOTU Fastlane MIDI interface connected to a USB port. This is my config results jawara@daw:~$ cat /proc/asound/cards 0 [M66 ]: ICE1712 - M Audio Delta 66 M Audio Delta 66 at 0x24c0, irq 18 1 [Fastlane ]: USB-Audio - Fastlane MOTU Fastlane at usb-0000:00:1d.1-2, full speed jawara@daw:~$ lsusb Bus 002 Device 003: ID 07fd:0001 Mark of the Unicorn The System's USB subsystem JACK, and MuSE Sequencer recognizes the MIDI interface and makes it available to be used. I verified that MIDI signal is reaching the MIDI interface, because the lights blink on and off when i press and release keys on the MIDI controller. I also get a constant on light when i set MuSE as the master on my laptop, and set it to generate MTC, and MIDI clock signals. When i try to play softsynths via MuSE. No sound. When i try to play softsynths and view MIDI activity with Rosegarden. No sound, no MIDI activity. When i configure MuSE as a master, and set it also generate MTC and MIDI clock. No signal is coming out of the system, because there is no constant light on on the MIDI interface. So therefore it seems like the issue is occuring between the MIDI interface and 64Studio, which still doesn't make any sense because the system see's the device. Since i'm a keyboardist this is critical for my recording process. I have also tried the solutions suggested in this forum without any success. All that left to do is to buy and try another MIDI interface or install another Music Production OS to get some closure. Is there any verification as to whether this is an issue with my MIDI interface (MOTU Fastlane) or a bug 64studio 2.0. Thanks for a great system, and any help kindly appreciated. Peace jawara

1. Discover what MIDI devices are configured on your system ($ls /dev/*mid*) 2. For each device configured, discover if MIDI commands are being sent to it. Do the following for each device: a) $cat /dev/xxxxxxxxxxxxxxxx (<------ device name here) b) while the cat command is executing, use the MIDI keyboard to send data to the computer (HINT: the pitch wheel sends tons of data, wiggle it around a bit) c) use ctrl C to quit the cat command If random characters appear as a result of the cat command, then the MIDI keyboard is probably connected to this device.

After all I have already tried during the past weeks I believe that could have to do with the alsa setup. I have noted that the kernel config in V 1.0 had no alsa section, apparently alsa caoms from "outside" (this is maybe not worded very professionally). All other distris, including 2.0, might have a slightly different setup. I am simpluy not good ebough in alsa/kernel configuration to fdind out on myself what could go wrong exactly... Hope someone can help........... Michael

May be worth checking that the device hasn't simply changed to a different MIDI device ID. I had some issues where the device popped-up on a different /dev ID.