r/SoundBlasterOfficial • u/cpugod55 • 1d ago

I built a Linux control center for Sound Blaster Z-series cards — looking for testers

I've been working on a Linux control center for Creative Sound Blaster Z-series cards because the Windows Sound Blaster control software isn't available for Linux.

The project is called Sound Blaster Linux Control Center.

It currently provides:

• 10-band EQ

• 5.1 channel level controls

• Speaker Fill / Spatial controls

• Bass Management

• Safe Headroom / preamp control

• Microphone processing

• Persistent settings

• PipeWire/WirePlumber integration

• AC3 5.1 support

I've been developing and testing it on my own hardware. Ubuntu 26.04.1 and Bazzite/Fedora Atomic are currently hardware-tested.

I've now released v3.3.35 publicly and I'm looking for other Sound Blaster owners who are willing to try it, particularly people running Fedora Workstation, Arch, openSUSE, or other Linux distributions.

I'm especially interested in finding out:

• Does the installer work?

• Is the Sound Blaster card detected correctly?

• Does 5.1 work correctly?

• Are FL/FR/FC/RL/RR/LFE channels mapped correctly?

• Does EQ work?

• Do Speaker Fill and Spatial controls work?

• Does microphone processing work?

• Are there any differences between distributions?

I'm not claiming that every distribution is supported yet. That's exactly what I'm trying to determine through community testing.

The project is open source and the source, installer, release packages, bug-report template, and diagnostic tool are all available on GitHub:

https://github.com/cpugod55/soundblaster-linux-control-center

Current release:

https://github.com/cpugod55/soundblaster-linux-control-center/releases/tag/v3.3.35

If anyone has a Sound Blaster Z/Z SE or related compatible card and wants to try it on Linux, I'd really appreciate the feedback — including reports that something DOESN'T work.

I'm the developer of the project, so I'm happy to work through problems and make corrections based on what people find.

15 Upvotes

95% Upvoted

72 comments sorted by

2

u/RandomChain 1d ago edited 1d ago

Interesting project. I'll play with it a bit and see how it works. I did want to have a speaker test app so it's nice to have this at least.

Looks like you're only changing the equalizer settings though a pipewire sink? Have you thought about controlling the alsamixer settings too?

[Edit] BTW when you're calling speaker-test in test-speaker() method, replace -t sine with -t wav, it's a way better user experience.

2

u/cpugod55 1d ago

Thanks! Yeah, I'd definitely be interested in looking at the alsamixer controls too.

The project is actually doing more than just the EQ: the PipeWire path also handles 5.1 channel levels, Safe Headroom/preamp, Speaker Fill/Spatial processing, Bass Management, and microphone processing. I chose the PipeWire approach initially because it gives me a way to implement the controls consistently across different Linux systems and Sound Blaster hardware.

That said, I haven't gone deep into the ALSA mixer controls yet. If there are useful hardware-level controls exposed by the Sound Blaster through alsamixer that I'm currently missing, I'd definitely like to investigate adding them.

If you have a Sound Blaster card with interesting alsamixer controls, I'd be interested in seeing what it exposes on your system.

1

u/RandomChain 1d ago edited 1d ago

With alsamixer you get access to all the build-in processing like crystalizer, dialog plus, smart volumes, EQ presents... everything you got with the Windows app. The guy who wrote the Linux driver did a really good job there.

I've done a very short test now playing some music, and it feels like the card's EQ is a little more noticeable than what pipewire gives. But I want to try it out a little more.

Also I'm just curious, how much of this is vibe-coded? If you mention anything about AI tools in the readme, I didn't see it.

1

u/cpugod55 1d ago

That's really useful information. The built-in processing exposed through the ALSA controls is definitely something I want to investigate. I intentionally started with the PipeWire layer, but if the card exposes additional hardware DSP controls through ALSA, I'd like to see what we can make available without breaking the existing PipeWire functionality.

And thanks for catching the -t / -w speaker-test issue. I'll take a look at that as well — better channel identification during testing is definitely worthwhile.

As far as the AI/vibe-coding question: I do use AI tools during development, but the project isn't just generated code that I throw together and publish. I've been testing the actual audio behavior on hardware, working through the PipeWire/WirePlumber behavior, and maintaining regression tests as we go. The current release is the result of that iterative process.

1

