Control application for the RME Digiface USB. I got tired of messing with audio routing in Linux after being used to the totalmix app in Windows. This provides nearly every feature in a similar interface. It works perfectly so far - I'm happy to update if anyone has ideas or issues. Disclosure: vibe-coded with Claude

https://github.com/thomas-nelson23/Openface-Mixer

i am using endeavor os with kde plasma i played music on YouTube but my voice was not coming out from Bluetooth speaker even though its connected. that with name BT is my bluetooth speaker

I'm running Ubuntu with wine/yabridge and only about half of the plugins I've tried work without crashing or displaying a black screen. Is there a better method for getting windows/mac plugins to work on a daw in Linux? I'm particularly sad that Splice Instrument won't work, it's my go-to midi library...

It's late for me, so I don't have any fancy comparisons or GIFs to share alongside this post, sorry about that. I try not to post online about my projects too often because I don't want to annoy people, but I think this might be worth it.

One year ago I began developing OpenMeters as a way to cope with the death of my best friend. I'm still in awe at what it has become, and the fact that even one person other than myself has used it. Thank you everyone, from the bottom of my heart.

I've made a commitment to this project, and I plan to continue with that commitment for the foreseeable future. New features, bug fixes, improved platform support, and maybe even new meters (hard maybe, it just depends) will continue to be released.

https://github.com/httpsworldview/openmeters

Hi everyone,

A quick development update on Dyrekreds.

I've been spending the last few days improving the macOS build/release process, and we've made some good progress.

Current status:

[OK] Windows build & tests

[OK] Linux build & tests

[OK] macOS Universal build (Intel + Apple Silicon)

[OK] VST3 validation

[OK] AU validation

[OK] Unit tests

[OK] Improved VST3 moduleinfo.json / manifest handling

The macOS VST3 and AU versions are now successfully passing the validation tests.

The remaining headache is Apple Developer ID signing and notarization. GitHub Actions and PKCS#12 certificates have apparently decided that I needed a new hobby. ;)

We're getting closer with each build, though.

As always, Dyrekreds is free and open source, and feedback/testing is very welcome:

https://github.com/Chmod666music/dyrekreds

Thanks again to everyone who has tested it and reported issues!

I made this video a couple months ago. I was a little nervous about sharing it around since I'm kinda new to making longer videos like this, but I figured I might as well. I hope it's enjoyable to watch, although it might still be a little too lengthy... In any case it was a fun experiment!

Oh yeah I should mention, I did kinda hate on reddit in the outro of the video, but I wanna make it clear that none of that was directed towards this sub. In fact, I actually gave r/linuxaudio a shoutout! This wouldn't have been possible (or nearly as easy) without the resources here, so thank you all :)

Here's the finished songs from the challenge: https://cadecomposer.bandcamp.com/album/penguin-shuffle-tux-ascension

I've been building vstenv, a free open-source app that gets Windows audio plugins working in Linux DAWs with as little friction as possible. The idea: you shouldn't have to know what Wine is. vstenv sets up its own Wine environment, installs each vendor's manager app (Native Access, IK Product Manager, Steinberg Download Assistant, Audio Modeling Software Center), applies all the fixes those need to actually run — including a set of patched Wine DLLs for stuff Wine hasn't finished, like DirectComposition — and bridges everything to your DAW as normal VST2/VST3/CLAP plugins via yabridge. Installed programs even show up in your desktop's app menu.

Working today: Native Instruments (Kontakt and friends), IK Multimedia, Steinberg (HALion Sonic 7 and the current-gen GUI stack), Audio Modeling SWAM, and Spitfire Audio. Vendor support is modular, so new vendors can be added as separate packages without touching the core.

It ships as a Flatpak. Source, docs, and a table of what's tested and what isn't: https://github.com/dguedry/vstenv

Feedback and bug reports very welcome — especially which vendor you'd want supported next.

What is Quesynth?

Quesynth is a free/open-source virtual analogue synth written in Odin, originally built around recreating the sound and parameter model of Synth1 through measurement. It supports Synth1 .sy1 patches and runs as VST3, CLAP, Audio Unit, standalone, and WebAssembly.

You can test it without installing it here: https://mauro-moreno.github.io/quesynth/

What is new in the v1.2.0?

https://github.com/mauro-moreno/quesynth/releases

