Yassir Chebaa

Eager software engineer with a BSc in Computer Science. C++ and Rust enthusiast, always learning.

  • Posts
  • About
  • Contact
  • GitHub
  • LinkedIn

Scaler 3 at KoalaDSP

done2024-12-07NDAProduct

  • c++
  • audio-plugin
  • caching
  • multithreading
  • serialization
  • algorithms
  • testing
  • freelance

Freelance C++ engineer on Scaler 3, a commercial music composition plugin used by producers worldwide. Built its thread-safe cache manager and serialization in a production codebase.

The product

Scaler 3 is a commercial music theory and composition tool. It ships as a standalone app and as a VST3, AU and AAX plugin running inside every major DAW, on macOS and Windows. It suggests chords and scales, detects keys and chords from MIDI and audio, generates melodies, basslines and arpeggios, and arranges it all on a timeline.

From December 2024 to January 2026 I worked on it as a freelance C++ engineer at KoalaDSP, shipping code into a released product used by real musicians.

The work is under an NDA, so the source code stays private. This page covers what I took on and what I brought to the team.

What I delivered

  • Cache manager: built the app’s thread-safe cache manager, so it reuses work it has already done instead of recomputing or reloading it, keeping Scaler fast and responsive while a musician is working.
  • Serialization: built serialization for saving and restoring the app’s data and state reliably, so a project reopens exactly as it was left. It is backward compatible: data saved by older versions of Scaler still loads correctly in newer ones, so updates never break a user’s existing work.
  • Best-fit algorithms: worked on best-fit algorithms that pick the closest match from many candidates, the kind of logic behind finding the right result fast in a large search space.
  • Testing: wrote tests around this work, so caching and serialization stay correct as the codebase evolves.
  • Production C++: wrote and maintained code in a large, mature codebase built on the company’s in-house libraries, to the standard of a shipping commercial product.

What I bring from it

  • Ramping up fast: became productive in a large existing C++ codebase and its internal libraries, rather than only working on greenfield projects.
  • Performance thinking: a habit of asking what work can be skipped, reused or done earlier, and measuring the result.
  • Remote teamwork: worked as part of a distributed team, with regular calls to report progress, raise blockers early and align on priorities, and fitted my work cleanly into a shared codebase alongside other developers.
  • Professional discipline: handled a commercial codebase under NDA, with the trust and confidentiality that comes with it.

Why it was hard

Scaler is a multi-threaded environment: the audio, UI and background threads all touch shared data at the same time, so every piece of it has to be safe under concurrency without blocking the real-time audio. On top of that, data has to survive save, reload and version changes without breaking a user’s work.

All of this ran against tight release deadlines. Staying calm under pressure was key: shipping new features quickly while keeping the existing work robust, with no regressions. That made architecture crucial. Getting the structure right up front is what allowed new features to land fast without destabilizing what was already there.

OlderDoodle JumpNewerMovie App
All projects

Questions about this project? Contact me

Disclaimer|Privacy Policy