diff options
| author | 2023-10-02 18:59:20 +0000 | |
|---|---|---|
| committer | 2023-10-02 18:59:20 +0000 | |
| commit | c79c20337222d701c39f3ff6e39e1a7f7924b71e (patch) | |
| tree | 9dd25401b1db939a57320a7584eeee99b7aa930d | |
| parent | 793049ec6e03b7c6abd1853a070262f0d4ee8640 (diff) | |
| parent | b09f678b9e3f6e24fb151d46548af42e8dc6cc7a (diff) | |
Merge "MIDI: Add callback docs for MIDI 2.0" into main
| -rw-r--r-- | media/java/android/media/midi/package.html | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/media/java/android/media/midi/package.html b/media/java/android/media/midi/package.html index d9e38e20f9ba..ae0c2ab0e811 100644 --- a/media/java/android/media/midi/package.html +++ b/media/java/android/media/midi/package.html @@ -451,6 +451,14 @@ For a MidiDeviceInfo, you can query the defaultProtocol.</p> int defaultProtocol = info.getDefaultProtocol(); </pre> +<p>To register for callbacks when MIDI 2.0 devices are added or removed, use +MidiManager.TRANSPORT_UNIVERSAL_MIDI_PACKETS as the transport.</p> + +<pre class=prettyprint> +midiManager.registerDeviceCallback( + MidiManager.TRANSPORT_UNIVERSAL_MIDI_PACKETS, executor, callback); +</pre> + <h1 id=creating_a_midi_2_0_virtual_device_service>Creating a MIDI 2.0 Virtual Device Service</h1> |