Sound · music productionIn developmentLinux build first

Start With a Groove.
Finish the Record.

Sound is Avlory's music studio. It opens simply and grows into a full studio, with Avlory's own instruments and effects, 18 templates that set a song up the way each style is made, a mixer where what you hear is exactly what you export, and release details that go straight to Waverate and DistroKid. Every clip on this page is real audio rendered by Sound's engine, and nothing plays until you press play. The screens are from Sound's browser test build, and every number says how it was measured.

  • Windows
  • Linux
  • macOS
  • iOS
  • Android
All planned. Downloads open through the waitlist.
01 · Templates

A template is a song, not a loop.

Each template sets the tempo, swing, key, sections with fills, builds and drops, and a mix to start from. There are 12 genres, 4 fusions (hip-hop × gospel, hip-hop × classical, jazz × blues and R&B × jazz) and two showcase pieces. A template opens as an ordinary song made with Sound's own tools, so you can change anything in it. Below are four of them as Sound renders them, opened and exported with nothing changed.

Hip-hop140 BPM · C minor · the hook, 8 bars
Rendered by Sound's engine from the Hip-hop template: 808, recorded grand piano with vibraphone, a choir stacked with recorded strings, glockenspiel lead, and drums layered with a recorded kit.
Lo-fi82 BPM · D Dorian · the hook, 6 bars
Rendered by Sound's engine from the Lo-fi template: swung drums, sub and recorded electric bass, stacked electric and FM piano, nylon and recorded electric guitar, a pad with recorded strings.
Hip-hop × gospel90 BPM · A♭ major · the hook, 5 bars
Rendered by Sound's engine from the Hip-hop × gospel fusion template, as it opens.
Jazz × blues128 BPM · B♭ Mixolydian · the head, 8 bars
Rendered by Sound's engine from the Jazz × blues fusion template, as it opens.

How every clip on this page was made: Sound's desktop engine (version 0.1.0, the library the app loads, on the same calls the app makes) opened the template, made the edit the caption names, and rendered the whole song offline to 24-bit WAV at 48 kHz on 4 November 2026, on Linux, with Sound's recorded instrument packs installed. The excerpt was cut on the bar, faded out over half a second and encoded for the web as Opus at 40 kbit/s and AAC at 64 kbit/s. Nothing else was done to the sound. avlory/apps/avlory_web/tools/render-sound-demos.py

18templates in the first build, each a whole song with sections
14 to 16×real time to render all 18 (2,002 s of music), notes and mix, from start to finish
7 to 8%of one processor core to play a template, mean, at a 64-sample buffer

