Lines Matching refs:sequencer

37 implemented differently (e.g. as a ALSA sequencer client), too.
40 rawmidi device and the access via ALSA sequencer API.
42 ALSA sequencer API was extended to allow the payload of UMP packets.
43 It's allowed to connect freely between MIDI 1.0 and MIDI 2.0 sequencer
55 the core support for UMP (`CONFIG_SND_UMP`) and the sequencer binding
172 In addition to the rawmidi interfaces, ALSA sequencer interface
173 supports the new UMP MIDI 2.0 device, too.  Now, each ALSA sequencer
177 sequencer event as was.  Meanwhile, UMP MIDI 1.0 and 2.0 clients send
181 A UMP packet can be sent/received in a sequencer event embedded by
188 With `SNDRV_SEQ_EVENT_UMP` flag set, the type field of a UMP sequencer
218 Ext OUT), and those are exposed as sequencer ports from 1 to 3.
226 Note that, although each UMP sequencer client usually creates 16
229 in the proc outputs.  In the example above, the sequencer ports from 4
260 while the data is automatically converted by ALSA sequencer core.
294   UMP EP info and the corresponding sequencer clients as well.
323   sequencer client is also changed from the former 28 bytes to 32
328 * `SNDRV_SEQ_EVENT_UMP` flag bit is added for each sequencer event
329   flags.  When this bit flag is set, the sequencer event is extended
333 * The new sequencer port type bit (`SNDRV_SEQ_PORT_TYPE_MIDI_UMP`)
336 * The sequencer ports have new capability bits to indicate the
340 * The event conversion of ALSA sequencer clients can be suppressed the
353   Each sequencer port is supposed to set this field if it's a port to
366   associated with the sequencer client.  The USB MIDI driver provides
375   device, ALSA sequencer core changes the corresponding sequencer port
377   announcement to the ALSA sequencer system port, similarly like the