mirror of
https://gitlab.freedesktop.org/pipewire/pipewire
synced 2024-10-01 13:44:40 +00:00
0.3.75
This commit is contained in:
parent
8d1b3f6f48
commit
a3bd0f7a0a
56
NEWS
56
NEWS
|
@ -1,3 +1,56 @@
|
|||
# PipeWire 0.3.75 (2023-07-21)
|
||||
|
||||
This is a bugfix release that is API and ABI compatible with previous
|
||||
0.3.x releases.
|
||||
|
||||
## Highlights
|
||||
- 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.
|
||||
|
||||
|
||||
## PipeWire
|
||||
- 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.
|
||||
|
||||
## modules
|
||||
- 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)
|
||||
|
||||
## SPA
|
||||
- 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)
|
||||
|
||||
Older versions:
|
||||
|
||||
|
||||
# PipeWire 0.3.74 (2023-07-12)
|
||||
|
||||
This is a quick bugfix release that is API and ABI compatible with previous
|
||||
|
@ -33,9 +86,6 @@ This is a quick bugfix release that is API and ABI compatible with previous
|
|||
- Merge scope based cleanup macros.
|
||||
- Add ratelimit function.
|
||||
|
||||
Older versions:
|
||||
|
||||
|
||||
# PipeWire 0.3.73 (2023-07-06)
|
||||
|
||||
This is a bugfix release that is API and ABI compatible with previous
|
||||
|
|
|
@ -1,5 +1,5 @@
|
|||
project('pipewire', ['c' ],
|
||||
version : '0.3.74',
|
||||
version : '0.3.75',
|
||||
license : [ 'MIT', 'LGPL-2.1-or-later', 'GPL-2.0-only' ],
|
||||
meson_version : '>= 0.61.1',
|
||||
default_options : [ 'warning_level=3',
|
||||
|
|
Loading…
Reference in a new issue