Lines Matching +full:in +full:- +full:functions
12 - Support of Universal MIDI Packet (UMP)
13 - Support of MIDI 2.0 protocol messages
14 - Transparent conversions between UMP and legacy MIDI 1.0 byte stream
15 - MIDI-CI for property and profile configurations
19 aligned, and each message can be put in a single packet. UMP can send
26 MIDI-CI is a high-level protocol that can talk with the MIDI device
27 for the flexible profiles and configurations. It's represented in the
31 the encoding/decoding of MIDI protocols on UMP, while MIDI-CI is
32 supported in user-space over the standard SysEx.
39 The access to UMP devices are provided in two ways: the access via
65 When a device supports MIDI 2.0, the USB-audio driver probes and uses
69 `midi2_enable=0` option to snd-usb-audio driver module, too.
77 unexpected UMP command; in such a case, pass `midi2_ump_probe=0`
78 option to snd-usb-audio driver for skipping the UMP v1.1 inquiries.
83 `/dev/snd/midiC*D*` for MIDI 1.0, in order to avoid confusing the
88 show the incoming UMP packets of the card 0 device 0 in the hex
91 % hexdump -C /dev/snd/umpC0D0
98 The 32-bit words in the UMP packet payload are always in CPU native
106 (0-based) UMP Group. Legacy applications can access to the specified
107 group via each substream in MIDI 1.0 byte stream format. With the
115 Blocks, where UMP Block is an abstraction introduced in the ALSA UMP
117 Block corresponds to Function Block in UMP 1.1 specification. When
119 partially from Group Terminal Block (GTB) as defined in USB MIDI 2.0
122 The information of UMP Endpoints and UMP Blocks are found in the proc
139 Groups: 1-1
142 Block 1 (ProtoZOA Ext IN)
145 Groups: 2-2
149 Note that `Groups` field shown in the proc file above indicates the
150 1-based UMP Group numbers (from-to).
157 in the case of USB MIDI, it's taken from `iInterface` of the
165 The protocol capabilities and the actual protocol bits are defined in
172 In addition to the rawmidi interfaces, ALSA sequencer interface
178 and receive in the extended event record for UMP. The MIDI version is
179 seen in the new `midi_version` field of `snd_seq_client_info`.
181 A UMP packet can be sent/received in a sequencer event embedded by
191 The type of each client can be seen in `/proc/asound/seq/clients`.
199 Port 0 : "Midi Through Port-0" (RWe-)
203 Groups: 1-1
204 UMP Block 1: ProtoZOA Ext IN [Active]
205 Groups: 2-2
207 Groups: 3-3
208 Port 0 : "MIDI 2.0" (RWeX) [In/Out]
209 Port 1 : "ProtoZOA Main" (RWeX) [In/Out]
210 Port 2 : "ProtoZOA Ext IN" (-We-) [Out]
211 Port 3 : "ProtoZOA Ext OUT" (R-e-) [In]
217 In this example, the device has three active groups (Main, Ext IN and
221 the all ports on the device ("catch-all"), while each UMP Group port
229 in the proc outputs. In the example above, the sequencer ports from 4
233 entry (but with more detailed information) is found in the rawmidi
240 `aseqdump` program on the ProtoZOA Main port in the legacy mode will
243 % aseqdump -p 20:1
250 When you run `aseqdump` in MIDI 2.0 mode, it'll receive the high
253 % aseqdump -u 2 -p 20:1
271 The protocols are specified in two field, the protocol capabilities
274 `SNDRV_UMP_EP_INFO_PROTO_MIDI2`) in the upper byte and the jitter
276 `SNDRV_UMP_EP_INFO_PROTO_JRTS_RX`) in the lower byte.
279 the currently assigned blocks are shown in the Endpoint information.
282 `SNDRV_UMP_IOCTL_BLOCK_INFO`. The block ID number (0-based) has to
285 (0-based) and the number of groups, the name string of the block,
296 * The legacy rawmidi device number is found in the new `tied_device`
298 On the other hand, the UMP rawmidi device number is found in
304 0x10 (`SNDRV_RAWMIDI_INFO_STREAM_INACTIVE`) in the `flags` field of
342 bytes, and the event contains the UMP packet in the payload.
345 indicates the port being UMP-capable.
353 For example, the kernel pass-through client (`snd-seq-dummy`) sets
361 which specifies the associated UMP Group Number (1-based).
362 When it's non-zero, the UMP group field in the UMP packet updated
363 upon delivery to the specified group (corrected to be 0-based).
367 * Each client may set the additional event filter for UMP Groups in
368 `group_filter` bitmap. The filter consists of bitmap from 1-based
373 * Two new ioctls are added for UMP-capable clients:
379 user-space client may provide its own data via `*_SET` ioctl.
382 Setting the data for a kernel client shall result in an error.
395 `snd_seq_ev_ump_notify` in the payload, indicating the client number
410 In addition, for using a gadget driver, you need a working UDC driver.
411 In the example below, we use `dummy_hcd` driver (enabled via
429 % mkdir functions/midi2.usb0
446 % echo "ACMESynth" > functions/midi2.usb0/iface_name
447 % echo "ACMESynth" > functions/midi2.usb0/ep.0/ep_name
448 % echo "ABCD12345" > functions/midi2.usb0/ep.0/product_id
449 % echo 0x0123 > functions/midi2.usb0/ep.0/family
450 % echo 0x4567 > functions/midi2.usb0/ep.0/model
451 % echo 0x123456 > functions/midi2.usb0/ep.0/manufacturer
452 % echo 0x12345678 > functions/midi2.usb0/ep.0/sw_revision
456 % echo 2 > functions/midi2.usb0/ep.0/protocol
461 % echo "Monosynth" > functions/midi2.usb0/ep.0/block.0/name
462 % echo 0 > functions/midi2.usb0/ep.0/block.0/first_group
463 % echo 1 > functions/midi2.usb0/ep.0/block.0/num_groups
467 % ln -s functions/midi2.usb0 configs/c.1
471 system. You can find the UDC instances in `/sys/class/udc` and pass
483 1 [Gadget ]: f_midi2 - MIDI 2.0 Gadget
487 the card and device names given in the configfs above::
491 2 [ACMESynth ]: USB-Audio - ACMESynth
492 ACME Enterprises ACMESynth at usb-dummy_hcd.0-1, high speed
496 % aplaymidi -p 20:1 to_host.mid
501 % aseqdump -p 20:0 -u 2
506 Each Function Block may have different direction and UI-hint,
508 Passing `1` is for input-only, `2` for out-only and `3` for
511 % echo 2 > functions/midi2.usb0/ep.0/block.0/direction
512 % echo 2 > functions/midi2.usb0/ep.0/block.0/ui_hint
516 them in the configuration procedure above before linking.
519 % mkdir functions/midi2.usb0/ep.0/block.1
520 % echo "Keyboard" > functions/midi2.usb0/ep.0/block.1/name
521 % echo 1 > functions/midi2.usb0/ep.0/block.1/first_group
522 % echo 1 > functions/midi2.usb0/ep.0/block.1/num_groups
523 % echo 1 > functions/midi2.usb0/ep.0/block.1/direction
524 % echo 1 > functions/midi2.usb0/ep.0/block.1/ui_hint
529 For assigning a Function Block for MIDI 1.0 I/O, set up in `is_midi1`
533 % echo 2 > functions/midi2.usb0/ep.0/block.1/is_midi1
535 For disabling the processing of UMP Stream messages in the gadget
536 driver, pass `0` to `process_ump` attribute in the top-level config::
538 % echo 0 > functions/midi2.usb0/process_ump
544 user-space over UMP rawmidi.
546 MIDI 1.0 ports are set up from the config in each Function Block.
549 % echo 0 > functions/midi2.usb0/ep.0/block.0/midi1_first_group
550 % echo 1 > functions/midi2.usb0/ep.0/block.0/midi1_num_groups
553 1.0 interface. Note that those groups must be in the groups defined
558 `ep.1` (but under the card top-level config) to enable a new Endpoint::
560 % mkdir functions/midi2.usb0/ep.1
565 % mkdir functions/midi2.usb0/ep.1/block.0
566 % echo 4 > functions/midi2.usb0/ep.1/block.0/num_groups
568 Now, you'll have 4 rawmidi devices in total: the first two are UMP
576 % amixer -c1 cget iface=RAWMIDI,name='Operation Mode'
577 ; type=INTEGER,access=r--v----,values=1,min=0,max=2,step=0
580 The value (shown in the second returned line with `: values=`)