- 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.
-
George Kiagiadakis authored
Initialize the log level with WIREPLUMBER_DEBUG in wp_init()
-
- Apr 19, 2021
-
-
George Kiagiadakis authored
This allows the channelVolumes and mute props to affect the output of the null sink's monitor ports. This way we will be able to use channelVolumes to track the configured volume of the endpoint and the monitorVolumes to implement volume ducking.
-
- Apr 16, 2021
-
-
George Kiagiadakis authored
This fixes adjusting volume for bluetooth nodes. Previously, the spa device would request a software volume change that we did not handle because WpImplNode was not a WpPipewireObject and there was no way to set the Props param on it.
-
George Kiagiadakis authored
-
- Apr 15, 2021
-
-
George Kiagiadakis authored
-
George Kiagiadakis authored
These don't make much sense here. In the endpoint policy we want the clients to be linked to the endpoint that matches their role and never move. Also, endpoint priorities are useless. If no endpoint matches the role, then just ignore the client.
-
George Kiagiadakis authored
-
George Kiagiadakis authored
-
George Kiagiadakis authored
-
- Apr 13, 2021
-
-
George Kiagiadakis authored
This allows closures to be properly unrefed when they are no longer used instead of staying alive until wireplumber exits Because GClosure has no weak references, we are now sharing the GPtrArray that holds these references among all the active closures and each closure is responsible for removing itself from the array when it is finalized. The lua engine holds a reference to a "store" object that also has a pointer to the array and when this "store" is finalized, all closures are invalidated and removed. Even if they stay alive afterwards, they are only holding a ref to an empty array
-
George Kiagiadakis authored
-