Automatic installer for virtual sinks and sources when using Focusrite Scarlett devices with PipeWire
Go to file
2024-09-10 19:33:15 +02:00
lib 🎉 initial codebase 2024-09-07 00:43:50 +02:00
profile 🎉 initial codebase 2024-09-07 00:43:50 +02:00
.editorconfig 🔧 add editorconfig 2024-08-09 14:01:49 +02:00
.gitignore 🎉 initial codebase 2024-09-07 00:43:50 +02:00
build.sh 🎉 initial codebase 2024-09-07 00:43:50 +02:00
LICENSE 📄 add license 2024-08-09 14:01:34 +02:00
main.sh 🎨 dont print newline inside sub-shells 2024-09-10 19:17:27 +02:00
README.md 🐛 fix pipe problems 2024-09-10 19:33:15 +02:00
version.sh 🎉 initial codebase 2024-09-07 00:43:50 +02:00

Focusrite Scarlett with PipeWire

Automatic installer for virtual sinks and sources when using Focusrite Scarlett devices with PipeWire

You just got yourself a new shiny audio interface with a hell lot of channels? Great!
Your Linux PC only lets you use it as one 5.1 Surround Sound Output? Not so Great!
But don't worry, this repo got you covered.

You should also have a look at Geoffrey Bennett's Linux GUI for Scarlett Interfaces.

Usage

Download and run the script; you will be guided through the setup:

$ wget "https://git.tjdev.de/DrMaxNix/scarlett-pipewire/releases/download/latest/script.sh" -O scarlett-pipewire.sh && bash scarlett-pipewire.sh

Tip

If you want to read the script before executing it, you should use the version contained in the repository (main.sh), because the release variant (script.sh) has been minified.

Important

After you have set up your virtual virtual sources and sinks, make sure not to select the audio interface in your system settings directly, as this may disable the Pro Audio profile that is required for the virtual mappings to work. One of the symptoms that this happened is that audio is always coming from channels 1+2 even though other ones are selected. If you accidentally ran into this problem, it can easily be fixed by running the script again.

Contributing

As I only own one interface model, the mapping profiles (profile/) for all other supported models are based on research and educated guesses. If your interface is currently not supported or seems to have divergent mappings, feel free to contribute by creating a pull request or issue for it!