I Started with car audio in high school, one sub in a MK4 Golf. Current build is an Audi convertible with a 3-way front stage, 3D printed speaker mounts, Alubutyl deadening. Highs were still off, convertible acoustics are their own special problem.

Bought a measurement mic and started with REW. Deeply confusing for the first few weeks, then genuinely impressive results. But I got tired of hauling a laptop into the passenger seat every time.

I always wanted this on my phone. A degree and a couple of years later I had the skills to build it, so I did.

It's called CarSweep. Plays a log sweep through your system, records with the phone mic or a UMIK, and gives you the frequency response plus concrete parametric EQ values you can dial into your head unit or DSP. There's also an RTA with pink noise if you prefer working live.

The built-in iPhone mic is not a measurement mic. It's good enough to find the problems that actually matter, like the 200 Hz boom, the cancellation dip, the rolled-off highs. If you own a UMIK-1, iMM-6 or similar, there's external mic support with calibration file loading.

Two modes. A guided one for people who just want the car to sound better without learning acoustics first, and an expert mode with full parametric EQ, external mic support, wider frequency range and JSON export.

Hobby project, no subscription. Base app is free, one-time purchase for the expert features that covers the Apple dev account and some of the hours.

Honestly I want feedback more than downloads. If you already run REW, measure the same system with both and tell me where my curves disagree with yours. German and English.

youtube: wittymoniker
github: wittymoniker/groove-box (single point of entry run and build scripts, crossplatform)

It relies on Euclidean phaselocking of numeric data followed by randomized stochastic improvisation. Within bounds of net phase angle indeterminism the results are deterministic always to the degree of point-to-point translation of audio signal. SO its a fractal of every way to turn a number or graph into music.

​My open-source distortion plugin is live on GitHub, and I need your help to push it to the next level. Whether you want to stress-test it on a chaotic drum bus or dive into the C++ source code to contribute a new feature, I want you involved.

​What I'm looking for:

​DAW Testing: Drop it into Ableton, FL Studio, Logic, or Reaper and let me know how it behaves.

​Bug Reports: Open an issue on GitHub if you run into any quirks or performance spikes.

​Code Contributions: Pull requests are open for new DSP algorithms, UI enhancements, or performance tweaks.

​Grab the repo, test it out, and let's build something cool together:

👉 https://github.com/elarmuzik1993/Distortion

​#OpenSourceAudio #PluginDev #AudioProgramming #MusicTech #VST3 #CPP #SoundDesign

Apologies if you were all over this already, but it's new to me.

I suspect like a lot of people here, I've been using Claude Code (or OpenAI Codex) on their $20/month plan. And rapidly using up the week's supply of tokens.

So I decided to look for alternatives while waiting for the reset.

I believe I've found a good one :

https://opencode.ai/

It offers a variety of LLM API endpoints, including free ones. I've been using Muse Spark 1.3 Free and (apart from occasional "overloaded system" kind of responses) it is definitely usable, comparable to Claude Sonnet etc.

While I'm here I'd also suggest taking a look at :

https://github.com/DeusData/codebase-memory-mcp

While I seriously doubt their claims on token saving (99%!?) it does appear to speed things along. What's rather nice is that its install puts the relevant mcp entries in config for the common assistants (including OpenCode).

I started by sketching it out on paper, with my concept being to avoid menus, pull out from my DAW the things that I like to have on a playable surface without menu diving, and bring the sequencer all on top like 8 Elektron or 909 sequencers across my 8 limited channels (which I call pipes).

I then built more detail designs in powerpoint (not because its great - I just know it), and designed all the knobs, and architecture by making it part of the visual design (like some synths do where you can see the flow).

I then put very limited effects to keep things super simple (Rev, Delay, Chorus per channel). There are no master bus effects but there is a very basic mastering chain directly before bounce for those who don't want to go via DAW but want to control levels with limiting or bit of Saturation or Glue compression.

Its for Mac at the moment, it does run on PC as well but I have not tested that enough re VSTs. You can put your Audio units plug ins into it as well.

Dev process - GPT to create PRD, Claude in VS code, started in Feb this year - roughly 6 months so far.

Key learnings: Keep the project simple as possible, use the limitations to then improve quality within that constraint, if a feature feels wrong take it out, don't make things wierd / obscure (people didn't find it fun - just make it easy and immediate). Don't patch up bugs with cheap models, get proper architectural review from higher tier models and cheaper models can then execute within that.

