{"id":116811,"date":"2024-06-28T00:05:43","date_gmt":"2024-06-27T22:05:43","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/vypusk-multimedijnogo-servera-pipewire-1-2-0"},"modified":"2024-06-28T00:05:43","modified_gmt":"2024-06-27T22:05:43","slug":"vypusk-multimedijnogo-servera-pipewire-1-2-0","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/vypusk-multimedijnogo-servera-pipewire-1-2-0","title":{"rendered":"Release of the multimedia server PipeWire 1.2.0.","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
After seven months of development, a new stable branch of the multimedia server PipeWire 1.2.0 has been formed, replacing the PulseAudio sound server. It differs by adding tools for handling video streams, the ability to process audio with minimal latency, and a new security model for managing access at the level of individual devices and streams. The project is supported in GNOME and is used by default in Fedora Linux, RHEL, Ubuntu, Debian, SUSE\/openSUSE, and many other Linux distributions. The project's code is written in C and is distributed under the LGPLv2.1 license.<\/p>\n
PipeWire is based on a multi-process architecture that allows multiple applications to share access to content. \nIt offers capabilities for processing any multimedia streams, mixing and redirecting streams with video, as well as managing video sources such as video capture devices, webcams, or content displayed by applications on the screen. For example, PipeWire enables multiple applications to work together with a webcam and resolves issues related to secure screen content capture and remote screen access in a Wayland environment. <\/p>\n
When used as a sound server, PipeWire can provide minimal latency and offer functionality that combines the capabilities of PulseAudio and JACK, including consideration of the needs of professional audio processing systems that PulseAudio could not address. Additionally, PipeWire features an advanced security model that allows access management at the level of individual devices and specific streams, simplifying the organization of audio and video forwarding from and to isolated containers. One of the main goals is to support self-contained applications in the Flatpak format and to operate within a graphical stack based on Wayland.<\/p>\n
In the new version:<\/p>\n
\n
The data stream processing model based on a node graph has been enhanced with support for asynchronous processing, where the node graph does not block when there is no output from a specific node, but continues to operate using data from a node obtained in the previous cycle. Thus, at the cost of a one-cycle delay, it avoids situations where one node blocks the operation of other nodes in the graph.\n
The concept of synchronized node groups (node.sync-group) has been implemented, allowing the creation of groups of nodes that can be activated simultaneously by the scheduler. This feature can be used for the simultaneous scheduling of node activation during JACK transport startup.\n
Error information output in the configuration file has been improved, adding a mention of where the error occurred in the settings (line number and position in the line).\n
Support for Explicit Sync technology has been added, allowing applications to inform the Wayland protocol-based compositor about frame output readiness, which helps to reduce delays and eliminate artifacts during graphic output. In particular, Explicit Sync resolves output disruption and stuttering issues on NVIDIA GPU systems with Wayland support enabled.\n
The ability to specify mandatory metadata when agreeing on buffer parameters used to ensure support for 'Explicit Sync' has been implemented.\n