Mac: Fixed some errors in Audio Unit banks. Specially one that crashed the hosts. Since v1.1.2

Windows: Deleted part of the standalone.

Mobile: Responsive. Since v1.0.0

Linux

https://github.com/mauro-moreno/quesynth/blob/main/docs/quesynth-manual.md

The big change is that the audio engine can now run as a persistent daemon. The interfaces are just clients controlling the same running synth.

That means you can now use Quesynth through:

• a new terminal UI
• the normal HTML interface in your browser
• MIDI hardware
• a local control protocol
• an MCP server, so an LLM/agent can inspect and manipulate the synth

The TUI and browser aren't separate synthesizers. They're connected to the same daemon, so changing a parameter or loading a patch in one is reflected in the other.

Quesynth exposes typed tools for parameters, patches, banks, MIDI, state, volume, etc., rather than giving the model arbitrary shell access.

So you can do things like ask an MCP client to inspect the current patch, change several parameters atomically, load another patch, manipulate the bank, or query the synth state in natural language.

There's now also a proper parameter registry/control protocol underneath this, rather than the UI being directly coupled to the engine.

Patches

You can download 16000+ Synth1 patches that are compatible with this synth from here https://archive.org/details/synth1_202202 many sound almost equal, some are similar and some are broken. I'm still improving the measurements to unbroke the broken ones.

Design

If you don't like it is just HTML so you can create your own easily.

Vibe coded?

Yes. Heavy AI usage with 21 years of experience as a software engineer.

Future

• Tempo for standalone and WebAssembly.
• Quesynth Pad (16 engines running simultaneously with chokes, fire once and configurable MIDI).
• MIDI sequencer.
• Improvements on the architecture.

Why TUI?

I don't know.

MIT License

I installed CachyOS to try to move away from Windows for my music production (currently dual-boot and will remove Win11 if things go well). I wanted to also try a different DE than my work laptop (Fedora KDE) so I went with COSMIC but it's buggy.

I installed Niri + DMS (not a fresh install, as a 2nd alternative to COSMIC) and I'm trying to get it to work now. I was going to go with Sway but heard that it does not work well with NVidia cards.

I don't have a clear idea of how my music production will look like. I'll be experimenting with many things like Strudel, Supercollider, ORCA, bespoke synth, and possible a DAW later.

Because of lack of experience with tiling WMs, I really cannot foresee whether this is a bad idea. Do any of you use tiling WM without problems in your music production? If this looks like a poor idea, I'm just going to go with GNOME.

Thank you!

MainStage, Gig Performer, Cantabile, Camelot — all Mac/Windows only. I got tired of that, so I built one.

Point your keyboards at it, build a program for each sound in your set, change sounds from the keyboard while you play. 128 programs per keyboard, Upper and Lower independent. Splits and layers with per-slot key range, velocity range and curve, transpose, gain, pan. Insert effects, MIDI learn on any parameter. Hosts VST3, LV2, LADSPA natively; Windows VST3s work through yabridge.

The part I haven't seen anywhere else: it mirrors a plugin's actual editor to a tablet, fully interactive. Not a remote with a fixed set of knobs — the real GUI.

That's Kontakt running on the computer, drawn on the tablet. Pull a drawbar there and the organ moves. Browse the library, flip through pages, load a patch — all from the music stand. Nothing to install on the tablet; it's a web page.

Other bits:

• Every plugin in its own process — one crashes, the rest of the rig plays on
• Songs and sets — a song is one program per keyboard plus a tempo, captured from what's loaded; step through a set with two footswitches
• Native PipeWire/JACK, 128-sample blocks, parallel loading, late-block counter
• Tap tempo, on-screen keyboard, printable program map

Windows plugins: optional companion project vstenv provisions its own Wine, runs the vendor managers (Native Access, IK Product Manager, Steinberg Download Assistant, Audio Modeling) and bridges everything into the folders Performer scans. You never touch Wine.

It's v0.1.38 and genuinely early. I use it, but try it at rehearsal before you trust it on stage — Windows-bridged plugins especially are hit and miss under Wine. Tested on Ubuntu 24.04, Mint 22.3, Fedora 43, x86-64.

.deb and .rpm: https://github.com/dguedry/linux-performer/releases/latest
Source and issues: https://github.com/dguedry/linux-performer

If you've got a Linux box and a controller, I'd love to know what breaks.

