Lines Matching full:midi
2 MIDI 2.0 on Linux
8 MIDI 2.0 is an extended protocol for providing higher resolutions and
9 more fine controls over the legacy MIDI 1.0. The fundamental changes
10 introduced for supporting MIDI 2.0 are:
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
17 UMP is a new container format to hold all MIDI protocol 1.0 and MIDI
21 16 MIDI channels.
23 MIDI 2.0 protocol is an extended protocol to achieve the higher
24 resolution and more controls over the old MIDI 1.0 protocol.
26 MIDI-CI is a high-level protocol that can talk with the MIDI device
31 the encoding/decoding of MIDI protocols on UMP, while MIDI-CI is
34 As of this writing, only USB MIDI device supports the UMP and Linux
43 It's allowed to connect freely between MIDI 1.0 and MIDI 2.0 sequencer
50 The following new configs are added for supporting MIDI 2.0:
59 support for the legacy raw MIDI device for UMP Endpoints.
62 Rawmidi Device with USB MIDI 2.0
65 When a device supports MIDI 2.0, the USB-audio driver probes and uses
66 the MIDI 2.0 interface (that is found always at the altset 1) as
67 default instead of the MIDI 1.0 interface (at altset 0). You can
68 switch back to the binding with the old MIDI 1.0 interface by passing
80 When the MIDI 2.0 device is probed, the kernel creates a rawmidi
83 `/dev/snd/midiC*D*` for MIDI 1.0, in order to avoid confusing the
94 Unlike the MIDI 1.0 byte stream, UMP is a 32bit packet, and the size
104 another standard raw MIDI device additionally as `/dev/snd/midiC*D*`.
107 group via each substream in MIDI 1.0 byte stream format. With the
113 from the information inquired via UMP 1.1 Stream messages or USB MIDI
119 partially from Group Terminal Block (GTB) as defined in USB MIDI 2.0
123 file `/proc/asound/card*/midi*`. For example::
126 ProtoZOA MIDI
157 in the case of USB MIDI, it's taken from `iInterface` of the
158 corresponding USB MIDI interface descriptor. If it's not provided,
163 It's copied from `iSerialNumber` of the device for USB MIDI.
169 ALSA Sequencer with USB MIDI 2.0
173 supports the new UMP MIDI 2.0 device, too. Now, each ALSA sequencer
174 client may set its MIDI version (0, 1 or 2) to declare itself being
175 either the legacy, UMP MIDI 1.0 or UMP MIDI 2.0 device, respectively.
177 sequencer event as was. Meanwhile, UMP MIDI 1.0 and 2.0 clients send
178 and receive in the extended event record for UMP. The MIDI version is
198 Client 14 : "Midi Through" [Kernel Legacy]
199 Port 0 : "Midi Through Port-0" (RWe-)
208 Port 0 : "MIDI 2.0" (RWeX) [In/Out]
214 and "UMP MIDI1" for client 20, which is a USB MIDI 2.0 device.
215 A USB MIDI 2.0 client gives always the port 0 as "MIDI 2.0" and the
219 The "MIDI 2.0" port is for a UMP Endpoint, and its difference from
236 When clients are connected between different MIDI versions, the events
238 only between the legacy and the UMP MIDI 1.0/2.0 types, but also
239 between UMP MIDI 1.0 and 2.0 types, too. For example, running
250 When you run `aseqdump` in MIDI 2.0 mode, it'll receive the high
273 MIDI protocol version (`SNDRV_UMP_EP_INFO_PROTO_MIDI1` or
291 * For the device supports UMP v1.1, the UMP MIDI protocol can be
321 the current MIDI version (either 0, 1 or 2) of each client.
366 associated with the sequencer client. The USB MIDI driver provides
384 The latest kernel contains the support for USB MIDI 2.0 gadget
385 function driver, which can be used for prototyping and debugging MIDI
436 The default MIDI protocol can be set either 1 or 2::
459 Now, the MIDI 2.0 gadget device is enabled, and the gadget host
465 1 [Gadget ]: f_midi2 - MIDI 2.0 Gadget
466 MIDI 2.0 Gadget
476 You can play a MIDI file on the gadget side::
480 and this will appear as an input from a MIDI device on the connected
511 For assigning a Function Block for MIDI 1.0 I/O, set up in `is_midi1`
512 attribute. 1 is for MIDI 1.0, and 2 is for MIDI 1.0 with low speed
522 The MIDI 1.0 interface at altset 0 is supported by the gadget driver,
523 too. When MIDI 1.0 interface is selected by the connected host, the
524 UMP I/O on the gadget is translated from/to USB MIDI 1.0 packets
528 MIDI 1.0 ports are set up from the config in each Function Block.
534 The configuration above will enable the Group 1 (the index 0) for MIDI
552 legacy MIDI 1.0 rawmidi devices corresponding to both EP 0 and EP 1.
563 indicates 1 for MIDI 1.0 (altset 0), 2 for MIDI 2.0 (altset 1) and 0