Skip to content
Snippets Groups Projects
Select Git revision
  • 3aa7d6ce787430ebc41300e2adef54ece8628f81
  • apertis/v2027dev0 default protected
  • pristine-lfs-source
  • apertis/v2026dev2 protected
  • apertis/v2026dev3 protected
  • apertis/v2026pre protected
  • debian/trixie protected
  • pristine-lfs protected
  • upstream/trixie protected
  • proposed-updates/debian/sid/ba7bb66e
  • apertis/v2025 protected
  • apertis/v2025dev1 protected
  • apertis/v2025dev2 protected
  • apertis/v2025dev3 protected
  • apertis/v2025pre protected
  • apertis/v2026dev0 protected
  • apertis/v2026dev1 protected
  • upstream/bookworm protected
  • debian/bookworm-backports protected
  • apertis/v2024 protected
  • apertis/v2024pre protected
  • apertis/0.5.8-2+apertis1
  • debian/0.5.8-2
  • apertis/0.5.8-1+apertis1
  • debian/0.5.8-1
  • upstream/0.5.8
  • debian/0.5.3-1
  • upstream/0.5.3
  • apertis/0.4.17-1_bpo12+1+apertis2
  • apertis/0.4.17-1_bpo12+1+apertis1
  • debian/0.4.17-1_bpo12+1
  • upstream/0.4.17
  • debian/0.4.15-1_bpo12+1
  • upstream/0.4.15
  • apertis/0.4.14-4_bpo12+1+apertis2
  • apertis/0.4.14-4_bpo12+1+apertis1
  • debian/0.4.14-4_bpo12+1
  • upstream/0.4.14
  • apertis/0.4.13-1+apertis1
  • debian/0.4.13-1
  • upstream/0.4.13
41 results

wireplumber

user avatar
George Kiagiadakis authored
- fall back to the default logic if node.target is set but it doesn't exist
- use the default endpoint if it is within the [target-endpoint] matches;
  this way we can use a config file to override just the stream name,
  for instance, while still respecting the default endpoint
- prefer use of the lookup methods instead of manual iterations

previously the default endpoint was not respected because our config
files have a [target-endpoint] table..
5a002888
History
Name Last commit Last update