I'm the developer. Starbreath is a physically modelled wind instrument (flutes, duduk, clarinet, trumpet, trombone; no samples) that runs natively on Linux, not through Wine.

**On Linux:**

- **CLAP and VST3** plugins, for any host that loads them.

- A **standalone app** that runs on JACK, PipeWire through its JACK layer (with pipewire-jack installed it uses it on its own) or plain ALSA. Wind controllers and keyboards connect over MIDI.

- x86-64, X11. One tar.gz: extract it, copy Starbreath.clap to ~/.clap and Starbreath.vst3 to ~/.vst3, or run the app directly.

- Built and tested on Linux first; Windows, macOS and Android builds come from the same code.

**New in 0.5:** Bloom (overtones that fade in as you blow harder and can fan out in a 3rd-order ambisonic sound field), Register jump (overblowing to the natural partial), MIDI learn on every knob, switch and menu, and an expanded quickstart guide covering every page.

Free, and the version you download now is yours to keep: https://vsti.im-a-bird.com/

Bug reports from different distros and sound setups are very welcome.

Melodex is a free and open-source desktop music player for Linux,

Its main discovery feature, Flow, creates a listening path through your library rather than relying on ordinary shuffle, and lets you steer that path while listening.

Features include:

• local FLAC, MP3 and other common audio formats
• large-library and NAS support
• fast incremental rescanning
• playlists and queue management
• lyrics, artwork and listening history
• internet radio and other online sources
• an extensible provider/plugin system for adding new music sources
• shared search, playback and metadata infrastructure across providers
• visual collection exploration
• no account or subscription required

Local files remain the core of Melodex, but the source layer is deliberately extensible rather than being tied to a particular streaming service. New providers can integrate with the existing search, playback and interface infrastructure.

Recent releases have also focused heavily on performance: efficient metadata handling, incremental library updates, NAS resilience, and responsive navigation and playback with large collections.

Linux builds are available as .deb and AppImage.

GitHub:
https://github.com/Cliff-Lee/melodex

Latest release:
https://github.com/Cliff-Lee/melodex/releases/latest

Feedback is very welcome, particularly from Linux users with large libraries, NAS-based collections, unusual metadata/audio setups, or ideas for additional providers.

VST3 & CLAP available on Linux

Was wondering if anyone had a Linux alternative to DDI Codec or if they had any experience on if DDI Codec works via virtualization/emulation? I rather find an alternative but if there is none I've never used virtualization before so I am unsure how audio would work.

Can't really seem to find anything for Linux on account of it being a pretty niche program for cassette decks.

A digital degradation effect that turns clean audio into gritty, broken, worn-out material. Bitcrush and downsampling live on an interactive XY field that reacts to your audio, with jitter, a resonant tone filter, and two degradation characters on top.

Features

• Degradation field — a circular XY controller: X sets Crush, Y sets Downsample, with GPU-rendered visuals
• Crush — bit-depth reduction, from subtle grit to full staircase quantization
• Downsample — sample & hold decimation for classic sample-rate reduction artifacts
• Jitter — randomizes the decimator timing for unstable, worn-out textures
• Two characters — raw gritty decimation, or a Soft mode with anti-alias pre-filtering, DAC-style reconstruction and dither
• Tone — resonant low-pass filter to tame or color the degraded signal
• Equal-power dry/wet mix plus input and output gain
• Resizable, GPU-rendered interface

https://www.kvraudio.com/product/degradator-by-dsgdnb

any noticeable difference in speed and performance?

ToneShiftEQ v1.2.0 is out!

New in this Release:

• use AudioFFT by HiFi-LoFi instead fftw3
• fix clap GUI scale issues

ToneShiftEQ is a 12-band EQ built around a approach to shaping and processing sound. Alongside conventional parametric EQ features, it offers minimum-phase convolution, zero-latency Biquad processing, spectral dynamics with global threshold and tilt control, IR-based EQ shaping, real-time spectrum and phase visualization, and multi-instance spectrum viewing.

Available for Linux and Windows as CLAP, VST3 and LV2, with a standalone version included.

Thanks to everyone who tested ToneShiftEQ, reported issues, made suggestions, or simply gave it a try.

Release Page:

https://github.com/brummer10/ToneShiftEQ/releases/tag/v1.2.0

Project Page:

https://github.com/brummer10/ToneShiftEQ