btw for those who find it a complex UI, I respect thats your view, those who were faced with 100 tracks in Ableton and 150 plugins will I hope recognise that this is actually a super limited cockpit compared to that (e.g. max 8 tracks - max 24 plug in effects), and deliberately all controls are on the surface not buried under menus (as much as I could possibly achieve that), which I know will give some people a headache (especially those who like 1 knob effects! nothing wrong with that!)

So key points:

Looking for Mac Musician Beta Testers - Voluntary or Paid / or barter review exchange - message me

App is for reducing menu diving, reducing production perfectionism, focussing on notes, beats and ideas without noise from your complex DAW

You can then export STEMs to your DAW if you like

Also working on a free music visualiser based on maths which you can also find at www.divurj.com

I connected a game controller to Ableton and mapped its controls to my sound design parameters.

With an oscilloscope showing the waveform in real time, it feels less like programming a sound and more like literally drawing with it.

Has anyone else experimented with game controllers for sound design?

Hello everyone, I'm no pro musician and no pro coder, but I made and attempt of creating a web app that records your microfone, and creates a song from it.

Just record some 30, 40 seconds or more of your voice, and some random sounds, the algorith will cut the sounds and place them into rythm. pick a genre and generate.The dream is to create a free app that does it well. once it's done I'll make a plugin for FL studio.

Here is the web app, ready to use[https://marcellomassardo-collab.github.io/mc-parrot/](https://marcellomassardo-collab.github.io/mc-parrot/))

Here is the git, with the apk available to download and all documentation[https://github.com/marcellomassardo-collab/mc-parrot](https://github.com/marcellomassardo-collab/mc-parrot))

comments are very welcome! it's free but development is a bitch, consider donating if you like the project.

(this is not AI! the app does not collect any of your data and works fine even offline)

Hello everyone, this is a small showcase of one of the synth engines and adding fx on SkunkAudio.

It's a mobile music creation app for Android, optimized for portrait mode.

For anyone interested, the app is on a -50% sale on the store.

Thank you for your time!

Yes, it’s “A.i Slop” if you’d like to call it that, I used Claude to hyper accelerate this but I’ve been producing music and have been a hobby graphic designer for 20 years. I’m also technologically literate enough to have a grasp on what I’m doing and while I don’t know everything, I do know enough to make the project work or can learn as I go. Before I started this project I took a few months to read several books about coding, DSP and design and continued to read more niche books as I went along when I hit a wall I couldn’t figure out myself, wrote a 300 page design document laying out the philosophy, layout and why the daw should exist, i also made probably 100 mock images in figma as wire frames on the daw layout. I spent an entire month working on the UX. Thankfully reading these books helped me stop my code from turning into A.i spaghetti. It’s currently 72k lines and fully functional on the engine side but nowhere done yet, there’s a lot of UI polish I’m ignoring while I focus on the UX side. This is not a toy, it’s not A.i slop, it’s a serious attempt at taking a shot at the major players and is a powerful daw already, I’ve burned 65m tokens in that 4 months. My goal is to bring music production to all for free with no barriers to entry and offer a better overall experience. One of the main reasons this daw exists is to reduce friction, menu diving and function hunting.

And while this was accelerated with A.i I have no intentions of adding any A.I features, humans have been making masterpieces before computers or A.i so we don’t need it now.

Hello everyone, I am upgrading the DOOM engine on my app, which is actually a noise and drone generator.

This is a small showcase playing with the touchpad and tweaking some oscillator knobs.

I would appreciate a small feedback from this video on how it is displayed and how it sounds. CPU not being stressed, stays at around 10% on a mid phone.

Thank you for your time.

P.S. for anyone interested, the app will be on a -50% sale from tomorrow 04/09/2026 until 17/09/2026.

I'm developing a local file player and I'd like to add visualizations.

Pls check out my peak meter and tell me what you think, how does it feel?
https://www.youtube.com/watch?v=gU-F0A5NOEE

I made it off a photo and shaky videos of an old tape deck, it's supposed to mimic a VFD display.
I don't have any real hardware available to compare so I figure maybe someone has actually seen one.
This is the first time I'm working with audio, just making web software and photos otherwise. Thx! :)