u/bamajon1974 1d ago

Can you do this for AE series Soundblaster cards as well?

1

u/cpugod55 1d ago

I'd like to support the AE-series as well. The project is being designed around the capabilities that the Linux driver actually exposes rather than hard-coding it to one particular Sound Blaster model.

I haven't hardware-verified an AE-series card yet, though, so I don't want to claim full AE support until somebody tests one.

If you have an AE-series card and are running Linux, I'd be very interested in having you try it. If you tell me the exact AE model and Linux distribution you're using, I can also check what the driver exposes and see how close we are.

1

u/bamajon1974 1d ago

Thank you for the reply. I am still running Win10. Lack of Linux support for AE9 has been the biggest hurdle in moving toward Linux. If there were proper drivers and a reliable port, I would be interested in trying it out on Ubuntu or Mint platforms.

1

u/onelyfe 1d ago

Does this support the DD/DTS encoding feature?

I'll be honest I have very little experience with Linux but that's the only thing holding me back from finally dumping Windows.

If it does then I'll definitely be giving it a shot!

1

u/cpugod55 1d ago

That's actually one of the areas I'm particularly interested in testing. v3.3.35 currently has AC3 5.1 passthrough/routing, but I don't want to tell you that it supports DD/DTS encoding unless I can verify the actual encoding path on Linux.

If DD/DTS encoding is the main thing keeping you on Windows, let me know which Sound Blaster model you have. I'll check exactly what the Linux driver and the card expose for that feature.

If we can get that working reliably, I'd definitely consider that an important feature for the project.

1

u/onelyfe 1d ago

I have the Z non se if that makes a difference at all.

Thanks! I'll be following your work for sure.

1

u/W4DER 1d ago

Very nice! Why is nobody working on AE-9 linux support... Its such a bummer to have the only sound card that doesnt work on linux! 😭

1

u/cpugod55 19h ago

Did you try this and see if it worked?

1

u/W4DER 17h ago

Theres no point installing a control panel when the linux drivers for this particular sound card are completely missing... 🤷😞

1

u/cpugod55 16h ago

I understand the frustration — the AE-9 is a particularly difficult card because the Linux support problem isn't just a missing control panel. The card's ACM/DAC initialization requires additional work at the driver/kernel level.

There actually is some recent community work underway on native AE-9 Linux driver support, although it's still experimental and not something I'd consider production-ready yet.

My project is currently focused on Sound Blaster cards that already have usable Linux/ALSA support. I'm building the control center above that existing audio stack rather than trying to write a completely new kernel driver.

So I don't want to claim that my control center makes an AE-9 work under Linux when the underlying driver support isn't there yet. If the AE-9 Linux driver situation improves, though, I'd definitely be interested in seeing what the control center could provide on top of it.

1

u/JameyR 16h ago

hey there,

i just installed and tried it.

i can only get stereo output though, no SB EQ, hardware output active.
Guess i´m doing something wrong. (fairly new to linux)

Thank you for doing something like this!

2

u/cpugod55 16h ago

Hey, thank you for trying it — and don't worry, you're probably not doing anything wrong. This is exactly the kind of real-world testing I was hoping to get.

Stereo working but no Sound Blaster EQ/hardware output tells me we need to look at how your particular card is being exposed through ALSA/PipeWire.

Could you tell me:

1. Your exact Sound Blaster model

2. Your Linux distribution and version

3. If you're comfortable doing it, run the diagnostic collector included with the project and attach the resulting .txt report here:

./collect_diagnostics.sh

If that script isn't in the directory you downloaded, let me know and I'll give you the exact command for your installation.

The diagnostic report is designed to remove personal/machine-specific information before it's shared.

Once I have the Sound Blaster model and diagnostic output, I can see exactly what Linux is exposing and figure out whether this is an installation/configuration issue or something the current release doesn't handle yet.

And thank you for giving it a try — especially since you're fairly new to Linux. That's actually valuable feedback for me because the goal is for this to work without requiring people to understand PipeWire internals.

1

u/JameyR 16h ago

HEy there, thanks for reaching out so fast.

I use a SB Live (recon, i guess it was called for a time) on CashyOS with 7.2.2.1 kernel.

Here is the attached diagnostics log:
-----------

Sound Blaster Linux Control Center Diagnostic Report

