• Welcome to ASR. There are many reviews of audio hardware and expert members to help answer your questions. Click here to have your audio equipment measured for free!

Looking for some macOS tester for CamiTune(open-source system-wide PEQ/CamillaDSP)

Shuail

New Member
Joined
Aug 15, 2026
Messages
3
Likes
2
I just joined here today, so hello everyone first :)

I've been studying computer engineering, so I'm comfortable with system-level audio routing, but I'm still fairly new to deeper DSP and the audiophile side. I thought this might be a good place to ask since there are people here with much more varied audio setups and DSP experience than I have, and I 'd really appreaciate any suggestions on what features or functions you think are actually worth having in a tool like this. Especially from a real-world listening or measurement perspective.

I've been working on a small open-source macOS app called CamiTune:

https://github.com/Shuail135/CamiTune

It is basically a native interface around CamillaDSP for system-wide parametric EQ on macOS also with EqualizerAPO text import feature.

I want to be clear that I'm not really trying to promote this as a finished app yet. I'm mainly looking for some people willing to test it and probably find things that I've broken, especially I have modified quite a lot of code derived from BlackHole to build the audio bridge, so that part especially needs testing on different machines.

My biggest problem right now is that I only have one Mac to develop and test on that is running macOS 13. There are a lot of scenarios I am not capable of testing.


The basic idea of the app is :
Mac system audio -> CamiTune Profile(Audio Bridge Driver) -> CamillaDSP -> Audio output device

One thing I wanted to do differently is make EQ profiles behave more like actual output. So instead of opening CamiTune every time you want to change an EQ, you can pick the EQ profile from the macOS audio menu. CamiTune will then automatically apply that EQ profile and send the sound to the audio device you have set in the profile.

This means you can have multiple profiles(EQ) for an audio device, but only one of them that you have chosen will process the system audio.


For the actual DSP, I'm using CamillaDSP, rather than writing my own DSP implementation.

At the moment CamiTune has:
  • up to 20 PEQ bands
  • frequency/gain/Q/preamp controls
  • several common filter types
  • live pre-EQ and post-EQ spectrum
  • EQ response curve
  • separate profiles for different devices
  • profile switching from the macOS output selector
  • Equalizer APO .txt import or paste
  • background/menu-bar operation

Equalizer APO support is something I particularly wanted since I have a lot of presets in that format already. Common PEQ filters work, including PK, shelves, HP/LP, notch, etc., and BW Oct gets converted to Q.

It definitely does not implement all of Equalizer APO syntax yet.

There are also still a huge amount I haven't implemented yet: separate L/R EQ, multichannel, per-app volume control, better menu-bar control, etc.

The main reason I'm posting: testing

I would really appreciate it if anyone here with a Mac is willing to try doing horrible things to it and tell me what breaks.

Especially:
  • macos 14/15/26
  • USB DACs and audio interfaces
  • HDMI/DisplayPort audio
  • changing sample rates

And if someone here understands Core Audio / virtual audio drivers particularly well, I’m also very open to being told that I've done something incorrectly. This is one of the reasons I wanted to post here instead of only asking friends to test it.

The current downloadable build is Apple Silicon. Intel Macs should be able to build it from source, but I haven't made a prebuilt Intel release yet.

Also, the app is not signed or notarized yet, so macOS will complain on first launch and you have to use System Settings → Privacy & Security → Open Anyway. I know that isn't ideal, however at the moment I am not capable to pay 99USD yearly for Apple notarization.

CamiTune is GPLv3, and I intend to keep the project open source.

Criticism, measurements, suggestions and bug reports are all very welcome.

And since this is literally my first day here, please let me know if there a more appropriate section for this kind of post. I really appreciate you taking the time to read this, and even if you don't get a chance to test it, a quick look or a star on the GitHub repo would mean a lot. Thanks in advance!
 
Yes, I have plans for both. FIR/Convolution is actually already implemented in the current development version. It can load WAV impulse responses and run them through CamillaDSP, so that should be in the next release coming soon. However, I need to do some testing before it.

Multichannel is partially implemented at the moment, I already have some channel aware processing and per channel EQ/gain/delay/limiter work in place, but I haven't implemented the main audio path yet.

Also curious what kind of setup you thinking of using it for? I am still a noob in the audiophile world, so a lot of these setups are quite new to me.
 
And here is some progress of the current implementation:

Live Spectrums:
1789270133969.png


Animated Equalizer:
1789270071450.png


Metric & Status(Tempory):
1789270286538.png


Device Correction:
1789270397133.png
 
Yes, I have plans for both. FIR/Convolution is actually already implemented in the current development version. It can load WAV impulse responses and run them through CamillaDSP, so that should be in the next release coming soon. However, I need to do some testing before it.

Multichannel is partially implemented at the moment, I already have some channel aware processing and per channel EQ/gain/delay/limiter work in place, but I haven't implemented the main audio path yet.

Also curious what kind of setup you thinking of using it for? I am still a noob in the audiophile world, so a lot of these setups are quite new to me.
My setup is actually quite computer-based. I’m using a Mac mini M4 connected to my AV receiver over HDMI, with the Mac outputting LPCM 5.1 for the bed layer.

I mainly use the AV receiver as a power amp rather than relying on its processing. The Mac mini handles the entire channel routing and DSP — including EQ, room correction, delays, levels, etc.

So basically, the Mac mini is the “brain” of the system, while the AV receiver is mostly there to provide the amplification.
 
Back
Top Bottom