|
From: Vladimir S. <ha...@so...> - 2004-06-29 00:25:55
|
Hi Rui, I'm not sure why you couldn't see alsa ports created. I've tried this last night several times and it was working ok. Try this: CREATE MIDI_INPUT_DEVICE Alsa OK[0] SET MIDI_INPUT_DEVICE_PARAMETER 0 ports=1 So AcquirePorts is called when the "ports" parameter is set. I've discussed it with Christian and although not yet documented (spec needs updating) ports are supposed to be created and removed similarly to audio channels via the above SET command. Once port is created, you can use these commands: GET MIDI_INPUT_PORT INFO 0 0 SET MIDI_INPUT_PORT_PARAMETER 0 0 alsa_seq_bindings='64:0' Let me know how it goes. Regards, Vladimir. Rui Nuno Capela wrote: >Hi, > >Another week, another monday and another patch :) > >The attached patch makes some progressions but also some fixes on the >latest MIDI input consolidation stuff as committed by Vladimir. > >Sorry to insist, but this brings back the unconsolidated commands: > > SET CHANNEL MIDI_INPUT_DEVICE <sampler-channel> <midi-device-id> > SET CHANNEL MIDI_INPUT_PORT <sampler-channel> <midi-port> > SET CHANNEL MIDI_INPUT_CHANNEL <sampler-channel> <midi-channel> > >To maintain my beloved compability, the following command has been >re-implemented: > > SET CHANNEL MIDI_INPUT_TYPE <sampler-channel> <midi-driver-type> > >The patch also makes the optional parameter list effective in: > > CREATE MIDI_INPUT_DEVICE <midi-driver-type> [<param>=<value>,...] > >However I could not make it to show up any actual ALSA sequencer port. >Even with this patch applied, current CVS HEAD's MIDI input triggering >it's at fault. At least as far as I could try. > >Strangely enough, I'm missing how MidiInputDevice::AcquirePorts(), and the >MidiInputDevice::CreatePort() executive is ever reached with current code >path. > >Vladimir? > > |