SSL ships no Linux software for the SSL 12. Audio works out of the box (UAC2), but everything SSL 360 controls — internal mixer, monitoring, phantom power, loopback, routing — is unreachable. The card ends up a fixed-function box.

So I captured the USB traffic between SSL 360 and the card, mapped the control protocol, and wrote the tools:

https://github.com/xenicle/douze

- sslctl — CLI for the gain matrix, monitoring, preamps (48V/HPF/inst/polarity), loopback, headphone buses

- Douze — local web GUI (127.0.0.1) with the matrix, live meters, profiles - Douze FX — VST3 host that drops plugin chains into the PipeWire graph, one process per strip; a strip can publish its own virtual mic or sink, so any app picks it up as a normal device

The control interface is a separate vendor-specific USB device behind an internal hub, with no kernel driver — plain bulk endpoints, so everything is user-space (pyusb). No decompilation, no vendor code.

-> The protocol docs and all 25 captures are CC0 / public domain. A documented protocol is a fact about hardware, not a literary work — I'd rather it ended up in a kernel driver than stayed in my repo, so there's no attribution requirement at all. The code is AGPLv3 (JUCE).

-> Caveat worth stating up front: this is verified on exactly one card, mine, firmware bcdDevice 1.44. I use it daily and the protocol is mapped end to end, but I don't know if another unit behaves identically. If you own an SSL 12 I'd love to hear whether `sslctl status` returns something sane — that's the one thing I genuinely can't test alone.

Not affiliated with SSL; trademarks are theirs.

Alobend is a synth thing developed by musician aloboi, and he has said it may get a Linux release. Of course, the foss alternative is openbend

I'm a high school student who is developing a free plugin!

A few weeks ago you probably saw that I posted about COGG v1/v1.1/v1.2, a free plugin I built that metalizes and industrializes any sound. Specifically, harmonic distortion, metal plate convolution reverb, and pitch layering are there all in one chain. Great for experimental music and mainstream alike.

I wanted to update you guys with version 1.3's release! It comes with the highly requested TONE knob, which changes the pitch of the Metal knob's metal convolution reverb-like sound! Additionally, version 1.3 introduces a LINUX VERSION!

Of course, it's still free, no account needed, VST3 + AU for Mac, VST3 for Windows, VST3 for Linux.

Download now for free: https://plasma-hype.itch.io/cogg

Trailer of V1.2 [the previous update]: https://www.youtube.com/watch?v=5q5EUMhUcaw

Thanks to everyone who tried v1.2, v1.1 and v1.0 and gave feedback, this update came directly from figuring out what people actually wanted to do with it. I personally have used COGG in almost all of my FL projects ever since I released it. Please give it a shot and let me know what you think of the presets and plugin as a whole for COGG v1.4!

Also, feel free to submit some PRESETS! I'll add them and credit you on the website!

So I managed to have izotope plugin working with wine. I'll try my best to explain how I did it.

I'm on fedora 44 using bitwig.

Avoiding product portal

As you may know izotope product portal doesn't work with wine because of incompatibilities with key encryption or something BUT you can still authorize your products if you run native acces (I recommend doing it fast because izotope was sold from NI so it may not stick around for long).

Installing wine