Measured 27 and 28 October 2026 on a shared cloud VM with 4 vCPUs (Intel Xeon, 2.10 GHz), Linux, release builds, no sound card (a timed stand-in plays the speakers' part). Another job was compiling on the same machine, so means are the reliable figures. cargo test --release -p avlory-audio-lab --test engine_bench -- --ignored --nocapture --test-threads=1

Recorded libraryLicenceWhat Sound plays from it
Salamander Grand Piano V3CC BY 3.0The grand piano, credited in the app
VSCO 2 Community EditionCC0Strings, brass, woodwinds, harp, organ, mallets
Versilian Community Sample LibraryCC0Hand percussion, vibraphone, kalimba, tenor sax, harmonica
Virtuosity DrumsCC0A recorded acoustic drum kit
Karoryfer basses and guitarsCC0Electric and upright bass, electric guitar
Avlory's own synthsAvlory's own808s and genre kits, electric piano, pads, leads, the choir
Sound's Start a song dialog: a new empty song with name, tempo, key and meter, Open a .sound file, and template cards for Hip-Hop at 140 BPM with 9 sections, R&B, Pop, Rock, Blues, Jazz, Electronic and Lo-Fi, each with a one-line description and Start from this.
Start a song, from Sound's browser test build (a testing build, not a release).
02 · Mix

A mixer with room to spare.

Volume, pan, mute and solo, sends to shared reverb and delay, any of 17 effects on any track, bus or the master, and meters everywhere. A track can stack up to 32 instruments into one sound. Faders glide instead of clicking, and changing a track's effects while the song plays hands over in 30 ms: the old chain keeps running and fades out under the new one. Hear one part three ways: as the template sets it, with an effect added, and pushed to the back of the room.

Lo-fi Keys, alone82 BPM · the hook, 4 bars
Rendered by Sound's engine: the Lo-fi template with its Keys track soloed. Six stacked layers (electric piano, recorded FM piano, a pad) through the part's filter, EQ, compressor and chorus.
Plus Sound's Lo-fi effectthe same 4 bars
Rendered by Sound's engine: the same song with one edit, Sound's Lo-fi effect added to the Keys track as it comes: 12 bits, half the sample rate, a little wobble, hiss at −60 dB, half mixed in.
Distance: farthe same 4 bars
Rendered by Sound's engine: the same song with one edit, the Keys group's Distance moved from near (0) to far (1). One control darkens the part and sends more of it to the shared hall.

The three clips are as the engine rendered them, within about 1 dB of each other in level. Switching keeps your place in the bar.

8 to 9%of one core for 64 tracks, each with EQ, compressor and 4 sends, at a 256-sample buffer (target: under 50%)
22%the same 64 tracks with the full chain: plus saturation, width, an automated filter and ducking
0clicks when the song is edited while it plays, in 15-second runs (43 to 141 click frames before)
0allocations, frees or sleeps on the audio thread under load, now enforced by a test

Measured 27 October 2026 on the same 4-vCPU VM with no sound card, mean load at 48 kHz; before and after were run back to back from saved builds. Real computers and audio interfaces are still to be measured. cargo test --release -p avlory-audio-mix --test engine_bench -- --ignored --nocapture --test-threads=1

Sound's studio with the Hip-hop template at 140 BPM in C minor: tracks for rim, 808, Keys, Choir and Lead with clips across sections from intro to outro, a mixer strip per track with pan, hall send and fader, and the Stage showing where each part sits, near or far. The Keys track is picked: 4 layers, near the front, full width.
The studio with the Hip-hop template, from Sound's browser test build. Its instruments are synth stand-ins there unless the recorded packs are served.
03 · Tools

Everything a template does, you can do.

Templates are built from the same instruments, effects and controls you get, so nothing in them is out of reach. Sound has 47 recorded instruments, 18 synths and 12 drum kits of its own, a synth you program, a sampler that chops and warps, 17 effects, and tools other studios don't have: stacks of up to 32 instruments that fuse into one sound, and one Distance control for depth. Hear three of them.

Stacking: a supersaw wall124 BPM · 8 bars
Rendered through Sound's mixer by Sound Lab (avlory-audio lab-stacks): one supersaw pumping under the kick, then every two bars a layer of the same synth: an octave down and dark, an octave up swelling in, then a detuned copy 25 ms late.
Drum Synth: the hip-hop kit88 BPM · 2 bars
Rendered through Sound's mixer by Sound Lab (avlory-audio lab-drums --template hip-hop): the kit's two-bar demo beat. Every sound is made from oscillators and noise, with no samples.
Hip-hop, in C minor140 BPM · the hook, 8 bars
Rendered by Sound's engine from the Hip-hop template, as it opens.
Hip-hop, moved to E minorthe same 8 bars
Rendered by Sound's engine after one edit: the song's key set to E minor with “move the notes” on. Every pitched part moves the shortest way to the new key; the drums stay.

Recorded instruments

First build

47 instruments from 52 packs: grand piano, a string section with sustained, pizzicato, spiccato and tremolo, brass, woodwinds, basses, guitar, a recorded kit, percussion and mallets. A 117 MB core set installs with the app; the rest download when first picked and stay offline.

Synths you program

First build

Start from any of 18 presets: up to four oscillators (FM, a plucked string, wavetables built in or loaded from a WAV), unison of seven, a filter with its own envelope, drive and four LFOs, free or in time. A key played live is the very note the song renders.

Drum rack and Drum Synth

First build

16 pads, each with layered sounds, pitch, decay, choke groups, a hall send and its own effects, and a step sequencer. The 12 genre kits (88 sounds) come from the Drum Synth, so they're original by construction.

A sampler that chops

First build

Any recording becomes an instrument: start, end and loop with a crossfade, the root note found by listening, an envelope and filter. Chop by hits, a grid or the beat onto pads, across the keys or onto the timeline; warp it to the song's tempo with its pitch kept.

Stacks that fuse

First build

Up to 32 instruments on one track, each with its own octave, level, pan, detune, timing, tone, swell, grit, drift and glide (the 808 slide), plus a selector that thins a stack in the verse and opens it in the hook.

Depth with one control

First build

Distance darkens a part and sends it further into the shared hall at once; every part shares a small room; width keeps the low end in the middle. Distance can move over the song.

17 effects

First build

EQ, compressor, reverb, plate, delay, chorus, saturation, limiter (true peak), multiband, filter, width, transients, doubler, lo-fi, gain, tape stop and stutter, plus ducking under the kick. Each shows its latency and how long its tail rings.

Knobs and Explain this sound

First build

Up to eight knobs a track (Warmth, Width, Punch, Space…), each moving several settings at once and automatable, and a plain-words explanation of how any part is made.

Clip grid

First build

Scenes and slots beside the timeline, launched on the bar, with follow actions, trigger, gate and toggle, pads that launch slots, and the performance recorded into the arrangement.

Play and record

First build

MIDI keyboards (MPE too), the computer's keys or the on-screen keyboard play any track live, 64 voices. Record several tracks at once, punch in and out, loop takes and comp them. A take survives a crash.

Piano roll and automation

First build

Chords from the key, strum, arpeggiate, fold, legato, move into the scale, quantise with swing, humanise with a seed. Lanes with curves and LFOs on any setting, exported exactly as heard.

Your own instruments and voice

First build

Sing or play notes one by one and they become an instrument kept in the song, each note tuned to its pitch. The vocal range finder names your range and voice type, and a voice can be reshaped into another range (in the engine; the app's screen comes later).

More effects

Planned

Gate, de-esser, dynamic EQ, convolution reverb, phaser, flanger, auto-pan, vocoder and an analyser; sidechain keying for any dynamics effect.

Stem separation, with a rights check

Planned

Split a recording on your device, keep the original, and know whether a split from someone else's record can be released, using the sample library's fingerprinting.

Session players

Planned

Players that follow your chords, drum and melody helpers: on your device, off by default, easy to turn on and off.

Scoring

Planned

A Create timeline in as a video track with its markers, the mix sent back; layered music Nebula mixes by intensity.

04 · Plug-ins

Other makers' plug-ins, kept apart.

Second build: plug-ins from other makers

Sound's first build plays only Avlory's own instruments and effects, so a song needs nothing else installed. Plug-ins from other makers come in the second build of the desktop app: they'll load because studios rely on them, but Sound doesn't feature them. Each will run in a separate process, so a plug-in that crashes can't take the song with it. The plan for phones, still a proposal, is Avlory's own only: iOS has AUv3, but Android has no common plug-in format.

PlatformFormatsStatus
WindowsVST3, CLAPSecond build
macOSVST3, CLAP, Audio UnitsSecond build
LinuxVST3, CLAPSecond build
iOSAUv3 is the format there. Proposed: phones use only Avlory's own instruments and effectsProposed
AndroidNo common plug-in format; Avlory's own instruments and effects onlyPhone app planned
Browser test buildAvlory's own onlyTesters

Avlory's own, everywhere

First build

Instruments and effects written in Rust on the shared audio core, so they run the same on every platform and the same in the browser build.

Sandboxed, crash-proof

Second build

Each plug-in outside the engine, in its own process. Proposed: a crash shows a reload button on that device while the song keeps playing, and a meter shows each plug-in's CPU and memory.

A scan that never blocks

Planned

Plug-ins are found in the background, never holding up start-up, with a manager to turn them on, hide them and sort them.

Sound's instruments in other studios

Planned

Avlory's instruments and effects as VST3, AU and CLAP plug-ins for other DAWs, and AAX for Pro Tools, so producers can try them before they switch.

ASIO on Windows

Later

Built into the engine and switched off until Steinberg's licence agreement is signed. Not a plug-in format, but what Windows studios expect from their audio interface.

05 · Files

What goes in, what comes out.

The desktop app is built on Linux first; Windows and macOS run the same engine code, which compiles for Windows but hasn't been built and run on either yet. The browser build is for testers and reads audio through the browser's own decoder. The phone apps come in phase 3.

FileWhat Sound does with itLinuxWindowsmacOSWebiOSAndroid
Reads
.soundOpens a song. Older versions open newer songs and keep what they don't understandFirst buildNot run yetNot run yetTest buildPlannedPlanned
.voiceA Voice recording dropped in as a track, copied in with a link backFirst buildNot run yetNot run yetNot supportedPlannedPlanned
WAVAudio onto a track, or into the samplerFirst buildNot run yetNot run yetTest buildPlannedPlanned
FLACInto the sampler on desktop; onto a track in the browserFirst buildNot run yetNot run yetTest buildPlannedPlanned
MP3, OGG, Opus, AACAudio onto a track, decoded by the browserNot supportedNot supportedNot supportedTest buildNot supportedNot supported
MIDI filesStandard MIDI, type 0 or 1: each part a track with its tempo, channel 10 a drum rackFirst buildNot run yetNot run yetNot supportedPlannedPlanned
.soundrackA rack preset with the recordings its samplers playFirst buildNot run yetNot run yetTest buildPlannedPlanned
SFZ instrumentsA sample library you own becomes an instrument inside the song (in the engine; no screen in the app yet)First buildNot run yetNot run yetNot supportedPlannedPlanned
JPG, PNGCover art, checked for the storesFirst buildNot run yetNot run yetNot supportedPlannedPlanned
Stems, DAWproject, other DAWs' projectsA folder of stems in one step, the open exchange format, and Live, FL and Logic projectsPlanned
AAF, OMF, MusicXML, videoFor scoring outside Create, and notationPlanned, phase 3
Writes
.soundSaved atomically, every edit journalled first, so a crash loses nothingFirst buildNot run yetNot run yetTest buildPlannedPlanned
WAVThe mix; on desktop 16 or 24-bit at 44.1 or 48 kHz, with the ISRC and credits embeddedFirst buildNot run yetNot run yetTest buildPlannedPlanned
FLACThe mix, 16 or 24-bit, taggedFirst buildNot run yetNot run yetNot supportedPlannedPlanned
MP3320 kbit/s through LAME, a separate library beside the app; without it, Sound says how to get itFirst buildNot run yetNot run yetNot supportedPlannedPlanned
StemsWAV or FLAC, by track or by bus, from one pass of the mixerFirst buildNot run yetNot run yetNot supportedPlannedPlanned
MIDI filesA clip, a track or the whole song, with the tempo mapFirst buildNot run yetNot run yetNot supportedPlannedPlanned
.soundrackA rack preset to share, recordings includedFirst buildNot run yetNot run yetTest buildPlannedPlanned
Release packagesWaverate directly; for DistroKid, audio, cover, release.json and the upload checklist, as a folder or ZIPFirst buildNot run yetNot run yetNot supportedPlannedPlanned
AAC, Opus, a preview inside .soundSmaller files, and a preview any Avlory app plays without the editorPlanned
Game and spatial audioLayers for Nebula, Wwise and FMOD; Dolby Atmos and ADM laterPlanned

From the engine's code: crates/sound (the app's calls), crates/project (.sound and MIDI files), crates/release (WAV, FLAC and the packages), crates/lame (MP3), crates/lab (FLAC and SFZ), the desktop app's file pickers, and the browser build's importer. “Not run yet” means the same code, compiled for Windows but not yet built and run on Windows or macOS.

06 · Export

What you hear is what you export.

An export runs the same mixing graph as playback, offline and faster than real time, so the file holds exactly the samples you heard. That's tested bit for bit at buffer sizes from 16 to 4,096, at random sizes, on 1 to 8 threads, and on every template. Stems come from one pass and add up to the mix before the master's effects. Here are three stems from one export of the Hip-hop hook, beside the mix.

The mixHip-hop · the hook, 8 bars
Rendered by Sound's engine from the Hip-hop template: every part through the master's gain, multiband, compressor, saturation, width and limiter.
808 stemthe same 8 bars
From one stems export by bus of the same song, rendered by Sound's engine: the 808 group, two stacked 808s, before the master's effects. Best on headphones or speakers with bass.
Keys stemthe same 8 bars
From the same stems export: the Keys group, two recorded grand pianos with recorded vibraphone and a bell synth.
Choir stemthe same 8 bars
From the same stems export: the Choir group, two choir synths (Sound's stand-in until Avlory records real voices) fused with recorded violins, violas and cellos and a string synth.

Stems leave the master's effects off, so they sit quieter than the mix. Switching keeps your place in the bar.

12.6×real time to export 64 tracks with EQ and compressor, on one thread
21.3×the same on 4 threads
Bit for bitexport equals playback at every buffer size tested, and a song rendered twice is identical

Measured 27 October 2026 on the same 4-vCPU VM: a 60-second song, offline. The bit-for-bit checks run with every cargo test in crates/mix/tests/engine_bench.rs; the speeds come from cargo test --release -p avlory-audio-mix --test engine_bench -- --ignored --nocapture --test-threads=1

Diagram: one mixing graph feeds both the speakers and the exported file. The songtracks, notes, clips One mixing graphthe same code, the same samples Speakerslive, buffer by buffer Exportoffline, 12.6× or faster
Diagram: why the export matches playback. There's no separate render path to drift apart.
07 · Release

Release with every credit attached.

Built in the engine and the desktop appAvlory's own ISRC registrant code comes later

Release details live in the .sound project: credits with roles, splits, the ISRC, UPC and ISWC, and the ℗ and © lines. Sound sends a release straight to Waverate, and makes a ready-to-upload package for DistroKid (it has no public API) with a checklist of its upload form, in order. One recording keeps one ISRC forever, on every service. Check a code the way Sound does.

Night Drive · single · release check

    Two letters, three letters or digits, a two-digit year and five digits. Hyphens and spaces are fine.

    Examples
    This release is

    Waverate, directly

    Built

    Sent through Waverate's artist service with your sign-in, splits and credits filled in. The engine never sees your sign-in token.

    DistroKid, as a package

    Built

    Audio, cover, release.json and the upload form's checklist with copy buttons, until the planned partnership gives a direct link.

    Codes inside the file

    Built

    WAV (16 and 24-bit) and FLAC at 44.1 or 48 kHz, with the ISRC embedded (ID3 in WAV and MP3, Vorbis in FLAC), a loudness report and cover checks.

    A number never reused

    Built

    Once Avlory has its registrant code, Sound issues codes from a registry that never hands out a number twice, even after a deletion.

    Diagram: the release details in a .sound project go to Waverate directly and into a DistroKid package with audio, cover, release.json and a checklist. .sound projectcredits, splits, ISRC, ℗ and ©the master, rendered offline Waveratesent directly DistroKid packageuploaded by you audio · cover artrelease.jsonthe upload form, step by step
    Diagram: where a release goes. Sound's Release screen is in the desktop app, which has no screens on this page yet.
    08 · Samples

    Samples with terms you can negotiate.

    Planned: the library in the second build, royalties after

    A shared library of original sounds only: every upload is checked against known recordings first. Each sample shows its terms. The artist who made it sets the rate, from 0% (credit only) up, and you can send a counteroffer, which they don't have to accept. On Waverate the agreed rate pays real money, out of the song's artist royalties, and the sampled artist can cash it out. Try an offer on an example sample.

    Porch Light keysAsks 15%

    An example sample by an example artist: 4 bars, D minor, 82 BPM. Free to use while you write; an agreement is needed only to release.

      Your offer

      This example artist accepts 12% or more on their own; anything lower they decline and keep their rate. Letting artists set a rate they accept automatically is proposed, not decided.

      Original sounds only

      Planned

      Every upload is fingerprinted against known recordings, so nobody can sell someone else's sample.

      Stamped into the song

      Planned

      The fingerprint, both Avlory IDs, the rate, the credit and the date, signed by both, saved in the project and carried into every export.

      Other services

      Open question

      Getting songs onto Spotify and Apple Music goes through a planned DistroKid partnership. How a sample split carries over there isn't decided yet.

      09 · Together

      Edit one song at the same time.

      Built, on a testing relay onlyInvite-only rooms come with the real relay

      Everyone edits the same song and sees each other's edits as they happen, like a shared document. When two people move the same control at once, the later move wins and the other stays one click away in history. When two people change the same clip, both versions are kept. You can lock the song, a track or a section; locks expire, and the song's owner can break one, with a notice. Try it with Maya.

      Night Drive · KeysYou Maya
      −6.0 dB
        Keys volume

        Maya is an example collaborator; everything here stays on this page.

        Sealed rooms

        Testing relay

        The song, every edit and every recording are encrypted with a key that's only in the link, so the testing server keeps only scrambled bytes.

        Recordings that keep up

        Testing relay

        Recordings go up in chunks in the background. A cut-off upload sends only what's missing, and arrives bit for bit.

        Browser and desktop

        Testing relay

        A desktop and a browser join the same room either way round, with per-person undo and who's here.

        Invited Avlory IDs

        Planned

        Editing and recording need an Avlory ID the owner invited. Listening and commenting can use a private link.

        Status

        Where Sound is today.

        In development. The mixing engine, the .sound file, the instruments and effects, recording, the 18 templates and release export are built, with a desktop app on Linux first and a browser build for testers. Stems, MIDI files and MP3 export are in the desktop app. The sample library and royalties, plug-ins from other makers (in a separate process, in the second build) and the phone apps come next. Downloads open through the waitlist.

        Tested

        • On a Linux build machine with 4 processor threads and no sound card.
        • The engine's Rust tests, a fuzz test of up to 60,000 random engine calls on every thread, and a monkey test driving the real engine through the app.
        • Widget tests on every screen in light and dark, at 200% text and with reduced motion; the browser build in headless Chromium at desktop and phone sizes.

        Not tested yet

        • Latency on real computers, sound cards and MIDI keyboards (the build machine has none).
        • Building and running on Windows and macOS.
        • Phones, plug-ins from other makers, the sample library and royalties: not built yet.
        • No feature moves up a tier

          A saved project always opens and exports, even after a plan ends.

        • Never locked out offline

          A failed licence check never stops editing or export.

        • AI never changes work silently

          Every AI change is a visible, undoable suggestion in the AI ledger.

        • Free to start

          Plans and prices are announced at launch. All the promises

        Waitlist

        Try Sound First.

        Sound's downloads open through the waitlist. We'll email you when it's ready on your platform.

        Which apps?

        It helps us decide what to finish first.0 / 500