| Message ID | 20230721194032.2185514-1-f_l_k@t-online.de |
|---|---|
| State | Under Review |
| Headers | show |
| Series | [meta-multimedia] pipewire: update 0.3.73 -> 0.3.75 | expand |
diff --git a/meta-multimedia/recipes-multimedia/pipewire/pipewire_0.3.73.bb b/meta-multimedia/recipes-multimedia/pipewire/pipewire_0.3.75.bb similarity index 99% rename from meta-multimedia/recipes-multimedia/pipewire/pipewire_0.3.73.bb rename to meta-multimedia/recipes-multimedia/pipewire/pipewire_0.3.75.bb index b27886d0cc..72533310cb 100644 --- a/meta-multimedia/recipes-multimedia/pipewire/pipewire_0.3.73.bb +++ b/meta-multimedia/recipes-multimedia/pipewire/pipewire_0.3.75.bb @@ -13,7 +13,7 @@ LIC_FILES_CHKSUM = " \ DEPENDS = "dbus ncurses" -SRCREV = "44deacbc670ccf6c02d66a48b756a16167d8048f" +SRCREV = "a3bd0f7a0a8dec9045deeb5eb3eb92b09ff75d57" SRC_URI = "git://gitlab.freedesktop.org/pipewire/pipewire.git;branch=master;protocol=https" S = "${WORKDIR}/git"
This is a bugfix release that is API and ABI compatible with previous 0.3.x releases. - Link permissions between nodes are now enforced. This avoids potential portal managed screencast nodes to link to the camera even though it was not assigned permissions to do so by the session manager. - Libcamera and v4l2 devices now have properties so that duplicates can be filtered out by the session manager. - A bug with draining was fixed where a buffer would be marked EMPTY and would not play when it contained drained samples. (#3365) - Many fixes and improvements. - Permissions for links between nodes are now enforced. The link will now check that the owner clients of the nodes can see eachother before allowing the link. This avoids screensharing clients to accidentally being linked to the camera nodes by the session manager. A side effect is that patchbay tools will no longer be able to link portal managed screencast nodes to the camera, for this we need a new permission for those patchbay clients. (wireplumber#218) - The stream.rules/filter.rules are now evaluated when connecting the stream/filter so that more properties can be matched. (#3355) - Move some internal events from the context to the nodes to better handle per-node threads in the future. - The thread-loop will now signal when the thread is started. - A timestamp workaround in module-raop was reverted because it does not work in all cases. Instead latency was increased to 1.5 seconds, which also makes the problematic device in question work. (#3247) - The profiler module was reworked a bit to use the new node realtime events. It should now also handle dynamically added and removed drivers. - The module-rt now does the rtkit calls from a separate thread so that it does not block the main thread. This could cause deadlocks during startup in some cases. (#3357) - Atomic operation macros were move from internal pipewire API to public API. - The video-info structure now has a new SPA_VIDEO_FLAG_MODIFIER_FIXATION_REQUIRED flag to instruct the application to fixate the modifiers. This simplifies some logic in applications a lot. - The libcamera and v4l2 nodes now have properties to enumerate the device id they are using. This can be used to match v4l2 devices and libcamera devices and filter out duplicates. - A bug with draining was fixed where a buffer would be marked EMPTY and would not play when it contained drained samples. (#3365) This is a quick bugfix release that is API and ABI compatible with previous - Merge scope based cleanup macros. - Add ratelimit function. Signed-off-by: Markus Volk <f_l_k@t-online.de> --- .../pipewire/{pipewire_0.3.73.bb => pipewire_0.3.75.bb} | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) rename meta-multimedia/recipes-multimedia/pipewire/{pipewire_0.3.73.bb => pipewire_0.3.75.bb} (99%)