mirrors/pipewire
1
0
Fork 0
mirror of https://gitlab.freedesktop.org/pipewire/pipewire.git synced 2025-10-29 05:40:27 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions

doc: update MIDI doc

Browse source
This commit is contained in:
Wim Taymans 2025-03-11 16:31:08 +01:00
parent 8e8306cad8
commit 6598938f12
1 changed files with 8 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

12
doc/dox/internals/midi.dox
View file

@ -92,6 +92,9 @@ The media session will check the permissions on `/dev/snd/seq` before
attempting to create this node. It will also use inotify to wait attempting to create this node. It will also use inotify to wait
until the sequencer device node is accessible. until the sequencer device node is accessible.
Currently, the session manager does not try to link control messages
automatically.
## JACK ## JACK
JACK assumes all `"application/control"` ports are MIDI ports. JACK assumes all `"application/control"` ports are MIDI ports.
@ -102,11 +105,12 @@ filtering out the \ref SPA_CONTROL_Midi, \ref SPA_CONTROL_OSC and
converted to control messages in a similar way. converted to control messages in a similar way.
Normally, all MIDI and UMP messages are converted to MIDI1 jack events unless Normally, all MIDI and UMP messages are converted to MIDI1 jack events unless
the JACK port was created with an explcit "32 bits raw UMP" format, in which the JACK port was created with an explcit "32 bits raw UMP" format or with
case the raw UMP is passed to the JACK application directly. For output ports, the JackPortIsMIDI2 flag, in which case the raw UMP is passed to the JACK
application directly. For output ports,
the JACK events are assumed to be MIDI1 and converted to UMP unless the port the JACK events are assumed to be MIDI1 and converted to UMP unless the port
has the "32 bit raw UMP" format, in which case the UMP messages are simply has the "32 bit raw UMP" formati or the JackPortIsMIDI2 flag, in which case
passed on. the UMP messages are simply passed on.
There is a 1 to 1 mapping between the JACK events and control There is a 1 to 1 mapping between the JACK events and control
messages so there is no information loss or need for complicated messages so there is no information loss or need for complicated