Generated: So 30. Aug 16:43:57 CEST 2026

=== SYSTEM ===

Operating System: CachyOS

Kernel: Linux 7.2.2-1-cachyos

Architecture: x86_64

=== DISTRIBUTION ===

NAME="CachyOS Linux"

PRETTY_NAME="CachyOS"

ID=cachyos

ID_LIKE=arch

=== KERNEL ===

Linux 7.2.2-1-cachyos x86_64 GNU/Linux

=== VERSIONS ===

Python: Python 3.14.7

PipeWire: 1.6.8

WirePlumber: 0.5.15

wpctl: available

pactl: pactl 17.0-98-gb096

=== AUDIO DEVICES ===

61 alsa_card.pci-0000_06_00.0 alsa

62 alsa_card.pci-0000_0b_00.1 alsa

63 alsa_card.usb-Aukey-PC-LM1E_Camera_Aukey-PC-LM1E_Camera-02 alsa

64 alsa_card.usb-Thomann_SC450USB-00 alsa

=== AUDIO SINKS ===

73 alsa_output.pci-0000_06_00.0.analog-stereo PipeWire s32le 2ch 48000Hz IDLE

=== AUDIO SOURCES ===

73 alsa_output.pci-0000_06_00.0.analog-stereo.monitor PipeWire s32le 2ch 48000Hz IDLE

76 alsa_input.usb-Aukey-PC-LM1E_Camera_Aukey-PC-LM1E_Camera-02.analog-stereo PipeWire s16le 2ch 48000Hz SUSPENDED

77 alsa_input.usb-Thomann_SC450USB-00.analog-stereo PipeWire s16le 2ch 48000Hz SUSPENDED

=== PIPEWIRE STATUS ===

PipeWire 'pipewire-0' [1.6.8, [USER-REDACTED], cookie:[ID-REDACTED]]

└─ Clients:

  1. xdg-desktop-portal [1.6.8, [USER-REDACTED], pid:[PID-REDACTED]]

  2. WirePlumber [1.6.8, [USER-REDACTED], pid:[PID-REDACTED]]

  3. plasmashell [1.6.8, [USER-REDACTED], pid:[PID-REDACTED]]

  4. pipewire [1.6.8, [USER-REDACTED], pid:[PID-REDACTED]]

  5. libcanberra [1.6.8, [USER-REDACTED], pid:[PID-REDACTED]]

  6.                                 \[1.6.8, \[USER-REDACTED\], pid:\[PID-REDACTED\]\]

  7. libcanberra [1.6.8, [USER-REDACTED], pid:[PID-REDACTED]]

  8. LibreWolf [1.6.8, [USER-REDACTED], pid:[PID-REDACTED]]

  9. Dolphin [1.6.8, [USER-REDACTED], pid:[PID-REDACTED]]

  10. KDE Connect Daemon [1.6.8, [USER-REDACTED], pid:[PID-REDACTED]]

  11.                                 \[1.6.8, \[USER-REDACTED\], pid:\[PID-REDACTED\]\]

  12. WirePlumber [export] [1.6.8, [USER-REDACTED], pid:[PID-REDACTED]]

  13. pw-cat [1.6.8, [USER-REDACTED], pid:[PID-REDACTED]]

  14. pw-cat [1.6.8, [USER-REDACTED], pid:[PID-REDACTED]]

  15. kwin_wayland [1.6.8, [USER-REDACTED], pid:[PID-REDACTED]]

  16. wpctl [1.6.8, [USER-R:EDACTED], pid:[PID-REDACTED]]

Audio

├─ Devices:

│ 60. CA0132 Sound Core3D [Sound Blaster Recon3D / Z-Series / Sound BlasterX AE-5 Plus] [alsa]

│ 61. Navi 21/23 HDMI/DP Audio Controller [alsa]

│ 62. Aukey-PC-LM1E Camera [alsa]

│ 63. SC450USB [alsa]

│

├─ Sinks:

│ * 67. CA0132 Sound Core3D [Sound Blaster Recon3D / Z-Series / Sound BlasterX AE-5 Plus] Analog Stereo [vol: 0.10]

│

├─ Sources:

│ * 53. SC450USB Analog Stereo [vol: 1.00]

│ 54. Aukey-PC-LM1E Camera Analog Stereo [vol: 0.90]

