- Sep 17, 2019
-
-
George Kiagiadakis authored
A method to copy specific keys from one properties set to another
-
George Kiagiadakis authored
This is very easy to reproduce when the pipewire-alsa integration is installed and you do 'arecord -l'; the alsa plugin connects and disconnects again before the proxy is ready. In this case we have to skip remote-global-added and we also have to be careful with the references: the global-removed callback is called earlier, so the core's reference to the proxy is gone and the GTask is the only thing holding a reference to the proxy. When we unref the GTask, the proxy is also unrefed, so we have to keep an additional reference in order to avoid crashing when accessing the hash table below.
-
- Sep 07, 2019
-
-
George Kiagiadakis authored
-
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.
-
- Aug 29, 2019
-
-
George Kiagiadakis authored
In case the proxy was created with wp_proxy_new_wrap(), the event listener was not attached on the pw_proxy
-
George Kiagiadakis authored
-
George Kiagiadakis authored
-
- Aug 27, 2019
-
-
George Kiagiadakis authored
-
George Kiagiadakis authored
* add proxy sync method * add wrapers for enum/set/subscribe_params * move the info structure handling to the subclasses * expose info->props as WpProperties
-
Julian Bouzas authored
-
- Aug 26, 2019
-
-
Julian Bouzas authored
-
- Aug 25, 2019
-
-
George Kiagiadakis authored
-
- Aug 24, 2019
-
-
George Kiagiadakis authored
-
- Aug 19, 2019
-
-
Julian Bouzas authored
-
George Kiagiadakis authored
-
- Aug 13, 2019
-
-
Julian Bouzas authored
-
Julian Bouzas authored
-
- Jul 25, 2019
-
-
George Kiagiadakis authored
-
Julian Bouzas authored
-
- Jul 12, 2019
-
-
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
-
- Jul 10, 2019
-
-
Julian Bouzas authored
-
Julian Bouzas authored
-
Julian Bouzas authored
-
Julian Bouzas authored
-
Julian Bouzas authored
-
- Jun 28, 2019
-
-
Julian Bouzas authored
-
Julian Bouzas authored
-
- Jun 27, 2019
-
-
Julian Bouzas authored
-
- Jun 26, 2019
-
-
Julian Bouzas authored
-
Julian Bouzas authored
-
- Jun 24, 2019
-
-
Julian Bouzas authored
-
Julian Bouzas authored
-
George Kiagiadakis authored
-
George Kiagiadakis authored
-
- Jun 20, 2019
-
-
Julian Bouzas authored
-
Julian Bouzas authored
-
Julian Bouzas authored
-
George Kiagiadakis authored
-
George Kiagiadakis authored
Fixes #1
-