- May 18, 2020
-
-
George Kiagiadakis authored
-
- May 16, 2020
-
-
George Kiagiadakis authored
-
George Kiagiadakis authored
-
George Kiagiadakis authored
-
- May 15, 2020
-
-
Julian Bouzas authored
-
Julian Bouzas authored
-
Julian Bouzas authored
-
- May 14, 2020
-
-
George Kiagiadakis authored
-
George Kiagiadakis authored
+ use a more correct naming scheme to match the one from Spa + remove the default video source, since we now use a different session for video
-
George Kiagiadakis authored
This makes WIREPLUMBER_DEBUG behave just like PIPEWIRE_DEBUG. Same levels, same syntax, easier for users. ERROR & CRITICAL are always printed, as they should; there is no point in disabling them, since: - ERRORs are always fatal and should never ever happen - CRITICALs are assertion failures and indicate bugs that need to be fixed
-
George Kiagiadakis authored
* use a short level name, like pipewire does * color the timestamp to compensate for the loss of the visible level name * use 18 chars for the category
-
George Kiagiadakis authored
-
George Kiagiadakis authored
-
- May 13, 2020
-
-
George Kiagiadakis authored
-
George Kiagiadakis authored
libpipewire already prints this, so we get it duplicated on the log
-
George Kiagiadakis authored
This happens when the daemon fails to connect and the not installed object managers try to get installed, but the weak ref to the core is already gone
-
George Kiagiadakis authored
-
George Kiagiadakis authored
object managers that are registered a bit early (such as the one in wireplumber-cli) have no use if they are declared as installed before any globals appear. After the initial registry startup, there should be at least 1 global, the core (id=0), so even if this client has no access to any object, the object manager should be able to finish its installation successfully
-
Julian Bouzas authored
-
Julian Bouzas authored
-
George Kiagiadakis authored
the on_sessions_exported callback runs from within the context of export_tmp_globals in object-manager.c and when plugins register more object managers, it modifies the object managers list that export_tmp_globals is iterating over, making things behave really weird
-
George Kiagiadakis authored
-
George Kiagiadakis authored
-
George Kiagiadakis authored
-
- May 12, 2020
-
-
Julian Bouzas authored
-
Julian Bouzas authored
-
George Kiagiadakis authored
-
George Kiagiadakis authored
Features are flags, therefore we must NEVER use them without a shift, otherwise bad mistakes happen, like the previous mistake of declaring WP_SESSION_FEATURE_LINKS as the number after WP_SESSION_FEATURE_ENDPOINTS, which ended up being (WP_SESSION_FEATURE_ENDPOINTS | WP_PROXY_FEATURE_PW_PROXY) and it was always becoming available together with the ENDPOINTS feature.
-
George Kiagiadakis authored
-
George Kiagiadakis authored
This serves as a base class for daemon plugins, which are implemented inside modules
-
George Kiagiadakis authored
And also provide a way to disable this integration at runtime to get pipewire's log back, with WIREPLUMBER_NO_PW_LOG=1
-
George Kiagiadakis authored
The GLib error level is fatal, but pipewire doesn't use it that way. Also, the GLib critical level is meant only for programming errors (assertions) and not for runtime errors. warn & msg levels really fit well with the error & warn, as they are being used in pipewire currently.
-
Julian Bouzas authored
-
Julian Bouzas authored
-
Julian Bouzas authored
-
Julian Bouzas authored
-
Julian Bouzas authored
-
- May 11, 2020
-
-
Julian Bouzas authored
-
George Kiagiadakis authored
-
Julian Bouzas authored
-