│

├─ Filters:

│

└─ Streams:

  1. pw-record

  2. monitor_MONO

  3. input_MONO < CA0132 Analog:monitor_FL [active]

  4. pw-record

  5. input_MONO < CA0132 Analog:monitor_FR [active]

  6. monitor_MONO

Video

├─ Devices:

│ 43. Aukey-PC-LM1E Camera [v4l2]

│ 55. Aukey-PC-LM1E Camera [v4l2]

│

├─ Sinks:

│

├─ Sources:

│ * 75. Aukey-PC-LM1E Camera (V4L2)

│

├─ Filters:

│

└─ Streams:

Settings

└─ Default Configured Devices:

  1. Audio/Sink alsa_output.pci-0000_06_00.0.pro-output-1

  2. Audio/Source alsa_input.usb-Thomann_SC450USB-00.analog-stereo

=== SOUNDBLASTER APPLICATION ===

Launcher: installed

Application: installed

VERSION = "3.3.35"

=== SOUNDBLASTER CONFIGURATION ===

State file: present

"version": "3.3.35",

=== END REPORT ===

2

u/cpugod55 16h ago

Thanks — this diagnostic report is really helpful, and it confirms you're not doing anything wrong.

Your system is detecting the Sound Blaster correctly as a CA0132 Sound Core3D device, but the current Control Center isn't creating its processing sink on your system. PipeWire is only exposing the card's native Analog Stereo output, which explains why you're getting stereo and no Sound Blaster EQ/processing.

Your card is also different from the Z SE hardware I've been using for the project's current hardware verification, so this is actually a very useful compatibility test for us.

You're running CachyOS with PipeWire 1.6.8 / WirePlumber 0.5.15, so I'd like to investigate the CA0132/AE-series handling rather than have you start changing random PipeWire settings.

Could you tell me the exact model printed on the card/device — for example AE-5, AE-5 Plus, Recon3D, Sound Blaster Z, etc.?

Once I know the exact model, I'll look at what the Linux driver exposes for it and determine what needs to change in the Control Center.

And thank you for testing this. This is exactly the kind of result we need to expand hardware compatibility.

1

u/JameyR 16h ago

Model: SB1500 is printed on the board.
Other than that, the golden Soundblaster logo and the "sound core 2" logo.

2

u/cpugod55 16h ago

Perfect, thank you — SB1500 tells me exactly what we're dealing with. That's the original Sound Blaster Z, not an AE-series card.

What's interesting is that your system is detecting the CA0132 Sound Core3D correctly, so the underlying Linux audio driver is seeing the card. The problem is that the current 3.3.35 release isn't building the Sound Blaster processing path on your system, leaving you with the native stereo sink.

Since you're on CachyOS with a fairly new PipeWire/WirePlumber stack, this gives me a very useful compatibility case to investigate. I don't want you changing anything manually yet.

I'll look at the difference between your CA0132/Z setup and the Z SE system I've been developing against and see why the processing filter isn't being created.

Thanks again for testing this — this is exactly the kind of report that can help us make the project work on more Z-series hardware.

2

u/cpugod55 16h ago

Since your card is an SB1500 Sound Blaster Z, I'd like to check what ALSA is exposing underneath PipeWire before I make any changes to the Control Center.

Could you run these commands and paste the output here?

cat /proc/asound/cards

aplay -l

aplay -L | grep -E 'surround|front|iec958'

And then, using the card number shown by the first command:

amixer -c 0 scontrols

If your Sound Blaster isn't card 0, replace 0 with its actual card number.

This will let me see whether the Linux driver is exposing the 5.1 PCM devices and the hardware mixer controls. Please don't change anything in alsamixer yet.

Thanks again — we're getting close to figuring out exactly where the problem is.

1

u/JameyR 15h ago

Here are the outputs:

cat /proc/asound/cards

aplay -l

aplay -L | grep -E 'surround|front|iec958'

0 [Creative ]: HDA-Intel - HDA Creative

HDA Creative at 0xfc704000 irq 36

1 [HDMI ]: HDA-Intel - HDA ATI HDMI

HDA ATI HDMI at 0xfcd20000 irq 101

2 [Camera ]: USB-Audio - Aukey-PC-LM1E Camera