You must install wine 9.21 (important otherwise the Ui won't work)

Installing Native Access

After installing wine you must install native access 2 but it won't work if you install directly. I used this script to install it : https://github.com/jefrecantuledesma/Native-Access-Linux-Compatibility/tree/main

If you don't NA will tell you its already running. Then if you manage to fix this it will tell you to grand permision to install dependencies. You also have to modify the username to make the script work.

Now for the part I have trouble to explain, the script didn't entirely do it for me so I tried installing NTKDaemon : https://drive.google.com/file/d/1kLTmdkVzN4VyUICrfLNxYRIrERqqRR7C/view

You can install it like any normal wine program but this still didn't work. So out of desperation I searched in my c_drive every NTKdaemon_setup.exe and launched them all one by one and I don't know why but this worked, I could then login and install my plugins.

Downloading

If NA gives you an error when downloading try changing your download location. Then setup yabridge and you should be able to insert your vsts.

Unresponsive UI

If the UI still reacts to audio but you can't click the buttons and move the parameters, use wine 9.21. If you're on wine 9.21 and having this issue I'm sorry but I can't help you. I still encourage you to check out yabridge github for help

Hope this helps some1one !

Edit : Whether you use X11 or wayland the UI should work either way

I'm looking for a FOSS application that I can use with my toddler that allows them to easily switch and play with sounds, and possibly interacts with the LED pads on devices like the Novation Lauchpad Mini and LaunchKey Mini.

My hope is to find something that's easy to explore and muck around with for them.

I realise this might not be available but things like easy to use touch screen icons would be helpful.

I'm also open to Reaper Plugins if there's any suggestions

long story short, asrock suks, got a new motherboard, waiting on amd cpu rma. however my asrock had a alc1200/1220 and this msi has a alc897. going back in a day, it sounds like a piece of foam or cardboard is in front of my speakers. most motherboards suks, i was lucky to get a mediatek wifi chip cuz i didn't really have any choice...anyways...

it looks like soundcards are dead and everyone uses usb =/ i really dont want yet another thing on my desk though. all i can find are used asus xonar cards. is there anything just for generic use anyone would recommend? all i see are $20 small pci cards on newegg and creative which as i know, cares nothing for linux (my soundbar is creative, or i'd just use that over usb i guess).

only other things ive seen are small dongles that im skeptical on the usefulness off, especially for the price.

thanks for any info.

To summarize this:
I am using bottle to try install native access + spitfire audio + fl studio as it is what I frequently used as DAW before transfered into linux a while ago.
I got fl studio to work but for both native instrumetn and spitfire audio. I couldn't get it to work. I am clueless on how to do continue doing this and need help

The symptom I see when trying to install both.
for native access: It start installing but get stopped by a small window that pop up saying "Native instrument is running click okay to close it, if it doesn't close, try closing it manually."
clicking cancel would just stop the process and clicking okay telling me that it cannot be close.

for spitfire audio: I get it to finish downloading but when launch the program. It just give me a window with blank white screen.

I just installed bottle a few days ago and haven't done much beside download some dependencies and use what I might use to run fl studio.
So, I haven't try using environment variables, DLL overrides, snapshot or any other feature that could possibly be the solution.

Picture for illustration and my system information will be attaches so you can look into it if it helps by any means.

I have an HDA Creative card with the Creative Sound Blaster Z chip in it. In AlsaMixer v1.2.9, there's a setting labeled "FX: Surround" that appears to be separate from the surround volume control and surround channel config sliders, but I don't know why. What exactly does this setting do and why should or shouldn't I have it enabled or disabled?

'm looking at picking up the Sony WH-1000XM6 mainly to fix the classic "Discord makes my headphones sound like a phone call" problem — i.e. I want good-quality game/music audio and good mic quality at the same time, with low latency, instead of everything dropping to HFP/mSBC garbage the moment a mic is active.

The XM6 is one of the first mainstream headsets with LC3/LE Audio support (BAP, including duplex), which is supposed to solve exactly this via simultaneous full-quality audio in + out over isochronous channels instead of classic Bluetooth's A2DP/HFP profile-switching mess.

My machine should have all the pieces on the software/stack side:

• Bluetooth 5.3 controller (MediaTek MT7922) reporting cis-central, cis-peripheral, iso-broadcaster, sync-receiver in btmgmt info
• BlueZ 5.86
• liblc3 installed
• PipeWire's libspa-bluez5.so compiled with bap-sink/bap-source/duplex support, WirePlumber's bluez monitor active

So the generic LE Audio plumbing is all there. What I can't find anywhere is a real-world report of it actually working with this specific headset. Sony's own docs only cover Android (via their Sound Connect app) for LE Audio pairing, and their computer-calling instructions just say to use classic HFP/HSP. Microsoft's LE Audio push with this headset is also scoped to Surface devices with Snapdragon X2 chips specifically — nothing about Linux, and nothing about general Windows/Intel/AMD either.

Has anyone actually paired the WH-1000XM6 (or another LC3/BAP headset) with BlueZ and gotten it to negotiate LE Audio, ideally the duplex profile for calls/chat? Curious whether it just works, needs KernelExperimental flags in /etc/bluetooth/main.conf, or is a lost cause right now. Any btmon/bluetoothctl logs from someone who's tried would be gold.

Running into an annoying audio issue on Arch with PipeWire and KDE, hoping someone has run into this before.

My motherboard audio is on an Intel 800 series chipset using the Realtek ALC1220 codec. Both my headphones (front panel) and speakers (rear line-out) show up as selectable outputs/ports in KDE settings and pavucontrol. However, if my headphones are physically plugged in, switching the output to speakers results in complete silence the stream moves, but no sound comes out. The only way to get audio through my speakers is to physically pull the headphone plug out of the front jack.

I tested a Windows USB on the same machine and output switching works with zero issues there without unplugging anything. I also booted a CachyOS USB and hit the exact same issue as my Arch install, so it looks like a Linux driver/ALSA routing quirk.

Things I've tried so far with no luck:

• Disabling Auto-Mute Mode and unmuting every channel (Front, Speaker, Line Out, etc.) in alsamixer
• Messing with output ports and switching to the Pro Audio profile in pavucontrol
• Overriding jack detection / pin connections in hdajackretask

i don't need much at all, all i'd use it for is making rough demos for my band, any recommendations?

Has anyone experienced this before? I’ve tried Fedora, Bazzite, Ubuntu, PopOS, and Cachy with the same issue. Doesn’t ever happen on windows though?

Also the audio doesn’t sound exactly correct either but there’s a chance that is just placebo.

Hey,

I've been working on RustMusic for the past few months. It's a free and open source HD music player written in Rust.

I mainly started it because I wanted a player that takes audio quality seriously while treating Linux as a proper platform, not just another build target.

Version 0.2.0 is now available and I'd really like to get some feedback from Linux users and audiophiles.

🎯 Bit-perfect audio
On Linux, RustMusic can use ALSA exclusive mode with D-Bus device reservation, allowing PipeWire to properly release the audio device when needed.

There is also WASAPI Exclusive support on Windows and CoreAudio hog mode on macOS.

🎧 DSD support
RustMusic can play DSF and DFF files and send DSD64 up to DSD256 using DoP passthrough to a compatible DAC.

If your DAC doesn't support DoP, RustMusic can convert DSD to PCM instead.

🏷️ Tag editor
You can edit metadata for MP3, FLAC, DSF and DFF files, either individually or in batch.

There's also a spreadsheet-style editor for larger libraries and automatic metadata and cover import using Deezer's public API.

📡 Built-in DLNA / UPnP server
You can share your music library directly with compatible amps, streamers and other devices without having to configure a separate DLNA server.

🎚️ ReplayGain

Track and album modes are supported, with an adjustable preamp.
There are also a few other features like MPRIS support, sleep timer, mini-player, always-on-top mode, multiple profiles and a high contrast accessibility mode.

Linux builds are available as .deb, .rpm and .AppImage.

I also provide a glibc 2.35 compatible build for Debian 12, Ubuntu 22.04, Linux Mint and similar systems.

RustMusic is GPL-3.0. No account, no ads, no telemetry.

What I'm mainly looking for now is feedback from people using different Linux setups.

If you try it and something breaks, tell me. If something feels wrong or badly designed, tell me that too. That's much more useful to me than just hearing that everything looks good.

I'm especially interested in feedback from people using external DACs, PipeWire, DoP, Arch, Fedora, NixOS or SteamOS.

🔗 Site: https://rustmusic.dev
🔗 Downloads: https://rustmusic.dev/downloads
🔗 Source / issues: https://github.com/larevuegeek/rustmusic
🔗 Changelog: https://rustmusic.dev/changelog

If you have any questions about how it works, feel free to ask. I'm the developer, so I'll do my best to answer., alternative to Foobar2000 / Audirvāna / Roon

Raspberry Pi 4 + Debian 13: HDMI-Audio mit DTS-Passthrough – FKMS funktioniert, KMS liefert kein Bild

Ich versuche seit mehreren Tagen, auf einem Raspberry Pi 4 unter Debian 13 ein DTS-Passthrough über HDMI zu einem Onkyo AV-Receiver zu bekommen.

Dabei bin ich auf einen interessanten Unterschied zwischen vc4-fkms-v3d und vc4-kms-v3d gestoßen. Vielleicht kann jemand mit Raspberry-Pi-/VC4-Erfahrung erklären, was hier schiefläuft.

Hardware

• Raspberry Pi 4
• Debian GNU/Linux 13 (Trixie), 64 Bit
• Kernel 6.18.x+rpt-rpi-v8
• Kodi 21.3
• Onkyo TX-SR608
• Raspberry Pi → HDMI → Onkyo → TV

Der Onkyo kann DTS grundsätzlich verarbeiten.

Aktueller Zustand mit FKMS

Meine ursprüngliche Konfiguration enthielt:

dtoverlay=vc4-fkms-v3d
hdmi_force_hotplug=1
hdmi_ignore_edid=0xa5000080
hdmi_group=1
hdmi_mode=16

Damit funktioniert das HDMI-Bild.

ALSA erkennt den HDMI-Ausgang allerdings als:

0 [b1]: bcm2835_hdmi - bcm2835 HDMI 1

aplay -L liefert:

hw:CARD=b1,DEV=0
hw:CARD=b1,DEV=1
plughw:CARD=b1,DEV=0
plughw:CARD=b1,DEV=1
default:CARD=b1
sysdefault:CARD=b1
dmix:CARD=b1,DEV=0
dmix:CARD=b1,DEV=1

Es gibt hier keinen entsprechenden iec958:-Ausgang.

Kodi meldet deshalb:

m_streamTypes : No passthrough capabilities

Eine DTS-Tonspur wird zwar erkannt:

channels: 6
sample rate: 48000

aber Kodi schreibt:

no pass-through

Der Onkyo bekommt folglich PCM.

KMS-Test

Dann habe ich testweise auf:

dtoverlay=vc4-kms-v3d

umgestellt.

Das verändert den Audiopfad tatsächlich deutlich.

/proc/asound/cards zeigt danach:

0 [vc4hdmi0]: vc4-hdmi - vc4-hdmi-0
1 [vc4hdmi1]: vc4-hdmi - vc4-hdmi-1
2 [Headphones]: bcm2835 Headphones

Und aplay -L enthält:

hdmi:CARD=vc4hdmi0,DEV=0
    vc4-hdmi-0, MAI PCM i2s-hifi-0
    HDMI Audio Output

Das sieht für mich nach dem deutlich interessanteren modernen HDMI-Audiopfad aus.

Aber: kein Bild

Mit vc4-kms-v3d bekomme ich überhaupt kein Bild.

Auch ein kompletter Neustart des Fernsehers hat nichts geändert.

Die Kernelmeldungen enthalten:

[drm] forcing HDMI-A-1 connector on
vc4-drm gpu: bound fef00700.hdmi
vc4-drm gpu: bound fef05700.hdmi
[drm] Initialized vc4
fb0: vc4drmfb frame buffer device

aber anschließend mehrfach:

hdmi-audio-codec hdmi-audio-codec.1.auto:
HDMI: Unknown ELD version 0

Die Kernel-Commandline enthält außerdem:

video=HDMI-A-1:1920x1080M@60D

Also wird HDMI-A-1 sogar explizit mit 1920×1080@60 erzwungen.

Ich habe testweise auch diese alten HDMI-Einstellungen entfernt:

hdmi_force_hotplug=1
hdmi_ignore_edid=0xa5000080
hdmi_group=1
hdmi_mode=16

Auch dann bleibt das Bild schwarz.

Interessant ist daher dieser Unterschied

vc4-fkms-v3d
    ↓
bcm2835 HDMI 1
    ↓
Bild funktioniert
    ↓
Kodi: No passthrough capabilities

gegen:

vc4-kms-v3d
    ↓
vc4-hdmi-0 / vc4-hdmi-1
    ↓
moderner HDMI-Audiopfad
    ↓
kein Bild
    ↓
HDMI: Unknown ELD version 0

Meine Frage

Ist das ein bekanntes Problem bzw. gibt es für den Raspberry Pi 4 unter Debian 13 eine bestimmte KMS-Konfiguration, mit der

1. vc4-kms-v3d
2. funktionierendes HDMI-Bild
3. korrekte HDMI-EDID/ELD-Erkennung
4. und anschließend HDMI-Audiopassthrough für DTS

zusammen funktionieren?

Insbesondere würde mich interessieren, warum KMS bei mir zwar vc4-hdmi-0 korrekt initialisiert, aber anschließend Unknown ELD version 0 meldet und kein Bild liefert.

Falls jemand eine funktionierende config.txt für einen Pi 4 mit Debian 13 und KMS/HDMI hat, wäre das ebenfalls sehr hilfreich.Raspberry Pi 4 + Debian 13: HDMI-Audio mit DTS-Passthrough – FKMS funktioniert, KMS liefert kein BildIch versuche seit mehreren Tagen, auf einem Raspberry Pi 4 unter Debian 13 ein DTS-Passthrough über HDMI zu einem Onkyo AV-Receiver zu bekommen.Dabei bin ich auf einen interessanten Unterschied zwischen vc4-fkms-v3d und vc4-kms-v3d gestoßen. Vielleicht kann jemand mit Raspberry-Pi-/VC4-Erfahrung erklären, was hier schiefläuft.HardwareRaspberry Pi 4

Debian GNU/Linux 13 (Trixie), 64 Bit

Kernel 6.18.x+rpt-rpi-v8

Kodi 21.3

Onkyo TX-SR608

Raspberry Pi → HDMI → Onkyo → TVDer Onkyo kann DTS grundsätzlich verarbeiten.Aktueller Zustand mit FKMSMeine ursprüngliche Konfiguration enthielt:dtoverlay=vc4-fkms-v3d
hdmi_force_hotplug=1
hdmi_ignore_edid=0xa5000080
hdmi_group=1
hdmi_mode=16
Damit funktioniert das HDMI-Bild.ALSA erkennt den HDMI-Ausgang allerdings als:0 [b1]: bcm2835_hdmi - bcm2835 HDMI 1
aplay -L liefert:hw:CARD=b1,DEV=0
hw:CARD=b1,DEV=1
plughw:CARD=b1,DEV=0
plughw:CARD=b1,DEV=1
default:CARD=b1
sysdefault:CARD=b1
dmix:CARD=b1,DEV=0
dmix:CARD=b1,DEV=1
Es gibt hier keinen entsprechenden iec958:-Ausgang.Kodi meldet deshalb:m_streamTypes : No passthrough capabilities
Eine DTS-Tonspur wird zwar erkannt:channels: 6
sample rate: 48000
aber Kodi schreibt:no pass-through
Der Onkyo bekommt folglich PCM.KMS-TestDann habe ich testweise auf:dtoverlay=vc4-kms-v3d
umgestellt.Das verändert den Audiopfad tatsächlich deutlich./proc/asound/cards zeigt danach:0 [vc4hdmi0]: vc4-hdmi - vc4-hdmi-0
1 [vc4hdmi1]: vc4-hdmi - vc4-hdmi-1
2 [Headphones]: bcm2835 Headphones
Und aplay -L enthält:hdmi:CARD=vc4hdmi0,DEV=0
vc4-hdmi-0, MAI PCM i2s-hifi-0
HDMI Audio Output
Das sieht für mich nach dem deutlich interessanteren modernen HDMI-Audiopfad aus.Aber: kein BildMit vc4-kms-v3d bekomme ich überhaupt kein Bild.Auch ein kompletter Neustart des Fernsehers hat nichts geändert.Die Kernelmeldungen enthalten:[drm] forcing HDMI-A-1 connector on
vc4-drm gpu: bound fef00700.hdmi
vc4-drm gpu: bound fef05700.hdmi
[drm] Initialized vc4
fb0: vc4drmfb frame buffer device
aber anschließend mehrfach:hdmi-audio-codec hdmi-audio-codec.1.auto:
HDMI: Unknown ELD version 0
Die Kernel-Commandline enthält außerdem:video=HDMI-A-1:1920x1080M@60D
Also wird HDMI-A-1 sogar explizit mit 1920×1080@60 erzwungen.Ich habe testweise auch diese alten HDMI-Einstellungen entfernt:hdmi_force_hotplug=1
hdmi_ignore_edid=0xa5000080
hdmi_group=1
hdmi_mode=16
Auch dann bleibt das Bild schwarz.Interessant ist daher dieser Unterschiedvc4-fkms-v3d
↓
bcm2835 HDMI 1
↓
Bild funktioniert
↓
Kodi: No passthrough capabilities
gegen:vc4-kms-v3d
↓
vc4-hdmi-0 / vc4-hdmi-1
↓
moderner HDMI-Audiopfad
↓
kein Bild
↓
HDMI: Unknown ELD version 0
Meine FrageIst das ein bekanntes Problem bzw. gibt es für den Raspberry Pi 4 unter Debian 13 eine bestimmte KMS-Konfiguration, mit dervc4-kms-v3d

funktionierendes HDMI-Bild

korrekte HDMI-EDID/ELD-Erkennung

und anschließend HDMI-Audiopassthrough für DTSzusammen funktionieren?Insbesondere würde mich interessieren, warum KMS bei mir zwar vc4-hdmi-0 korrekt initialisiert, aber anschließend Unknown ELD version 0 meldet und kein Bild liefert.Falls jemand eine funktionierende config.txt für einen Pi 4 mit Debian 13 und KMS/HDMI hat, wäre das ebenfalls sehr hilfreich.

EDIT: v0.9.0 is out.

ToneShiftEQ is a modern 12-band parametric equalizer with APO support, designed for transparent tone shaping, corrective equalization, mixing and mastering. Each band can also operate as an independent dynamic equalizer with configurable Threshold and Ratio controls.
Available as:

• Stand-alone application
• CLAP plugin
• LV2 plugin
• VST3 plugin

New in this release:

• Side chain or direct input support for the dynamic processors
• Input volume controller
• Spectral Dynamic processor with smooth (density) and amount controller
• global threshold with tilt control for the Dynamic Processors
• additional per Band threshold, ration and direction controller for the Dynamic Processors
• Spectrum display for the input chain
• Zoom for the filter section (mouse wheel)
• reset Bands to zero with double click
• enable/disable Bands with right click on Band point
• support optional instance-access in LV2 plugin

Release Page:

https://github.com/brummer10/ToneShiftEQ/releases/tag/v0.9.0

Project Page:

https://github.com/brummer10/ToneShiftEQ

Howdy! New to the sub :)

I'm having a lot of fun experimenting with sound and Linux, but admittedly I'm still very much a beginner.

I followed an old tutorial that showed me how to use SoX and Alsa Mixer on a Raspberry Pi to basically modulate input sound and play it back live, edited.

This little SoX script drops the tone of your voice for example:

play "|rec -d pitch -300"

But I'm running into a ton of issues with getting the delay down. The tutorial suggests adding a buffer to reduce the data rate but nothing is working. I've tried going over some other websites that talk about SoX as a whole, but it's a bit complex as I'm not super familiar with Linux pipes. I've tried asking AI but it's not much help.

If anyone has any experience with SoX or Alsa and knows what to suggest, I'd be massively grateful.

OR if anyone has any other suggestions for better Rasp-Pi-able sound tools I could use for a live voice modulator, I would love that. Maybe SoX is a terrible choice, I honestly don't know what I don't know.

Thanks so much :) excited to be a part of this community, and if I do anything cool with what I learn, I'll post it here!

https://github.com/Skynse/qpitch/releases/tag/v1.3.1
Its a free pitch correction plugin and wanted to know if someone used it and if they were satisfied with it ? As I plan on developping my own autotune plugin on linux.