Technology

Under the hood.

For anyone who also thinks about runtimes, plugins and data formats when looking at a music app. A short tour of what makes Parentone tick.

Common Lisp / SBCL

The musical modules are built on Common Lisp and Parentone’s ccb library. SBCL runs the calculations in a separate process. The app exchanges typed lists and results with the Lisp runtime through a JSON interface.

Steel Bank Common Lisp ↗
JUCE / C++

The native audio engine uses JUCE for audio playback and VST3 hosting. Installed VST3 instruments are discovered automatically; plugins run in a separate audio process.

JUCE ↗
MTS-ESP

Parentone acts as an MTS-ESP master, transmitting tuning to compatible instruments for EDO-N, JI-5 and JI-7 playback. The instrument must support MTS-ESP and be configured to use it.

ODDSound / MTS-ESP ↗
C# / .NET / Avalonia

The desktop interface and application logic are written in C# on .NET. Avalonia renders the patch workbench, list editors and dialogs. Lisp calculations and audio hosting are handled separately.

Avalonia ↗
MIDI / Scala / KBM

MIDI files take the generated material into your DAW. Scala (.scl) and keyboard mappings (.kbm) describe scales and key assignments. A MIDI file alone carries neither plugin presets nor the microtonal tuning; set these up separately in the destination environment.

ASP.NET Core / PostgreSQL

The backend uses ASP.NET Core on .NET 10 and PostgreSQL to manage accounts, licences, releases and feedback. Musical calculations run locally on your computer.

Explore what Parentone can do