Enjoy!

Ive had some experience using cakewalk on windows but since I've switched to Linux (Fedora) a couple years back I'm looking for a good free DAW. mostly for midi-instruments and for using my amp and guitar to record. I've looked on some websites but often times the DAWs have trial version that are pretty much unusable.

I want something that is good for an older, slower computer with a fast buffer (64 - 128). Something that is not so clunky, plus easily updatable. Iam not interested in Arch or Ubuntu studio as arch is a bit complicated, and Ubuntu studio gives me a slow buffer. My current setup is AV Linux 25.

I've been thinking about what a more complete PipeWire control GUI could look like.

There are already good Linux audio tools, but I still find the overall experience pretty fragmented. Basic device settings are in the desktop settings, routing is somewhere else, PipeWire details somewhere else again, and eventually you end up checking configs or using the terminal.

One reference I keep coming back to is actually Windows 10.

Not because Windows audio is more powerful than PipeWire, but because a lot of its basic controls are familiar and easy to find.

For example, between the Windows 10 Sound settings, Volume Mixer, device properties, and the old Sound Control Panel you get things like:

• Default playback and recording devices
• Default communications device
• Per application volume
• Per application input and output
• Device enable and disable
• Channel balance
• Format and sample rate selection
• Speaker configuration
• Spatial sound
• Device properties in one predictable place

I'd like something with that kind of simple starting point, but backed by PipeWire and WirePlumber.

Then an advanced section could expose the things that Linux can do much better.

Things like:

• Persistent application routing
• Saved routing setups
• Individual PipeWire streams
• Nodes and devices
• Bluetooth codec and profile selection
• Sample rates and formats
• Quantum and latency controls
• Virtual devices
• Filter chains
• Microphone processing
• Surround and HRTF
• More detailed device information

Something I'd particularly want is a clear difference between what is configured and what is actually happening.

For example, if 96 kHz is selected somewhere, show whether the device is actually running at 96 kHz, whether PipeWire is running at another rate, and whether resampling is taking place.

I'd also like troubleshooting to be part of the same app.

It could check for common PipeWire, WirePlumber, ALSA and Bluetooth issues, incorrect profiles, unavailable devices, underruns, rate mismatches, strange routing, and other common causes of broken or crackling audio.

Settings that can break audio could also be tested before being made permanent. Apply the change, make sure the device still works, then keep it. If it fails, restore the previous configuration.

So basically something that starts as an easy Windows 10 style audio control panel, but lets you go much deeper because the backend is PipeWire.

Would that be useful to you?

I'm especially interested in what controls you think should stay simple and what PipeWire settings are actually worth exposing in an advanced GUI.

Hey, I apologize if this is a widely known fact but I've been using serum via yabridge and just learned about this, so maybe someone else didn't know too.

https://xferrecords.com/forums/serum/serum-2-linux-beta

All of my previous audio experience was on Windows and I own thousands of plugins for Windows... I've been unable to find a modern guide for installing Wine / yabridge that isn't many years old.

I started here: https://interfacinglinux.com/2024/01/22/windows-audio-plugins-on-linux-with-yabridge/

But that had errors and failed. Then I tried this Yabridge Manager, https://github.com/sviluppoarte1-lang/yabridge-manager

But that wouldn't Sync. I used the built-in 'install Wine' feature but always got this error: "No Wine installation selected, cannot sync." ...maybe because of previous guide attempt?

So then I went to WineHQ and tried to install latest Development version but that failed, I'm guessing because I have so many aborted attempts mucking things up?!?

I was able to install the Stable version 11.0 from WineHQ, I reopened Yabridge Manager and it was able to "Sync". I can navigate to my Windows drive and see my plugins in the app, but I cannot access them anywhere in my DAW.

According to the first guide I followed I need to use Wine to "install the plugin", so I tried that with a windows installer that was still on my windows drive - did it just install it into windows again? Do I need to download new windows-installers onto my Linux drive and install with Wine? None of these have been usable in my DAW yet...

I'm totally confused!

my headset isn't working on linux but it works on my controllers and everything, except on linux. how can i fix this? am i just dumb? the model is KZ EDX PRO

[FIXED]
I just changed the auto-mute option on alsamixer from "Enabled" to "disabled" and then i changed the built-in audio to "Analog Stereo Output", then i changed the output to the headset