Request for Assistance with Pipewire Integration in Docker Container
I am reaching out to request your guidance and expertise on a specific technical challenge related to integrating Pipewire into a Docker container for our open source radio show scheduling system AURA.
Problem Description:
We currently use a Docker container to manage the scheduling of radio shows and the handling of multiple inputs, both from a soundcard and a software level. Liquidsoap is utilized for this purpose. However, we've encountered latency issues when simultaneously using the line-in and line-out of the soundcard with the pure ALSA setup (configured in .asoundrc).
Proposed Solution:
To overcome these latency challenges, we are exploring the possibility of integrating Pipewire into our Docker container. Pipewire seems to offer a more efficient and flexible solution for managing audio streams. However, we are currently unsure about how to configure Pipewire and connect it to the soundcard within the Docker environment.
Specific Questions:
- How can we configure Pipewire within a Docker container to ensure seamless integration with our soundcard?
- Are there any best practices or recommended approaches for managing audio streams with Pipewire in a Dockerized environment?
- Should we be using a session manager like WirePlumber, and if so, how should it be configured to meet our requirements?
I understand that this might not be the typical platform for such inquiries, but any advice, guidance, or suggestions you can provide would be greatly appreciated. We are eager to explore Pipewire as a potential solution to our latency issues and enhance the performance of our radio show scheduling system.