Lines Matching full:midi

18    9. MIDI function
360 9. MIDI function
368 The function name to use when creating the function directory is "midi".
369 The MIDI function provides these attributes in its function directory:
372 	buflen		MIDI buffer length
373 	id		ID string for the USB MIDI adapter
374 	in_ports	number of MIDI input ports
375 	index		index value for the USB MIDI adapter
376 	out_ports	number of MIDI output ports
380 Testing the MIDI function
392    14:0    Midi Through                     Midi Through Port-0
393    24:0    MIDI Gadget                      MIDI Gadget MIDI 1
418    14:0    Midi Through                     Midi Through Port-0
419    24:0    MIDI Gadget                      MIDI Gadget MIDI 1
427 MIDI files can be played to speakers/headphones with e.g. timidity installed::
431    14:0    Midi Through                     Midi Through Port-0
432    24:0    MIDI Gadget                      MIDI Gadget MIDI 1
440 MIDI ports can be logically connected using the aconnect utility, e.g.::
444 After the gadget's MIDI port is connected to timidity's MIDI port,
1025 attributes for a UMP Endpoint (which is a pair of USB MIDI Endpoints):
1028 	protocol_caps	MIDI protocol capabilities;
1029 			1: MIDI 1.0, 2: MIDI 2.0, or 3: both protocols
1030 	protocol	Default MIDI protocol (either 1 or 2)
1049 	midi1_first_group	The first UMP Group number for MIDI 1.0 (0-15)
1050 	midi1_num_groups	The number of groups for MIDI 1.0 (0-16)
1053 	midi_ci_verison		Supported MIDI-CI version number (8 bit)
1054 	is_midi1		Legacy MIDI 1.0 device (0-2)
1055 				0: MIDI 2.0 device,
1056 				1: MIDI 1.0 without restriction, or
1057 				2: MIDI 1.0 with low speed
1072 For emulating the old MIDI 2.0 device without UMP v1.1 support, pass 0
1092 UMP MIDI client such as "MIDI 2.0 Gadget".
1097 For testing a MIDI input from the gadget to the host (e.g. emulating a
1098 MIDI keyboard), you can send a MIDI stream like the following.
1104   client 20: 'MIDI 2.0 Gadget' [type=kernel,card=1]
1105       0 'MIDI 2.0        '
1106       1 'Group 1 (MIDI 2.0 Gadget I/O)'
1113   client 24: 'MIDI 2.0 Gadget' [type=kernel,card=2]
1114       0 'MIDI 2.0        '
1115       1 'Group 1 (MIDI 2.0 Gadget I/O)'
1128 For testing a MIDI output to the gadget to the host (e.g. emulating a
1129 MIDI synth), it'll be just other way round.
1139 The access to MIDI 1.0 on altset 0 on the host is supported, and it's
1151 where 0 = unused, 1 = MIDI 1.0 (altset 0), 2 = MIDI 2.0 (altset 1).
1152 The example above shows it's running in 2, i.e. MIDI 2.0.