WIP: Avb ptp management

doc/dox/config/pipewire-client.conf.5.md

@@ -80,6 +80,9 @@ stream.properties = {
     #channelmix.fc-cutoff  = 12000.0
     #channelmix.rear-delay = 12.0
     #channelmix.stereo-widen = 0.0
+    #channelmix.center-level = 0.707106781
+    #channelmix.surround-level = 0.707106781
+    #channelmix.lfe-level = 0.5
     #channelmix.hilbert-taps = 0
     #dither.noise = 0
     #dither.method = none # rectangular, triangular, triangular-hf, wannamaker3, shaped5

doc/dox/config/pipewire-props.7.md

@@ -783,6 +783,15 @@ more to the center speaker and leaves the ambient sound in the stereo channels.
 This is only active when up-mix is enabled and a Front Center channel is mixed.
 \endparblock
 
+@PAR@ node-prop  channelmix.center-level = 0.707106781
+The level of the center channel when up/downmixing.
+
+@PAR@ node-prop  channelmix.surround-level = 0.707106781
+The level of the surround channels when up/downmixing.
+
+@PAR@ node-prop  channelmix.lfe-level = 0.5
+The level of the LFE channel when up/downmixing.
+
 @PAR@ node-prop  channelmix.hilbert-taps = 0
 \parblock
 This option will apply a 90 degree phase shift to the rear channels to improve specialization.

doc/dox/config/pipewire-pulse.conf.5.md

@@ -93,6 +93,9 @@ stream.properties = {
     #channelmix.fc-cutoff = 12000.0
     #channelmix.rear-delay = 12.0
     #channelmix.stereo-widen = 0.0
+    #channelmix.center-level = 0.707106781
+    #channelmix.surround-level = 0.707106781
+    #channelmix.lfe-level = 0.5
     #channelmix.hilbert-taps = 0
     #dither.noise = 0
     #dither.method = none # rectangular, triangular, triangular-hf, wannamaker3, shaped5

doc/dox/internals/index.dox

@@ -10,6 +10,7 @@
 - \subpage page_objects_design
 - \subpage page_library
 - \subpage page_dma_buf
+- \subpage page_running
 - \subpage page_scheduling
 - \subpage page_driver
 - \subpage page_latency

doc/dox/internals/latency.dox

@@ -103,7 +103,7 @@ down and upstream.
 # Async nodes
 
 When a node has the node.async property set to true, it will be considered an async
-node and will be scheduled differently, see scheduling.dox.
+node and will be scheduled differently, see \ref page_scheduling .
 
 A link between a port of an async node and another port (async or not) is called an
 async link and will have the link.async=true property.

doc/dox/internals/midi.dox

@@ -62,6 +62,13 @@ As of 1.4, SPA_CONTROL_UMP (Universal Midi Packet) is the prefered format
 for the MIDI 1.0 and 2.0 messages in the \ref spa_pod_sequence. Conversion
 to SPA_CONTROL_Midi is performed for legacy applications.
 
+As of 1.7 the prefered format is Midi1 again because most devices and
+applications are still Midi1 and conversions between Midi1 and UMP are not
+completely transparent in ALSA and PipeWire. UMP in the ALSA sequencer
+and consumers must be enabled explicitly. UMP in producers is supported
+still and will be converted to Midi1 by all consumers that did not explicitly
+enable UMP support.
+
 ## The PipeWire Daemon
 
 Nothing special is implemented for MIDI. Negotiation of formats
@@ -104,13 +111,14 @@ filtering out the \ref SPA_CONTROL_Midi, \ref SPA_CONTROL_OSC and
 \ref SPA_CONTROL_UMP types. On output ports, the JACK event stream is
 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 bit 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 or the JackPortIsMIDI2 flag, in which case
-the UMP messages are simply passed on.
+Normally, all MIDI and UMP input messages are converted to MIDI1 jack
+events unless the JACK port was created with an explcit "32 bit raw UMP"
+format or with the JackPortIsMIDI2 flag, in which case the messages are
+converted to UMP or passed on directly.
+
+For output ports, the JACK events are assumed to be
+MIDI1 unless the port has the "32 bit raw UMP" format or the JackPortIsMIDI2
+flag, in which case the control messages are assumed to be UMP.
 
 There is a 1 to 1 mapping between the JACK events and control
 messages so there is no information loss or need for complicated