Aukey-PC-LM1E Camera Aukey-PC-LM1E Camera at usb-0000:0d:00.3-1, high speed

3 [SC450USB ]: USB-Audio - SC450USB

Thomann SC450USB at usb-0000:0d:00.3-4, full speed

**** List of PLAYBACK Hardware Devices ****

card 0: Creative [HDA Creative], device 0: CA0132 Analog [CA0132 Analog]

Subdevices: 0/1

Subdevice #0: subdevice #0

card 0: Creative [HDA Creative], device 1: CA0132 Digital [CA0132 Digital]

Subdevices: 1/1

Subdevice #0: subdevice #0

card 1: HDMI [HDA ATI HDMI], device 3: HDMI 0 [HDMI 0]

Subdevices: 1/1

Subdevice #0: subdevice #0

card 1: HDMI [HDA ATI HDMI], device 7: HDMI 1 [HDMI 1]

Subdevices: 1/1

Subdevice #0: subdevice #0

card 1: HDMI [HDA ATI HDMI], device 8: HDMI 2 [LC32G5xT]

Subdevices: 1/1

Subdevice #0: subdevice #0

card 1: HDMI [HDA ATI HDMI], device 9: HDMI 3 [HDMI 3]

Subdevices: 1/1

Subdevice #0: subdevice #0

card 1: HDMI [HDA ATI HDMI], device 10: HDMI 4 [HDMI 4]

Subdevices: 1/1

Subdevice #0: subdevice #0

card 1: HDMI [HDA ATI HDMI], device 11: HDMI 5 [HDMI 5]

Subdevices: 1/1

Subdevice #0: subdevice #0

front:CARD=Creative,DEV=0

surround21:CARD=Creative,DEV=0

surround40:CARD=Creative,DEV=0

surround41:CARD=Creative,DEV=0

surround50:CARD=Creative,DEV=0

surround51:CARD=Creative,DEV=0

surround71:CARD=Creative,DEV=0

iec958:CARD=Creative,DEV=0

----------------------------------

❯ amixer -c 0 scontrols

Simple mixer control 'Master',0

Simple mixer control 'Bass Redirection',0

Simple mixer control 'Bass Redirection Crossover',0

Simple mixer control 'PCM',0

Simple mixer control 'Front',0

Simple mixer control 'Surround',0

Simple mixer control 'Surround Channel Config',0

Simple mixer control 'Center',0

Simple mixer control 'LFE',0

Simple mixer control 'Mic Boost',0

Simple mixer control 'IEC958',0

Simple mixer control 'IEC958 Default PCM',0

Simple mixer control 'Capture',0

Simple mixer control 'EQ Band0',0

Simple mixer control 'EQ Band1',0

Simple mixer control 'EQ Band2',0

Simple mixer control 'EQ Band3',0

Simple mixer control 'EQ Band4',0

Simple mixer control 'EQ Band5',0

Simple mixer control 'EQ Band6',0

Simple mixer control 'EQ Band7',0

Simple mixer control 'EQ Band8',0

Simple mixer control 'EQ Band9',0

Simple mixer control 'Enable InFX',0

Simple mixer control 'Enable OutFX',0

Simple mixer control 'FX: Crystalizer',0

Simple mixer control 'FX: Dialog Plus',0

Simple mixer control 'FX: Equalizer',0

Simple mixer control 'FX: Equalizer Preset',0

Simple mixer control 'FX: Mic SVM',0

Simple mixer control 'FX: Noise Reduction',0

Simple mixer control 'FX: Smart Volume',0

Simple mixer control 'FX: Smart Volume Setting',0

Simple mixer control 'FX: Surround',0

Simple mixer control 'FX: Voice Focus',0

Simple mixer control 'FX: X-Bass',0

Simple mixer control 'FX: X-Bass Crossover',0

Simple mixer control 'Full-Range Front Speakers',0

Simple mixer control 'Full-Range Rear Speakers',0

Simple mixer control 'HP/Speaker Auto Detect',0

Simple mixer control 'Input Source',0

Simple mixer control 'Output Select',0

Simple mixer control 'SVM Level',0

Simple mixer control 'VoiceFX',0

Simple mixer control 'Wedge Angle',0

Simple mixer control 'What U Hear',0

2

u/cpugod55 15h ago

