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
pipewire/meson_options.txt

398 lines
13 KiB
Meson
Raw Normal View History

doc: add docdir option As patched in Gentoo. Fixes #1057
2021-04-15 21:45:53 +03:00
option('docdir',
type : 'string',
description : 'Directory for installing documentation to (defaults to pipewire_datadir/doc/meson.project_name() )')
meson: rename options as per meson's style guide see https://mesonbuild.com/Style-guide.html
2018-05-19 11:44:28 +02:00
option('docs',
meson.build: separate options for installing man pages or docs
2023-11-24 17:48:22 +02:00
description: 'Documentation',
type: 'feature',
value: 'disabled')
option('man',
description: 'Manual pages',
meson: Use `feature` options everywhere it makes sense
2021-03-10 15:36:27 -03:00
type: 'feature',
value: 'disabled')
meson: add examples option Add an option to allow the user to disable examples, this will allow to build pipewire without alsa. Without this option, build with -Dpipewire-alsa=false -Dalsa=false fails on: src/examples/meson.build:47:0: ERROR: Unknown variable "alsa_dep". Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
2020-01-18 13:59:28 +01:00
option('examples',
description: 'Build examples',
meson: Use `feature` options everywhere it makes sense
2021-03-10 15:36:27 -03:00
type: 'feature',
value: 'enabled')
meson: add tests option Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
2020-02-23 00:09:16 +01:00
option('tests',
description: 'Build tests',
meson: Use `feature` options everywhere it makes sense
2021-03-10 15:36:27 -03:00
type: 'feature',
meson_options.txt: replace auto with enabled/disabled where possible For cases where auto has an always known value, explicitly set it for the sake of clarity. This commit only deals with the most trivial uses that do not require rewriting the internal logic and where auto is not behaving in a third way that's distinct from both enabled and disabled.
2021-06-21 14:56:46 +03:00
value: 'enabled',
meson: Use `feature` options everywhere it makes sense
2021-03-10 15:36:27 -03:00
yield : true)
Optionally install examples and tests This makes it easier to test PipeWire in its "as-installed" state, for example in an OS distribution. The .test metadata files in ${datadir}/installed-tests/${package} are a convention taken from GNOME's installed-tests initiative, allowing a generic test-runner like gnome-desktop-testing to discover and run tests in an automatic way. The installation path ${libexecdir}/installed-tests/${package} is also a convention borrowed from GNOME's installed-tests initiative. In addition to the automated tests, I've installed example executables in the same place, for manual testing. They could be separated into a different directory if desired, but they seem like they have more similarities with the automated tests than differences: both are there to test that PipeWire works correctly, and neither should be relied on for production use. Some examples are installed in deeper subdirectories to avoid name clashes. Signed-off-by: Simon McVittie <smcv@debian.org>
2020-06-05 14:06:36 +01:00
option('installed_tests',
description: 'Install manual and automated test executables',
meson: Use `feature` options everywhere it makes sense
2021-03-10 15:36:27 -03:00
type: 'feature',
value: 'disabled')
meson: rename options as per meson's style guide see https://mesonbuild.com/Style-guide.html
2018-05-19 11:44:28 +02:00
option('gstreamer',
make gstreamer elements optional
2017-11-13 20:08:29 +01:00
description: 'Build GStreamer plugins',
meson: Use `feature` options everywhere it makes sense
2021-03-10 15:36:27 -03:00
type: 'feature',
value: 'auto')
gst: add option to disable device provider
2020-10-13 12:40:48 +02:00
option('gstreamer-device-provider',
description: 'Build GStreamer device provider plugin',
meson: Use `feature` options everywhere it makes sense
2021-03-10 15:36:27 -03:00
type: 'feature',
value: 'auto')
meson.build: rework `systemd` related options One issues is that the `systemd-{system,user}-service` feature options do not anything without the `systemd` option. This makes it more complicated to arrive at the desired build configuration since there are 3^3 = 27 possible ways to set each of them, but if `systemd=disabled`, then the other two are just ignored. Secondly, the `systemd` option also influences whether or not libsystemd will be used or not. This is not strictly necessary, since the "systemd" and "libsystemd" pkg-config files might be split, and one might wish to disable any kind of service file generation, but use libsystemd. Solve the first issues by using the `systemd-{system,user}-service` options when looking up the "systemd" dependency for generating service files. This means that the corresponding option is in full control, no secondary options are necessary. This means that the "systemd" dependency is looked up potentially twice, but that should not be a significant issue since meson caches dependecy lookups. And solve the second issue by renaming the now unused `systemd` option to `libsystemd` and using it solely to control whether or not libsystemd will be used. Furthermore, the default value of `systemd-user-service` is set to "auto" to prevent the dependency lookup from failing on non-systemd systemd out of the box. And the journal tests in "test-support" are extended to return "skip" if `sd_journal_open()` returns `ENOSYS`, which is needed because "elogind" ships the systemd pkg-config files and headers.
2025-05-10 17:43:28 +02:00
option('libsystemd',
description: 'Enable code that depends on libsystemd',
meson: Use `feature` options everywhere it makes sense
2021-03-10 15:36:27 -03:00
type: 'feature',
value: 'auto')
spa: use a separate logind dependency separate from systemd non-systemd systems also have logind, in the form of elogind, which works to resolve the v4l2 video source race just as well. permit finding elogind, by using a separate dep object.
2024-09-20 03:12:04 +02:00
option('logind',
description: 'Enable logind integration',
type: 'feature',
value: 'auto')
option('logind-provider',
description: 'Provider for logind integration',
type: 'combo',
choices: ['libelogind', 'libsystemd'],
value: 'libsystemd')
systemd: Add system service and socket Add system service and socket in addition to the user service and socket. The system service is started as pipewire user and group and clients need to be in the pipewire group to be able to connect.
2020-08-17 10:48:55 +02:00
option('systemd-system-service',
description: 'Install systemd system service file',
meson: Use `feature` options everywhere it makes sense
2021-03-10 15:36:27 -03:00
type: 'feature',
meson: Fixed remaining issues from the port to `feature` options
2021-03-11 14:25:48 -03:00
value: 'disabled')
systemd: Add system service and socket Add system service and socket in addition to the user service and socket. The system service is started as pipewire user and group and clients need to be in the pipewire group to be able to connect.
2020-08-17 10:48:55 +02:00
option('systemd-user-service',
meson.build: rework `systemd` related options One issues is that the `systemd-{system,user}-service` feature options do not anything without the `systemd` option. This makes it more complicated to arrive at the desired build configuration since there are 3^3 = 27 possible ways to set each of them, but if `systemd=disabled`, then the other two are just ignored. Secondly, the `systemd` option also influences whether or not libsystemd will be used or not. This is not strictly necessary, since the "systemd" and "libsystemd" pkg-config files might be split, and one might wish to disable any kind of service file generation, but use libsystemd. Solve the first issues by using the `systemd-{system,user}-service` options when looking up the "systemd" dependency for generating service files. This means that the corresponding option is in full control, no secondary options are necessary. This means that the "systemd" dependency is looked up potentially twice, but that should not be a significant issue since meson caches dependecy lookups. And solve the second issue by renaming the now unused `systemd` option to `libsystemd` and using it solely to control whether or not libsystemd will be used. Furthermore, the default value of `systemd-user-service` is set to "auto" to prevent the dependency lookup from failing on non-systemd systemd out of the box. And the journal tests in "test-support" are extended to return "skip" if `sd_journal_open()` returns `ENOSYS`, which is needed because "elogind" ships the systemd pkg-config files and headers.
2025-05-10 17:43:28 +02:00
description: 'Install systemd user service file',
meson: Use `feature` options everywhere it makes sense
2021-03-10 15:36:27 -03:00
type: 'feature',
meson.build: rework `systemd` related options One issues is that the `systemd-{system,user}-service` feature options do not anything without the `systemd` option. This makes it more complicated to arrive at the desired build configuration since there are 3^3 = 27 possible ways to set each of them, but if `systemd=disabled`, then the other two are just ignored. Secondly, the `systemd` option also influences whether or not libsystemd will be used or not. This is not strictly necessary, since the "systemd" and "libsystemd" pkg-config files might be split, and one might wish to disable any kind of service file generation, but use libsystemd. Solve the first issues by using the `systemd-{system,user}-service` options when looking up the "systemd" dependency for generating service files. This means that the corresponding option is in full control, no secondary options are necessary. This means that the "systemd" dependency is looked up potentially twice, but that should not be a significant issue since meson caches dependecy lookups. And solve the second issue by renaming the now unused `systemd` option to `libsystemd` and using it solely to control whether or not libsystemd will be used. Furthermore, the default value of `systemd-user-service` is set to "auto" to prevent the dependency lookup from failing on non-systemd systemd out of the box. And the journal tests in "test-support" are extended to return "skip" if `sd_journal_open()` returns `ENOSYS`, which is needed because "elogind" ships the systemd pkg-config files and headers.
2025-05-10 17:43:28 +02:00
value: 'auto')
module-protocol-native: add module argument 'sockets' Add module argument 'sockets' for creating multiple sockets clients can connect to. Also allow setting socket file permissions.
2023-10-07 12:21:20 +03:00
option('selinux',
description: 'Enable SELinux integration',
type: 'feature',
value: 'auto')
pipewire: add enable/disable to meson for spa plugins
2018-10-09 13:57:59 +05:30
option('pipewire-alsa',
description: 'Enable pipewire-alsa integration',
meson: Use `feature` options everywhere it makes sense
2021-03-10 15:36:27 -03:00
type: 'feature',
value: 'auto')
pipewire: add enable/disable to meson for spa plugins
2018-10-09 13:57:59 +05:30
option('pipewire-jack',
description: 'Enable pipewire-jack integration',
meson: Use `feature` options everywhere it makes sense
2021-03-10 15:36:27 -03:00
type: 'feature',
meson_options.txt: replace auto with enabled/disabled where possible For cases where auto has an always known value, explicitly set it for the sake of clarity. This commit only deals with the most trivial uses that do not require rewriting the internal logic and where auto is not behaving in a third way that's distinct from both enabled and disabled.
2021-06-21 14:56:46 +03:00
value: 'enabled')
pipewire-v4l2: the start of a v4l2 LD_PRELOAD library
2021-10-06 20:24:08 +02:00
option('pipewire-v4l2',
description: 'Enable pipewire-v4l2 integration',
type: 'feature',
value: 'enabled')
Add feature option for installing jack development files
2021-04-18 14:21:43 +02:00
option('jack-devel',
description: 'Install jack development files',
[Meson] Change jack-devel option to be boolean
2021-08-01 17:54:09 +02:00
type: 'boolean',
meson_options: pass proper boolean values to boolean options Passing strings has been deprecated: https://mesonbuild.com/Release-notes-for-1-1-0.html#coercing-values-in-the-option-function-is-deprecated
2024-01-05 03:41:58 +01:00
value: false)
install replacement libraries in modules directory Don't use a special name for the replacement libraries but install them into the modules directory by default. Add an option to install them into another location. This way, we don't need to set up symlinks in development, distros can choose to install them where they want and/or we can use symlinks or LD_LIBRARY path to select the replacement versions.
2020-04-29 11:24:24 +02:00
option('libjack-path',
description: 'Where to install the libjack.so library',
type: 'string')
meson: add a libv4l2-path option to match libjack-path pw-v4l2 uses the gnu ld's ${LIB} features, see meson.build. Make it possible to work around this by specifying an explicit path, just like for pw-jac. Fixes #1751
2021-10-27 15:16:27 +10:00
option('libv4l2-path',
description: 'Where to install the libpw-v4l2.so library',
type: 'string')
pipewire: add enable/disable to meson for spa plugins
2018-10-09 13:57:59 +05:30
option('spa-plugins',
description: 'Enable spa plugins integration',
meson: Use `feature` options everywhere it makes sense
2021-03-10 15:36:27 -03:00
type: 'feature',
meson_options.txt: replace auto with enabled/disabled where possible For cases where auto has an always known value, explicitly set it for the sake of clarity. This commit only deals with the most trivial uses that do not require rewriting the internal logic and where auto is not behaving in a third way that's distinct from both enabled and disabled.
2021-06-21 14:56:46 +03:00
value: 'enabled')
pipewire: add enable/disable to meson for spa plugins
2018-10-09 13:57:59 +05:30
option('alsa',
description: 'Enable alsa spa plugin integration',
meson: Use `feature` options everywhere it makes sense
2021-03-10 15:36:27 -03:00
type: 'feature',
value: 'auto')
pipewire: add enable/disable to meson for spa plugins
2018-10-09 13:57:59 +05:30
option('audiomixer',
description: 'Enable audiomixer spa plugin integration',
meson: Use `feature` options everywhere it makes sense
2021-03-10 15:36:27 -03:00
type: 'feature',
meson_options.txt: replace auto with enabled/disabled where possible For cases where auto has an always known value, explicitly set it for the sake of clarity. This commit only deals with the most trivial uses that do not require rewriting the internal logic and where auto is not behaving in a third way that's distinct from both enabled and disabled.
2021-06-21 14:56:46 +03:00
value: 'enabled')
pipewire: add enable/disable to meson for spa plugins
2018-10-09 13:57:59 +05:30
option('audioconvert',
meson: enable more options by default Update submodules to latest version
2018-10-10 17:16:01 +02:00
description: 'Enable audioconvert spa plugin integration',
meson: Use `feature` options everywhere it makes sense
2021-03-10 15:36:27 -03:00
type: 'feature',
meson_options.txt: replace auto with enabled/disabled where possible For cases where auto has an always known value, explicitly set it for the sake of clarity. This commit only deals with the most trivial uses that do not require rewriting the internal logic and where auto is not behaving in a third way that's distinct from both enabled and disabled.
2021-06-21 14:56:46 +03:00
value: 'enabled')
resampler: Precompute some common filter coefficients While this is quite fast on x86 (order of a few microseconds), the computation can take a few milliseconds on ARM (measured at 1.9ms (32000 -> 48000) and 3.3ms (32000 -> 44100) on a Cortex A53). Let's precompute some common rates so that we can avoid this overhead on each stream (or any other audioconvert) instantiation. The approach taken here is to write a little program to create the resampler instance, and run that on the host at compile-time to generate some common rate conversions.
2024-08-07 12:30:10 -04:00
option('resampler-precomp-tuples',
description: 'Array of "inrate,outrate[,quality]" tuples to precompute resampler coefficients for',
type: 'array',
value: [ '32000,44100', '32000,48000', '48000,44100', '44100,48000' ])
pipewire: add enable/disable to meson for spa plugins
2018-10-09 13:57:59 +05:30
option('bluez5',
description: 'Enable bluez5 spa plugin integration',
meson: Use `feature` options everywhere it makes sense
2021-03-10 15:36:27 -03:00
type: 'feature',
value: 'auto')
bluez5: Add simple HFP AG support to backend-native
2020-12-23 14:41:57 +01:00
option('bluez5-backend-hsp-native',
description: 'Enable HSP in native backend in bluez5 spa plugin',
meson: Use `feature` options everywhere it makes sense
2021-03-10 15:36:27 -03:00
type: 'feature',
meson_options.txt: replace auto with enabled/disabled where possible For cases where auto has an always known value, explicitly set it for the sake of clarity. This commit only deals with the most trivial uses that do not require rewriting the internal logic and where auto is not behaving in a third way that's distinct from both enabled and disabled.
2021-06-21 14:56:46 +03:00
value: 'enabled')
bluez5: Add simple HFP AG support to backend-native
2020-12-23 14:41:57 +01:00
option('bluez5-backend-hfp-native',
description: 'Enable HFP in native backend in bluez5 spa plugin',
meson: Use `feature` options everywhere it makes sense
2021-03-10 15:36:27 -03:00
type: 'feature',
meson_options.txt: replace auto with enabled/disabled where possible For cases where auto has an always known value, explicitly set it for the sake of clarity. This commit only deals with the most trivial uses that do not require rewriting the internal logic and where auto is not behaving in a third way that's distinct from both enabled and disabled.
2021-06-21 14:56:46 +03:00
value: 'enabled')
bluez5: backend-native: Add a ModemManager dependency Some Linux phones doesn't use oFono but ModemManager to control the modem.
2022-09-06 12:13:14 +02:00
option('bluez5-backend-native-mm',
description: 'Enable ModemManager in native backend in bluez5 spa plugin',
type: 'feature',
value: 'disabled')
bluez5: Make native and ofono backends optional
2020-07-22 14:50:38 +02:00
option('bluez5-backend-ofono',
meson_options.txt: replace auto with enabled/disabled where possible For cases where auto has an always known value, explicitly set it for the sake of clarity. This commit only deals with the most trivial uses that do not require rewriting the internal logic and where auto is not behaving in a third way that's distinct from both enabled and disabled.
2021-06-21 14:56:46 +03:00
description: 'Enable oFono HFP backend in bluez5 spa plugin (no dependency on oFono)',
meson: Use `feature` options everywhere it makes sense
2021-03-10 15:36:27 -03:00
type: 'feature',
meson_options.txt: replace auto with enabled/disabled where possible For cases where auto has an always known value, explicitly set it for the sake of clarity. This commit only deals with the most trivial uses that do not require rewriting the internal logic and where auto is not behaving in a third way that's distinct from both enabled and disabled.
2021-06-21 14:56:46 +03:00
value: 'enabled')
bluez5: Create backend skeleton for HSP/HFP support using hsphfpd As hsphfpd is a prototype and its API subject to change, this backend is disable by default. This skeleton connects to hsphfpd daemon and list the managed devices.
2020-07-22 17:40:32 +02:00
option('bluez5-backend-hsphfpd',
meson_options.txt: replace auto with enabled/disabled where possible For cases where auto has an always known value, explicitly set it for the sake of clarity. This commit only deals with the most trivial uses that do not require rewriting the internal logic and where auto is not behaving in a third way that's distinct from both enabled and disabled.
2021-06-21 14:56:46 +03:00
description: 'Enable hsphfpd backend in bluez5 spa plugin (no dependency on hsphfpd)',
meson: Use `feature` options everywhere it makes sense
2021-03-10 15:36:27 -03:00
type: 'feature',
meson_options.txt: replace auto with enabled/disabled where possible For cases where auto has an always known value, explicitly set it for the sake of clarity. This commit only deals with the most trivial uses that do not require rewriting the internal logic and where auto is not behaving in a third way that's distinct from both enabled and disabled.
2021-06-21 14:56:46 +03:00
value: 'enabled')
meson: Add 'feature' options to enable/disable bluetooth codecs Fixes: #606
2021-03-15 00:14:23 +02:00
option('bluez5-codec-aptx',
meson: Change codec options description
2021-03-14 22:54:37 +00:00
description: 'Enable AptX Qualcomm open source codec implementation',
meson: Add 'feature' options to enable/disable bluetooth codecs Fixes: #606
2021-03-15 00:14:23 +02:00
type: 'feature',
value: 'auto')
option('bluez5-codec-ldac',
meson: Change codec options description
2021-03-14 22:54:37 +00:00
description: 'Enable LDAC Sony open source codec implementation',
meson: Add 'feature' options to enable/disable bluetooth codecs Fixes: #606
2021-03-15 00:14:23 +02:00
type: 'feature',
value: 'auto')
bluez5: ldac decoding support Add support for LDAC decoding, if libldac decoder is available.
2022-08-07 17:58:39 +03:00
option('bluez5-codec-ldac-dec',
description: 'Enable LDAC Sony open source codec decoding',
type: 'feature',
value: 'auto')
meson: Add 'feature' options to enable/disable bluetooth codecs Fixes: #606
2021-03-15 00:14:23 +02:00
option('bluez5-codec-aac',
description: 'Enable Fraunhofer FDK AAC open source codec implementation',
type: 'feature',
value: 'auto')
bluez5: add LC3plus A2DP vendor codec Implement codec plugin for the LC3plus codec, supporting the LC3plus encoder/decoder from Fraunhofer.
2022-04-30 21:03:59 +03:00
option('bluez5-codec-lc3plus',
description: 'Enable LC3plus open source codec implementation',
type: 'feature',
value: 'auto')
bluez5: add Opus as a (Pipewire-specific) A2DP vendor codec Support Opus as A2DP vendor codec. The specification for vendor A2DP codec is our Pipewire-specific one, so it is compatible only with devices running Pipewire.
2022-05-21 14:40:26 +03:00
option('bluez5-codec-opus',
description: 'Enable Opus open source codec implementation',
type: 'feature',
value: 'auto')
bluez5: Add LC3 codec support to LE Audio BAP By default this codec is disabled as the BlueZ support for LE Audio is still experimental.
2022-06-16 09:56:52 +02:00
option('bluez5-codec-lc3',
description: 'Enable LC3 open source codec implementation',
type: 'feature',
meson.build: enable LC3 by default Enable LE Audio support by default if liblc3 is present, the Pipewire implementation should be OK. Remove unused HAVE_BLUETOOTH_BAP define, we don't have any #ifdefs for this. The feature is still disabled by default in BlueZ, which also now takes care of necessary hardware feature checks, and should be safe to enable on Pipewire side.
2023-07-24 17:25:02 +03:00
value: 'auto')
bluez5: Add G722 codec for ASHA For documentation on ASHA, see https://source.android.com/docs/core/connect/bluetooth/asha
2024-11-26 16:41:04 +05:30
option('bluez5-codec-g722',
description: 'Enable G722 open source codec implementation',
type: 'feature',
value: 'auto')
bluez5: add PLC for MSBC using spandsp Use spandsp as optional dependency for MSBC codec, for providing PLC.
2025-06-14 18:52:55 +03:00
option('bluez5-plc-spandsp',
description: 'Enable SpanDSP for packet loss concealment',
type: 'feature',
value: 'auto')
control: add control mixer plugin Add a mixer plugin for control messages and plug it in ports with control messages.
2019-10-16 11:13:23 +02:00
option('control',
description: 'Enable control spa plugin integration',
meson: Use `feature` options everywhere it makes sense
2021-03-10 15:36:27 -03:00
type: 'feature',
meson_options.txt: replace auto with enabled/disabled where possible For cases where auto has an always known value, explicitly set it for the sake of clarity. This commit only deals with the most trivial uses that do not require rewriting the internal logic and where auto is not behaving in a third way that's distinct from both enabled and disabled.
2021-06-21 14:56:46 +03:00
value: 'enabled')
pipewire: add enable/disable to meson for spa plugins
2018-10-09 13:57:59 +05:30
option('audiotestsrc',
description: 'Enable audiotestsrc spa plugin integration',
meson: Use `feature` options everywhere it makes sense
2021-03-10 15:36:27 -03:00
type: 'feature',
meson_options.txt: replace auto with enabled/disabled where possible For cases where auto has an always known value, explicitly set it for the sake of clarity. This commit only deals with the most trivial uses that do not require rewriting the internal logic and where auto is not behaving in a third way that's distinct from both enabled and disabled.
2021-06-21 14:56:46 +03:00
value: 'enabled')
pipewire: add enable/disable to meson for spa plugins
2018-10-09 13:57:59 +05:30
option('ffmpeg',
description: 'Enable ffmpeg spa plugin integration',
meson: Use `feature` options everywhere it makes sense
2021-03-10 15:36:27 -03:00
type: 'feature',
value: 'disabled')
jack: add jack source and sink Makes a device with a source and sink that automatically proxies all physical ports from jack. Jack then drives our PipeWire pipeline from its own thread.
2019-08-20 20:35:41 +02:00
option('jack',
description: 'Enable jack spa plugin integration',
meson: Use `feature` options everywhere it makes sense
2021-03-10 15:36:27 -03:00
type: 'feature',
value: 'auto')
pipewire: add enable/disable to meson for spa plugins
2018-10-09 13:57:59 +05:30
option('support',
description: 'Enable support spa plugin integration',
meson: Use `feature` options everywhere it makes sense
2021-03-10 15:36:27 -03:00
type: 'feature',
meson_options.txt: replace auto with enabled/disabled where possible For cases where auto has an always known value, explicitly set it for the sake of clarity. This commit only deals with the most trivial uses that do not require rewriting the internal logic and where auto is not behaving in a third way that's distinct from both enabled and disabled.
2021-06-21 14:56:46 +03:00
value: 'enabled')
evl: add build option
2019-06-18 18:01:14 +02:00
option('evl',
description: 'Enable EVL support spa plugin integration',
meson: Use `feature` options everywhere it makes sense
2021-03-10 15:36:27 -03:00
type: 'feature',
value: 'disabled')
pipewire: add enable/disable to meson for spa plugins
2018-10-09 13:57:59 +05:30
option('test',
description: 'Enable test spa plugin integration',
meson: Use `feature` options everywhere it makes sense
2021-03-10 15:36:27 -03:00
type: 'feature',
value: 'disabled')
pipewire: add enable/disable to meson for spa plugins
2018-10-09 13:57:59 +05:30
option('v4l2',
description: 'Enable v4l2 spa plugin integration',
meson: Use `feature` options everywhere it makes sense
2021-03-10 15:36:27 -03:00
type: 'feature',
value: 'auto')
meson: make it possible to compile without dbus Make an option to disable dbus and all the code that depends on it. Fixes #1685
2021-10-09 15:00:04 +02:00
option('dbus',
description: 'Enable code that depends on dbus',
type: 'feature',
value: 'enabled')
Integrating libcamera
2020-04-20 12:26:50 +05:30
option('libcamera',
description: 'Enable libcamera spa plugin integration',
meson: Fixed remaining issues from the port to `feature` options
2021-03-11 14:25:48 -03:00
type: 'feature',
value: 'auto')
videoconvert: beginnings of video converter
2019-07-25 12:19:41 +02:00
option('videoconvert',
description: 'Enable videoconvert spa plugin integration',
meson: Use `feature` options everywhere it makes sense
2021-03-10 15:36:27 -03:00
type: 'feature',
meson_options.txt: replace auto with enabled/disabled where possible For cases where auto has an always known value, explicitly set it for the sake of clarity. This commit only deals with the most trivial uses that do not require rewriting the internal logic and where auto is not behaving in a third way that's distinct from both enabled and disabled.
2021-06-21 14:56:46 +03:00
value: 'enabled')
pipewire: add enable/disable to meson for spa plugins
2018-10-09 13:57:59 +05:30
option('videotestsrc',
description: 'Enable videotestsrc spa plugin integration',
meson: Use `feature` options everywhere it makes sense
2021-03-10 15:36:27 -03:00
type: 'feature',
meson_options.txt: replace auto with enabled/disabled where possible For cases where auto has an always known value, explicitly set it for the sake of clarity. This commit only deals with the most trivial uses that do not require rewriting the internal logic and where auto is not behaving in a third way that's distinct from both enabled and disabled.
2021-06-21 14:56:46 +03:00
value: 'enabled')
pipewire: add enable/disable to meson for spa plugins
2018-10-09 13:57:59 +05:30
option('volume',
meson_options.txt: Disable the legacy volume SPA The volume plugin was an experiment that's not really used anywhere that we're aware of. As such it makes sense to switch the default to disabled state and skip building something no one probably needs. Signed-off-by: Niklāvs Koļesņikovs <89q1r14hd@relay.firefox.com>
2022-11-28 16:18:33 +02:00
description: 'Build the legacy volume spa plugin',
meson: Use `feature` options everywhere it makes sense
2021-03-10 15:36:27 -03:00
type: 'feature',
meson_options.txt: Disable the legacy volume SPA The volume plugin was an experiment that's not really used anywhere that we're aware of. As such it makes sense to switch the default to disabled state and skip building something no one probably needs. Signed-off-by: Niklāvs Koļesņikovs <89q1r14hd@relay.firefox.com>
2022-11-28 16:18:33 +02:00
value: 'disabled')
vulkan: add vulkan compute source Add a source that runs a compute shader and exports the GPU buffer as a DmaBuf to the clients.
2019-08-19 16:32:22 +02:00
option('vulkan',
description: 'Enable vulkan spa plugin integration',
meson: Use `feature` options everywhere it makes sense
2021-03-10 15:36:27 -03:00
type: 'feature',
meson_options.txt: disable vulkan option since it's not ready for use According to George Kiagiadakis it being set to auto is an accident, because the Vulkan support does not [yet] provide anything useful.
2021-06-25 14:22:47 +03:00
value: 'disabled')
rename pipewire tools Use the pw- prefix for all pipewire tools. This makes the commands shorter but also avoids conflicts with password and patchwork tools (pwcli is taken, pwconv is maybe we someday can make). pipewire-monitor -> pw-mon pipewire-cli -> pw-cli pipewire-dot -> pw-dot pwcat -> pw-cat
2020-01-27 15:42:59 +01:00
option('pw-cat',
description: 'Build pw-cat/pw-play/pw-record',
meson: Use `feature` options everywhere it makes sense
2021-03-10 15:36:27 -03:00
type: 'feature',
value: 'auto')
meson: Rework FFmpeg / tinycompress detection and add pw-cat-ffmpeg option * Decouple FFmpeg integration in pw-cat from the ffmpeg option; if one wants to use Compress-Offload but not the ffmpeg SPA plugin, it is then possible to just pass -Dpw-cat-ffmpeg=enabled to meson. Likewise, this also makes it possible to build the ffmpeg plugin without extending pw-cat. * tinycompress does not need to be detected in the root meson.build, since it is only needed by the alsa plugin.
2022-11-23 16:22:30 +01:00
option('pw-cat-ffmpeg',
description: 'Enable FFmpeg integration in pw-cat/pw-play/pw-record',
type: 'feature',
value: 'disabled')
udev: Make Udev optional In order to further simplify "unprivileged" builds, add "udev" boolean, which make installing Udev rules optional. I.e. without requiring any ugly hacks (mktemp -d), an privileged build capable of running PulseAudio and JACK applications, can be configured trivially: meson --prefix=~/.local build meson configure build -Dsystemd-user-unit-dir=$HOME/.config/systemd/user meson configure build -Dpipewire-alsa=false meson configure build -Dudev=false Signed-off-by: Jarkko Sakkinen <jarkko.sakkinen@iki.fi>
2021-01-09 23:31:47 +02:00
option('udev',
description: 'Enable Udev integration',
meson: Use `feature` options everywhere it makes sense
2021-03-10 15:36:27 -03:00
type: 'feature',
value: 'auto')
add udev rules so we don't rely on pulseaudio
2020-07-28 13:11:17 +02:00
option('udevrulesdir',
type : 'string',
description : 'Directory for udev rules (defaults to /lib/udev/rules.d)')
systemd: Add systemd-system-unit-dir override
2022-01-06 12:17:10 +00:00
option('systemd-system-unit-dir',
type : 'string',
description : 'Directory for system systemd units (defaults to /usr/lib/systemd/system)')
systemd: Add systemd-user-unit-dir override Add a new build option 'system-user-unit=dir', which can be used to override the pkg-config default value. By doing this, it becomes more practical to make a local unprivileged build of the latest PipeWire: $ meson --prefix=~/.local build $ meson configure build -Dpipewire-alsa=false $ meson configure build -Dsystemd-user-unit-dir=~/.config/systemd/user $ meson configure build -Dudevrulesdir="`mktemp -d`" $ ninja -C build install For a local build enabling ALSA plugins is not plausible. JACK needs a simple addition to the ~/.profile: export LD_LIBRARY_PATH=$HOME/.local/lib/x86_64-linux-gnu/pipewire-0.3/jack Finally, the genuine PulseAudio must be masked and local services enabled: systemctl --user enable pipewire.socket systemctl --user enable pipewire-pulse.socket systemctl --user mask pulseaudio.service A sanity check [*] shows that nothing has leaked out of the home directory (even though at least on my Debian 10 system PolKit still asks for authorization during the meson build). Not perfect, but lowers a barrier to run the development version a lot, as that does not anymore to trash your system. [*] find / -name "*pipewire*" \! -path "/home/*" \! -path "/var/lib/flatpak/*" 2> /dev/null Signed-off-by: Jarkko Sakkinen <jarkko@suppilovahvero.lan>
2021-01-09 11:38:45 +02:00
option('systemd-user-unit-dir',
type : 'string',
description : 'Directory for user systemd units (defaults to /usr/lib/systemd/user)')
meson: Make SDL2 and libsndfile dependencies configurable This is important for cross-platform build frameworks such as Yocto where the build configurations must be deterministic. In this case, if some other build dependency pulled in SDL2, then the meson.build logic would suddenly enable extra features that would not have been built otherwise. By allowing for explicitely enabling/disabling SDL2 and sndfile depending bits, this problem is fixed.
2021-02-15 11:59:10 +01:00
option('sdl2',
description: 'Enable code that depends on SDL 2',
type: 'feature',
value: 'auto')
option('sndfile',
description: 'Enable code that depends on libsndfile',
type: 'feature',
value: 'auto')
filter-chain: add spatializer SOFA is a file format used for storing and accessing spatial audio data, namely head-related transfer functions. These can be used to create binaural spatial sound using head- or earphones. This commit introduces libmysofa as an optional dependency for loading SOFA files and creates a spatializer plugin for the filter-chain ci: install libmysofa-devel for full build ci: bump FDO_DISTRIBUTION_TAG
2023-01-15 08:01:37 +03:00
option('libmysofa',
description: 'Enable code that depends on libmysofa',
type: 'feature',
value: 'auto')
module-pulse-tunner: add module to tunnel to PulseAudio Add a module that can make a source or sink that tunnels audio to or from a (remote) PulseAudio server.
2021-05-12 15:55:15 +02:00
option('libpulse',
description: 'Enable code that depends on libpulse',
type: 'feature',
value: 'auto')
module-protocol-pulse: Add module-roc-sink
2021-06-23 17:08:39 +05:30
option('roc',
description: 'Enable code that depends on roc toolkit',
type: 'feature',
value: 'auto')
zeroconf: add avahi zerconf discover module Discovers remote sinks and sources and load the tunnel module to make a local sink and source for them.
2021-05-13 18:05:26 +02:00
option('avahi',
description: 'Enable code that depends on avahi',
type: 'feature',
value: 'auto')
module-echo-cancel: Wire up the webrtc echo canceller Mostly uses the existing infrastructure, but the webrtc canceller has a fixed blocksize, so we: 1. Use the canceller blocksize if configured 2. Accumulate output data in a ringbuffer 3. Push out the data in the required chunk size
2021-05-28 11:28:03 -04:00
option('echo-cancel-webrtc',
description : 'Enable WebRTC-based echo canceller',
type : 'feature',
value : 'auto')
bluez5: backend-native: use quirks + usb adapter caps for checking msbc Use the quirks database to check whether to enable MSBC codec for each device. If quirks don't allow ALT1 mode for an USB adapter, check whether the adapter has an usable ALT6 mode and disable MSBC if not.
2021-06-13 21:52:41 +03:00
option('libusb',
description: 'Enable code that depends on libusb',
type: 'feature',
value: 'auto')
meson: changes meson switches for controlling session manager Some distributions set --auto_features=enabled which messes with the internal logic of the build system when features are used for other purposes than pure dependency control. The only solution is to either avoid the value auto or change the type of the option to non-feature. This commit does the later by replacing -Dmedia-session, -Dwireplumber and -Dsession-manager with the new -Dsession-managers array and -Ddefault-session-manager combo options. Fixes #1333 Fixes #1336
2021-06-24 16:54:36 +03:00
option('session-managers',
meson: Allow session-managers option to be an absolute path If it's not an absolute_path, then set the build_ms and build_wp as normal, otherwise use the value as passed in.
2021-10-23 10:51:16 +01:00
description : 'Session managers to build (can be [] for none or an absolute path)',
meson: changes meson switches for controlling session manager Some distributions set --auto_features=enabled which messes with the internal logic of the build system when features are used for other purposes than pure dependency control. The only solution is to either avoid the value auto or change the type of the option to non-feature. This commit does the later by replacing -Dmedia-session, -Dwireplumber and -Dsession-manager with the new -Dsession-managers array and -Ddefault-session-manager combo options. Fixes #1333 Fixes #1336
2021-06-24 16:54:36 +03:00
type : 'array',
meson_options: change default session manager to wireplumber
2022-10-03 09:10:35 +03:00
value : ['wireplumber'])
meson: add -Draop switch for OpenSSL dep control Even though OpenSSL is very common, automagic dependencies are still not great, so let's have a raop switch to control that.
2021-11-12 21:16:52 +02:00
option('raop',
description: 'Enable module for Remote Audio Output Protocol',
type: 'feature',
value: 'auto')
filter-chain: add support for lv2 plugins Support lv2 plugins and their control values.
2021-12-10 17:44:28 +01:00
option('lv2',
description: 'Enable loading of LV2 plugins',
type: 'feature',
value: 'auto')
modules: add x11-bell module It listens for X11 bell events and plays a sample with libcanberra. Fixes #1668
2022-01-21 16:27:44 +01:00
option('x11',
description: 'Enable code that depends on X11',
type: 'feature',
value: 'auto')
pipewire: module-x11-bell: mark connection as terminatable Since XFixes version 6[1] it is possible to mark an X connection as terminatable. The X server will gracefully terminate after a timeout if only terminatable connections remain. [1]: https://gitlab.freedesktop.org/xorg/lib/libxfixes/-/merge_requests/1
2022-02-17 20:16:22 +01:00
option('x11-xfixes',
description: 'Enable code that depends on XFixes',
type: 'feature',
value: 'auto')
modules: add x11-bell module It listens for X11 bell events and plays a sample with libcanberra. Fixes #1668
2022-01-21 16:27:44 +01:00
option('libcanberra',
description: 'Enable code that depends on libcanberra',
type: 'feature',
value: 'auto')
meson: Add option to enable/disable legacy RTKit module The RTKit module is being replaced by the RT module. Currently, it is always built if D-Bus is present. For packagers, it can be beneficial to be able to disable the legacy module. Add a Meson option to allow for exactly that. Make it enabled by default to not change default behavior.
2022-03-30 19:44:38 +02:00
option('legacy-rtkit',
description: 'Build legacy rtkit module',
type: 'boolean',
meson_options: pass proper boolean values to boolean options Passing strings has been deprecated: https://mesonbuild.com/Release-notes-for-1-1-0.html#coercing-values-in-the-option-function-is-deprecated
2024-01-05 03:41:58 +01:00
value: true)
start of AVB support
2022-03-07 20:24:46 +01:00
option('avb',
description: 'Enable AVB code',
type: 'feature',
value: 'auto')
modules: support getting app_id in pw_check_flatpak Support getting the Flatpak application ID from the .flatpak-info file, similarly as what xdg-desktop-portal does.
2022-07-30 21:29:42 +03:00
option('flatpak',
description: 'Enable Flatpak support',
type: 'feature',
value: 'enabled')
meson_options: Add readline option Make it possible to disable code that depends on readline even if readline is pulled in by another dependency, like bluez.
2022-11-07 15:35:01 +01:00
option('readline',
description: 'Enable code that depends on libreadline',
type: 'feature',
value: 'auto')
pulse-server: add gsettings module Uses a thread to monitor gsettings data. Loads and unload modules based on gsettings. This makes paprefs work.
2022-12-07 09:10:29 +01:00
option('gsettings',
description: 'Enable code that depends on gsettings',
type: 'feature',
value: 'auto')
Rename "compressed-offload to "Compress-Offload" in the code
2022-11-23 15:55:00 +01:00
option('compress-offload',
description: 'Enable ALSA Compress-Offload support',
Add support for ALSA compressed offload See https://docs.kernel.org/sound/designs/compress-offload.html https://github.com/alsa-project/tinycompress
2022-09-20 15:13:16 +05:30
type: 'feature',
alsa-compress-offload-sink: major sink rework * Add support for running the sink as a driver * Detect which compressed formats are actually supported * Correctly open/close/start/stop device according to the node commands * Shift away from tinycompress and use Compress-Offload ioctls directly to be able to access various caps information (including fragment sizes) which are unavailable in the tinycompress API * Implement SPA_PARAM_PropInfo and SPA_PARAM_Props support
2023-02-11 20:52:06 +01:00
value: 'auto')
RLIMITs: add support for generating limits.d files This commit implements generating /etc/security/limits.d/20-pw-defaults.conf and /etc/security/limits.d/25-pw-rlimits.conf files. The numbering is arbitrary and may very well warrant being in the reverse order, however `man 5 limits.conf` does not appear to specify the parsing order or even say exactly how multiples matches will resolve, so the value can be adjusted later, if required. The actual limit values, the match rule and even whether each file is to be installed can be changed via the build system before compilation. Likewise the files can be modified or (re)moved during distro package building phase. The 20-pw-defaults.conf should only be installed on legacy systems lacking both a modern kernel and up to date systemd, because all it does is set the current Linux default. Accordingly its not installed by default. Signed-off-by: Niklāvs Koļesņikovs <89q1r14hd@relay.firefox.com>
2023-02-07 00:26:03 +02:00
option('pam-defaults-install',
description: 'Install limits.d file modifying defaults for all PAM users. Only for old kernels/systemd!',
type: 'boolean',
meson_options: pass proper boolean values to boolean options Passing strings has been deprecated: https://mesonbuild.com/Release-notes-for-1-1-0.html#coercing-values-in-the-option-function-is-deprecated
2024-01-05 03:41:58 +01:00
value: false)
RLIMITs: add support for generating limits.d files This commit implements generating /etc/security/limits.d/20-pw-defaults.conf and /etc/security/limits.d/25-pw-rlimits.conf files. The numbering is arbitrary and may very well warrant being in the reverse order, however `man 5 limits.conf` does not appear to specify the parsing order or even say exactly how multiples matches will resolve, so the value can be adjusted later, if required. The actual limit values, the match rule and even whether each file is to be installed can be changed via the build system before compilation. Likewise the files can be modified or (re)moved during distro package building phase. The 20-pw-defaults.conf should only be installed on legacy systems lacking both a modern kernel and up to date systemd, because all it does is set the current Linux default. Accordingly its not installed by default. Signed-off-by: Niklāvs Koļesņikovs <89q1r14hd@relay.firefox.com>
2023-02-07 00:26:03 +02:00
option('pam-memlock-default',
description : 'The default memlock value for any PAM user in kilobytes. Multiples of 64 recommended.',
type : 'integer',
min: 640,
value: 8192)
option('rlimits-install',
description: 'Install PAM limits.d file. Voids all following rlimits-* options, if false',
type: 'boolean',
meson_options: pass proper boolean values to boolean options Passing strings has been deprecated: https://mesonbuild.com/Release-notes-for-1-1-0.html#coercing-values-in-the-option-function-is-deprecated
2024-01-05 03:41:58 +01:00
value: true)
RLIMITs: add support for generating limits.d files This commit implements generating /etc/security/limits.d/20-pw-defaults.conf and /etc/security/limits.d/25-pw-rlimits.conf files. The numbering is arbitrary and may very well warrant being in the reverse order, however `man 5 limits.conf` does not appear to specify the parsing order or even say exactly how multiples matches will resolve, so the value can be adjusted later, if required. The actual limit values, the match rule and even whether each file is to be installed can be changed via the build system before compilation. Likewise the files can be modified or (re)moved during distro package building phase. The 20-pw-defaults.conf should only be installed on legacy systems lacking both a modern kernel and up to date systemd, because all it does is set the current Linux default. Accordingly its not installed by default. Signed-off-by: Niklāvs Koļesņikovs <89q1r14hd@relay.firefox.com>
2023-02-07 00:26:03 +02:00
option('rlimits-match',
description : 'PAM match rule for the generated limits.d file. @<name> denotes matching a group.',
type : 'string',
value: '@pipewire')
meson: add options to set server and client RT priority Make a rtprio-server and rtprio-client option. Leave the server priority by default to 88 but lower client priority to 83. JACK does something similar by setting clients to rtprio-server - 5. Make module-rt use the client priority by default and bump the server priority explicitly in the config file. Leave the pulse-server to the default rtprio-client, there is no reason to lower this any further because it is really just a regular client. Bump the ffado packetizer thread to rtprio-server + 5 because that is also what JACK does. 88 is still much higher than the value of 60 that JACK uses in Fedora but now this is at least configurable.
2024-02-15 11:53:32 +01:00
option('rtprio-server',
description : 'PipeWire server realtime priority',
type : 'integer',
min: 11,
max: 99,
value: 88)
option('rtprio-client',
description : 'PipeWire clients realtime priority',
type : 'integer',
min: 11,
max: 99,
value: 83)
RLIMITs: add support for generating limits.d files This commit implements generating /etc/security/limits.d/20-pw-defaults.conf and /etc/security/limits.d/25-pw-rlimits.conf files. The numbering is arbitrary and may very well warrant being in the reverse order, however `man 5 limits.conf` does not appear to specify the parsing order or even say exactly how multiples matches will resolve, so the value can be adjusted later, if required. The actual limit values, the match rule and even whether each file is to be installed can be changed via the build system before compilation. Likewise the files can be modified or (re)moved during distro package building phase. The 20-pw-defaults.conf should only be installed on legacy systems lacking both a modern kernel and up to date systemd, because all it does is set the current Linux default. Accordingly its not installed by default. Signed-off-by: Niklāvs Koļesņikovs <89q1r14hd@relay.firefox.com>
2023-02-07 00:26:03 +02:00
option('rlimits-rtprio',
description : 'RR and FIFO scheduler priority permitted for realtime threads of the matching user(s)',
type : 'integer',
min: 11,
max: 99,
value: 95)
option('rlimits-memlock',
description : 'kB of memory each process of the user matched by the rule can lock. Can be unlimited .',
type : 'string',
value: '4194304')
option('rlimits-nice',
description : 'Not niceness permitted for non-realtime threads of the matching user(s)',
type : 'integer',
min: -20,
max: -1,
value: -19)
module-rtp: add opus encoding
2023-03-10 17:39:51 +01:00
option('opus',
description: 'Enable code that depends on opus',
type: 'feature',
value: 'auto')
modules: add ffado driver module
2023-05-28 15:49:09 +02:00
option('libffado',
description: 'Enable code that depends on libffado',
type: 'feature',
value: 'auto')
Add a build option to specify whether pulse gsettings schema should be installed
2022-12-22 15:45:06 +00:00
option('gsettings-pulse-schema',
description: 'Install gsettings schema for pulseaudio',
type: 'feature',
value: 'auto')
pipewire-pulse: add snap permissions support SNAP containers have two main "audio" security rules: * audio-playback: the applications inside the container can send audio samples into a sink * audio-record: the applications inside the container can get audio samples from a source Also, old SNAP containers had the "pulseaudio" rule, which just exposed the pulseaudio socket directly, without limits. This is similar to the current Flatpak audio permissions. In the pulseaudio days, a specific pulseaudio module was used that checked the permissions given to the application and allowed or forbade access to the pulseaudio operations. With the change to pipewire, this functionality must be implemented in pipewire-pulse to guarantee the sandbox security. This patch adds support for sandboxing permissions in the pulseaudio module, and implements support for the SNAP audio security model, thus forbiding a SNAP application to record audio unless it has permissions to do so. The current code for pipewire-pulseaudio checks the permissions of the snap and adds three properties to each new client: * pipewire.snap.id: contains the Snap ID of the client. * pipewire.snap.audio.playback: its value is 'true' if the client has permission to play audio, or 'false' if not. * pipewire.snap.audio.record: its value is 'true' if the client has permission to record audio, or 'false' if not. These properties must be processed by wireplumber to add or remove access permissions to the corresponding nodes. That code is available in a separate patch: https://gitlab.freedesktop.org/pipewire/wireplumber/-/merge_requests/567
2023-11-22 11:26:16 +01:00
option('snap',
Better meson_options description
2023-11-22 16:47:26 +01:00
description : 'Enable Snap permissions support.',
pipewire-pulse: add snap permissions support SNAP containers have two main "audio" security rules: * audio-playback: the applications inside the container can send audio samples into a sink * audio-record: the applications inside the container can get audio samples from a source Also, old SNAP containers had the "pulseaudio" rule, which just exposed the pulseaudio socket directly, without limits. This is similar to the current Flatpak audio permissions. In the pulseaudio days, a specific pulseaudio module was used that checked the permissions given to the application and allowed or forbade access to the pulseaudio operations. With the change to pipewire, this functionality must be implemented in pipewire-pulse to guarantee the sandbox security. This patch adds support for sandboxing permissions in the pulseaudio module, and implements support for the SNAP audio security model, thus forbiding a SNAP application to record audio unless it has permissions to do so. The current code for pipewire-pulseaudio checks the permissions of the snap and adds three properties to each new client: * pipewire.snap.id: contains the Snap ID of the client. * pipewire.snap.audio.playback: its value is 'true' if the client has permission to play audio, or 'false' if not. * pipewire.snap.audio.record: its value is 'true' if the client has permission to record audio, or 'false' if not. These properties must be processed by wireplumber to add or remove access permissions to the corresponding nodes. That code is available in a separate patch: https://gitlab.freedesktop.org/pipewire/wireplumber/-/merge_requests/567
2023-11-22 11:26:16 +01:00
type : 'feature',
value : 'auto')
doc: add options to change what /usr and /etc paths are shown Add options to change the 'prefix' and 'sysconfdir' values shown in documentation, e.g. on config file man pages. Update CI to set them, so that its produced output doesn't show /builds/pipewire/... on man pages
2024-03-10 22:25:42 +02:00
option('doc-prefix-value',
description : 'Installation prefix to show in documentation instead of the actual value.',
type : 'string',
value : '')
option('doc-sysconfdir-value',
description : 'Sysconf data directory to show in documentation instead of the actual value.',
type : 'string',
value : '')
filter-chain: add ebur128 filter The EBU R128 filter measures the signal and generates LUFS control notifications for further processing. It also adds a plugin that can convert LUFS to a gain (based on a target LUFS). Also add an example filter-chain to enable the EBU R128 measurement and how to use the results to adjust the volume dynamically. See #2286 #222 #2210
2024-12-09 11:12:35 +01:00
option('ebur128',
description: 'Enable code that depends on ebur128',
type: 'feature',
value: 'auto')
meson: add fftw option Packagers need to have a way to control whether a dependency is used even if it's installed/available.
2025-06-28 02:59:03 +01:00
option('fftw',
description: 'Enable code that depends on fftw',
type: 'feature',
value: 'auto')
filter-graph: add ONNX plugin It uses the onnxruntime library to parse the onnx file and construct a neural network. It uses the label field to setup the plugin and how to map the various tensors of the model to input, output, control and notify ports. Add an example config for how to use the silero VAD ONNX model with the noise gate.
2025-07-09 14:12:36 +02:00
option('onnxruntime',
description: 'Enable code that depends on onnxruntime',
type: 'feature',
value: 'auto')
Reference in a new issue Copy permalink