- Sep 25, 2019
-
-
Julian Bouzas authored
-
Julian Bouzas authored
-
Julian Bouzas authored
-
- Sep 22, 2019
-
-
George Kiagiadakis authored
GVariant is instructed to store a 64-bit unsigned integer (mode "t") but we pass it a pointer to a pointer to read this value out, which will crash in 32-bit architectures, as the pointer doesn't have enough bits and g_variant_lookup therefore corrupts the stack.
-
- Sep 17, 2019
-
-
George Kiagiadakis authored
-
George Kiagiadakis authored
This is a generic WpMonitor loader that sets up the WpMonitor properties from the module arguments and applies some well-known properties to the device & node objects
-
- Sep 07, 2019
-
-
George Kiagiadakis authored
In practice we always create a remote and connect to pipewire. Any other scenario is invalid, therefore, it is not justified to be confused with so many classes for such small functionality. This simplifies a lot the modules code. Also, this commit exposes the pw_core and pw_remote objects out of WpCore. This is in practice useful when dealing with low-level pw and spa factories, which are used in the monitors. Let's not add API wrappers for everything... Bindings will never use this functionality anyway, since it depends on low level pipewire C API.
-
George Kiagiadakis authored
-
- Sep 05, 2019
-
-
George Kiagiadakis authored
Since the alsa endpoints class was renamed...
-
- Sep 02, 2019
-
-
Julian Bouzas authored
-
- Aug 29, 2019
-
-
George Kiagiadakis authored
-
George Kiagiadakis authored
-
- Aug 28, 2019
-
-
Julian Bouzas authored
-
Julian Bouzas authored
-
Julian Bouzas authored
-
Julian Bouzas authored
-
- Aug 27, 2019
-
-
Julian Bouzas authored
-
- Aug 26, 2019
-
-
Julian Bouzas authored
-
Julian Bouzas authored
-
Julian Bouzas authored
-
- Aug 19, 2019
-
-
Julian Bouzas authored
-
George Kiagiadakis authored
-
- Aug 15, 2019
-
-
Julian Bouzas authored
-
- Aug 13, 2019
-
-
Julian Bouzas authored
-
Julian Bouzas authored
-
Julian Bouzas authored
-
Julian Bouzas authored
-
Julian Bouzas authored
-
- Jul 30, 2019
-
-
George Kiagiadakis authored
When two clients have the same role, the current policy should favor the newest client.
-
George Kiagiadakis authored
-
- Jul 25, 2019
-
-
Julian Bouzas authored
-
George Kiagiadakis authored
-
Julian Bouzas authored
-
Julian Bouzas authored
-
Julian Bouzas authored
-
- Jul 15, 2019
-
-
Julian Bouzas authored
-
- Jul 12, 2019
-
-
George Kiagiadakis authored
Avoids crashing if a rescan is scheduled but the policy module is destroyed in the meantime
-
George Kiagiadakis authored
* Every client has a priority based on its role * For playback, we allow only a single client to play at a time * For capture, we allow all clients to capture simultaneously * Every time the "selected" device changes (either because devices are discovered/removed or because the user changed the selection), the clients are re-linked to the new "selected" device. * When a playback client quits and there are others waiting unlinked, the highest priority one is linked automatically. * This also properly fixes re-linking the correct client(s) to the correct device(s) when wireplumber exits and restarts.
-
Julian Bouzas authored
-
Julian Bouzas authored
-