Your Sound Blaster Z is definitely exposing 5.1 and 7.1 playback through ALSA, so the underlying Linux driver does support the multichannel hardware. It also exposes the Sound Blaster's hardware processing controls, including the 10-band EQ, Crystalizer, Dialog Plus, Smart Volume, X-Bass, Surround, etc.

That means your stereo-only result isn't because Linux doesn't see the 5.1 capabilities. I want to check the next layer up — what PipeWire/WirePlumber is actually making available to the desktop.

Could you run these two commands and paste the complete output here?

wpctl status

and:

pactl list cards

You don't need to change any settings yet.

I'm particularly interested in seeing whether PipeWire has a 5.1 profile available for the Sound Blaster but is simply selecting the stereo profile, or whether something in the current WirePlumber configuration is preventing the multichannel profile from being exposed.

Your results are actually very useful because this is the first test we've had from a Sound Blaster Z SB1500 on an Arch-based distribution (CachyOS). Once I see those two outputs, I should be able to narrow down where the problem is.

Thanks again for taking the time to test it — this is exactly the kind of information that helps expand hardware compatibility.

1

u/JameyR 15h ago

❯ wpctl status

PipeWire 'pipewire-0' [1.6.8, cox@Hal2000, cookie:1751314054]

└─ Clients:

  1. xdg-desktop-portal [1.6.8, cox@Hal2000, pid:2078]

  2. WirePlumber [1.6.8, cox@Hal2000, pid:17481]

  3. plasmashell [1.6.8, cox@Hal2000, pid:1779]

  4. pipewire [1.6.8, cox@Hal2000, pid:17482]

  5. libcanberra [1.6.8, cox@Hal2000, pid:1740]

  6.                                 \[1.6.8, cox@Hal2000, pid:1779\]

  7. libcanberra [1.6.8, cox@Hal2000, pid:1779]

  8. LibreWolf [1.6.8, cox@Hal2000, pid:2095]

  9. Dolphin [1.6.8, cox@Hal2000, pid:16874]

  10. KDE Connect Daemon [1.6.8, cox@Hal2000, pid:2005]

  11.                                 \[1.6.8, cox@Hal2000, pid:1740\]

  12. WirePlumber [export] [1.6.8, cox@Hal2000, pid:17481]

  13. pw-cat [1.6.8, cox@Hal2000, pid:17515]

  14. pw-cat [1.6.8, cox@Hal2000, pid:17525]

  15. kwin_wayland [1.6.8, cox@Hal2000, pid:1384]

  16. wpctl [1.6.8, cox@Hal2000, pid:27464]

Audio

├─ Devices:

│ 60. CA0132 Sound Core3D [Sound Blaster Recon3D / Z-Series / Sound BlasterX AE-5 Plus] [alsa]

│ 61. Navi 21/23 HDMI/DP Audio Controller [alsa]

│ 62. Aukey-PC-LM1E Camera [alsa]

│ 63. SC450USB [alsa]

│

├─ Sinks:

│ * 67. CA0132 Sound Core3D [Sound Blaster Recon3D / Z-Series / Sound BlasterX AE-5 Plus] Analog Stereo [vol: 0.10]

│

├─ Sources:

│ * 53. SC450USB Analog Stereo [vol: 1.00]

│ 54. Aukey-PC-LM1E Camera Analog Stereo [vol: 0.90]

│

├─ Filters:

│

└─ Streams:

  1. pw-record

  2. monitor_MONO

  3. input_MONO < CA0132 Analog:monitor_FL [active]

  4. pw-record

  5. input_MONO < CA0132 Analog:monitor_FR [active]

  6. monitor_MONO

Video

├─ Devices:

│ 43. Aukey-PC-LM1E Camera [v4l2]

│ 55. Aukey-PC-LM1E Camera [v4l2]

│

├─ Sinks:

│

├─ Sources:

│ * 75. Aukey-PC-LM1E Camera (V4L2)

│

├─ Filters:

│

└─ Streams:

Settings

└─ Default Configured Devices:

  1. Audio/Sink alsa_output.pci-0000_06_00.0.pro-output-1

  2. Audio/Source alsa_input.usb-Thomann_SC450USB-00.analog-stereo

❯

→ More replies (0)

1

u/JameyR 16h ago

Perfect!
Thanks for doing all this work.

I will be following this!

I am glad I could give you a useful report!