- May 07, 2021
-
-
Arnaud Ferraris authored
This can be easily missed when upgrading the package, so it's safer to use a wildcard here as there won't be another `/usr/include/wireplumber-*` folder during build. Signed-off-by:
Arnaud Ferraris <arnaud.ferraris@collabora.com>
-
Arnaud Ferraris authored
Signed-off-by:
Arnaud Ferraris <arnaud.ferraris@collabora.com>
-
Arnaud Ferraris authored
This commit adds minimum version conditions matching upstream's requirements. It also adds `${gir:Depends}` to the GIR package in order to make sure we don't miss any such dependency, as suggested by lintian. Signed-off-by:
Arnaud Ferraris <arnaud.ferraris@collabora.com>
-
Arnaud Ferraris authored
It should match the Typelib file name. Signed-off-by:
Arnaud Ferraris <arnaud.ferraris@collabora.com>
-
Arnaud Ferraris authored
The library package name should include the SO version as well, so rename it to `libwireplumber-0.4-0`. Signed-off-by:
Arnaud Ferraris <arnaud.ferraris@collabora.com>
-
Arnaud Ferraris authored
Signed-off-by:
Arnaud Ferraris <arnaud.ferraris@collabora.com>
-
Signed-off-by:
Frédéric Danis <frederic.danis@collabora.com>
-
George Kiagiadakis authored
-
George Kiagiadakis authored
Not really a hard requirement, wrt libpipewire API, but it's hard to keep runtime compatibility with earlier versions when it comes to configuration options
-
George Kiagiadakis authored
-
George Kiagiadakis authored
Plugin() is confusing because it's not a constructor, it just finds an existing instance of a plugin object. All other camel-case functions are constructors in the current lua API.
-
- May 06, 2021
-
-
Julian Bouzas authored
-
George Kiagiadakis authored
This is no longer used and likely not very useful now that we have a simpler design. We can re-add it in the future if necessary, but let's keep it out of the 0.4 release.
-
George Kiagiadakis authored
Also rename the intermediate lua api table WpDebug -> WpLog Keeps things more consistent with the function names (wp_log*), with the lua api (Log.*) and with pipewire using log.{h,c} as well. After all, these functions are for logging...
-
George Kiagiadakis authored
This is not part of the policy, it's something standalone that writes metadata Needs to be disabled by default, since it's not built by default now
-
George Kiagiadakis authored
-
George Kiagiadakis authored
-
George Kiagiadakis authored
-
George Kiagiadakis authored
-
George Kiagiadakis authored
-
George Kiagiadakis authored
-
George Kiagiadakis authored
-
George Kiagiadakis authored
We no longer have the audiofade-related code
-
George Kiagiadakis authored
This is only intended to be used with specific embedded applications. There is no good reason to use it on a standard desktop environment.
-
- May 05, 2021
-
-
George Kiagiadakis authored
-
- May 04, 2021
-
-
Julian Bouzas authored
-
Julian Bouzas authored
Handles SUSPEND and RESUME wpipc requests in order to set metadata that will eventually unlink or re-link endpoints.
-
Julian Bouzas authored
Simple library that uses sockets for inter-process communication. It provides an API to create server and client objects. Users can add custom handlers in the server, and clients can send requests for those custom handlers.
-
- Apr 27, 2021
-
-
George Kiagiadakis authored
After all, we can just load multiple lua config files/directories from a single .conf file and so have both styles available for the user to choose at runtime
-
George Kiagiadakis authored
These allow running multiple instances of wireplumber with different config files. The config file is denoted on the service name, ex: wireplumber@bluetooth loads bluetooth.conf
-
- Apr 26, 2021
-
-
George Kiagiadakis authored
-
George Kiagiadakis authored
This only applies to non-device nodes, because monitorVolumes are not exposed on device Routes
-
George Kiagiadakis authored
Configurable. Replaces the "flatpak" access policy.
-
George Kiagiadakis authored
This configuration allows splitting wireplumber into multiple instances. The "main" instance takes care of loading and managing devices The "policy" instance does all the linking and implements endpoints The "bluetooth" instance runs the bluetooth devices & nodes Test with (in separate terminals): ./wp-uninstalled.sh -c config-split -- wireplumber -c main.conf ./wp-uninstalled.sh -c config-split -- wireplumber -c policy.conf ./wp-uninstalled.sh -c config-split -- wireplumber -c bluetooth.conf
-
George Kiagiadakis authored
Similar to pw-uninstalled.sh, but without an interactive shell
-
- Apr 22, 2021
-
-
George Kiagiadakis authored
This is not useful, we can do this on the pipewire-style config files
-
George Kiagiadakis authored
Also, use a context property to control whether to enable this core or not and enable it only in the daemon
-
George Kiagiadakis authored
with inverted semantics
-
George Kiagiadakis authored
This allows configuring: * the scripting engine, in case we ever add another one * the app name, so that we can distinguish multiple instances of wireplumber * the log level in the same way as pipewire * wireplumber components to load. This allows loading components even without a scripting engine (for a mimimal daemon) and also allows configuring which lua config file(s) to load * additional pw_context properties that pipewire modules may be using * the exact pipewire modules to load (instead of relying on client.conf)
-
- Apr 21, 2021
-
-
George Kiagiadakis authored
And don't override PIPEWIRE_DEBUG, unless WIREPLUMBER_DEBUG is set. This allows pipewire to use log.level as well to set up its logging. If WIREPLUMBER_DEBUG is set, though, override PIPEWIRE_DEBUG to prevent log.level from being used.
-