[PlanetCCRMA] snd_seq loaded but no midi

[Kenneth]

Fernando Lopez-Lezcano wrote:

>On Wed, 2005-05-25 at 19:41, Kenneth wrote:
>  
>
>>Fernando Lopez-Lezcano wrote:
>>    
>>
>>>On Wed, 2005-05-25 at 17:44, Kenneth wrote:
>>>      
>>>
>>>>Fernando Lopez-Lezcano wrote:
>>>>        
>>>>
>>>>>On Wed, 2005-05-25 at 04:10, Kenneth wrote:
>>>>>          
>>>>>
>>>>>>cat /proc/asound/devices
>>>>>>0: [0- 0]: ctl
>>>>>>17: [0- 1]: digital audio playback
>>>>>>25: [0- 1]: digital audio capture
>>>>>>16: [0- 0]: digital audio playback
>>>>>>24: [0- 0]: digital audio capture
>>>>>>1:       : sequencer
>>>>>>33:       : timer
>>>>>>32: [1- 0]: ctl
>>>>>>48: [1- 0]: digital audio playback
>>>>>>56: [1- 0]: digital audio capture
>>>>>>
>>>>>>	I'm guessing that starting pd with -mididev 2 would point it to the sequencer in the device list, but that didn't work either.
>>>>>>	Also JACK fails to recognize the keyboard as well. Before I would just run pd through JACK and everything was fine.
>>>>>>
>>>>>>            
>>>>>>
>>>>>Ah, pd, of course. Pd (the version at Planet CCRMA, at least) still uses
>>>>>oss for midi i/o. See if you have the OSS midi devices in /dev ("ls -l
>>>>>/dev/midi*")
>>>>>
>>>>>          
>>>>>
>>>>And we have a winner... there are no midi devices in the /dev or 
>>>>/dev/snd directories. So... how do I fix that? I checked my kernel and 
>>>>the oss sequencer API is compiled as a moduled together with alsa.
>>>>        
>>>>
>>>I have not yet transfered from the "planetedge" repository to the normal
>>>repository the packages that have this fix (part of the alsa-driver
>>>pacakge). You can copy these couple of lines:
>>>
>>>=== CUT HERE ===
>>># alsa-driver: add symbolic link too oss midi device in /dev
>>>KERNEL="midi[CD0-9]*", SYMLINK="midi%e"
>>>=== CUT HERE ===
>>>
>>>to a file named "/etc/udev/rules.d/40-ossmidi.rules"
>>>I don't know how to restart udev, I guess a reboot will do :-)
>>>      
>>>
>>ok... that was a little weird. Seems that file was already there with 
>>exactly those two lines in it and nothing else. Is there another way to 
>>get the kernel to recognize this?
>>    
>>
>
>I should pay more attention..... argh....
>The listing of devices above is not listing any raw midi interfaces. It
>has to show something like this:
>
> 40: [1- 0]: raw midi
>
>So... the second card (the edirol?) is not being completely recognized
>by the system, audio is there but midi is not. Isn't the Edirol 25 the
>card that has a couple of different "modes"? I think not all of them are
>fully supported. You should try to use it in the other mode than it is
>now (I think it is either "Advanced" or "Normal", try "Normal")
>
>Sorry I did not notice this earlier.
>-- Fernando
>
Quite alright, you're giving me more help than I could have hoped for :)

But the Edirol UA series has got the "advanced" and "normal" modes. 
However FC3 (the only linux I've been able to try it on) will only 
recognize it correctly when it is set to 'normal', meaning only 16bit 
44.1 kHz resolution and no midi (through the old five pin connecters). 
In advanced mode it is being recognized as a Roland sound device of some 
sort but I wasn't ever able to make it say anything at all, so 
connecting through the edirol is not an option.

Strange thing is though, that raw midi is being loaded as module 
(snd_rawmidi), it just doesn't show in the device listing. I don't thing 
this has anything to do with the edirol, as the keyboard is plugged 
directly into the computer via usb.

Oh, and again. I'm really appreciating you're doing this.

kenneth