There are multiple approaches available when configuring PulseAudio to suit the requirements of a given use case.
Pulseaudio for windows driver#
Enabling a PulseAudio null sink to act as a virtual audio output device requires only a single directive in a configuration file.ĭue to its flexibility, PulseAudio is the recommended audio driver for Linux containers. PulseAudio is a higher-level sound server and provides far more flexibility as a result of its client/server model. Creating an ALSA loopback device to act as a virtual audio output device involves loading kernel modules, which requires running containers with specific security privileges.
Pulseaudio for windows drivers#
These drivers include the Advanced Linux Sound Architecture (ALSA) and PulseAudio:ĪLSA is the lower-level option, and provides less flexibility than a sound server such as PulseAudio. As a result, the Audio Mixer system will only initialise successfully under Linux if one of the supported SDL audio drivers is available. The SDL2 audio backend for Linux does not support the use of a null audio device. For more details, see the specific sections for Linux and Windows. However, support for using a null audio device varies between the backend implementations for different platforms. The Audio Mixer system supports the concept of a “null audio device”, which allows the Engine to generate audio output even when there are no physical audio devices available. This is particularly relevant for use cases such as Pixel Streaming, which leverages the Audio Mixer system in order to capture generated audio and transmit it to client devices over WebRTC. This is important when discussing Unreal Engine containers because the Engine’s Audio Mixer system must still be initialised in order to use audio mixing functionality, even when the generated audio data will be written to file or transmitted over a network rather than sent to an output device. When running applications inside a container, there are no physical audio devices available by default. Using the host system’s PulseAudio server.Automatically spawning a PulseAudio server inside the container.No additional configuration is required for Windows containers.Multiple approaches are available for enabling audio output in Linux containers.Audio output must be enabled for use cases that leverage the Unreal Engine’s audio mixing functionality.