At Tue, 15 Oct 2002 16:40:56 +0200 (CEST), karsten wiese wrote: > > Hi, > > I am in the process of updating the tascam us-428 > patch for alsa-current and need some hints: > formerly the snd-usb-us428 issued > "request_module( "snd-usb-midi");" > to load that module. this doesn't work with > alsa-current anymore as the snd-usb-audio > initialisation, which is triggered, conflicts with the > initialisation of snd-usb-us428. > thus I deleted that "request_module( "snd-usb-midi");" > from snd_usb_us428. > I remember from some Mail on this list, that > snd-usb-midi would be autoloaded if a users process > accesses a mididevice, which has been created by > "snd_seq_device_new( ...SNDRV_SEQ_DEV_ID_USBMIDI)". > this does not happen here now. > what do I miss? > for the tests I use the bristolsynth with > "./startBristol -alsa -audiodev hw:1 -mididev hw:1" > having issued "modprobe snd-usb-midi" before, > everythingg works as expected. otherwise > "Could not open the MIDI interface. > Error opening midi device hw:1, exiting midi thread"
does support bristrol ALSA sequencer? if it accesses only the midi device, then snd-usb-midi module won't be loaded automatically, because the midi device itself is not the sequencer stuff. the auto-load mechanism works only when the sequencer stuff is requested. i think that an easy way is to force to load snd-usb-midi after snd-usb-audio, such as above command in /etc/modules.conf. Takashi ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
