mirror of
https://gitlab.freedesktop.org/pipewire/pipewire.git
synced 2025-10-29 05:40:27 -04:00
doc: update MIDI doc
This commit is contained in:
parent
8e8306cad8
commit
6598938f12
1 changed files with 8 additions and 4 deletions
|
|
@ -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
|
||||
until the sequencer device node is accessible.
|
||||
|
||||
Currently, the session manager does not try to link control messages
|
||||
automatically.
|
||||
|
||||
## JACK
|
||||
|
||||
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.
|
||||
|
||||
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
|
||||
case the raw UMP is passed to the JACK application directly. For output ports,
|
||||
the JACK port was created with an explcit "32 bits raw UMP" format or with
|
||||
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
|
||||
has the "32 bit raw UMP" format, in which case the UMP messages are simply
|
||||
passed on.
|
||||
has the "32 bit raw UMP" formati or the JackPortIsMIDI2 flag, in which case
|
||||
the UMP messages are simply passed on.
|
||||
|
||||
There is a 1 to 1 mapping between the JACK events and control
|
||||
messages so there is no information loss or need for complicated
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue