A lot of recent Lab time has gone into something unglamorous and necessary: compatibility across audio codecs — decode, encode, and playback — so Dialer's Apps tools can open what people actually have, write what destinations actually need, and preview the result without a mystery middle step.

That work shows up first in chainDRiVE: an on-device effects processor and transcoder aimed at people who care about the file that comes out. Not “High / Medium / Low.” Real parameters — profiles, bitrates, containers, channel layouts, loudness — surfaced where they matter, and capability-probed so we don’t advertise a format the browser can’t actually do.

chainDRiVE is the audio nerd’s converter: signal chain, radio simulation, LUFS, limiter, then a codec drawer that treats AAC LC / HE / friends, MP3, FLAC, Opus, AMR, and specialty WAV as distinct tools — not one vague “convert to audio” button.

CHAiNAMP wants to leave the nest

Inside chainDRiVE today, CHAiNAMP is the preview player after you encode — a place to hear the chain and the codec together. That was never the end of the idea. We want CHAiNAMP as its own standalone player: a Winamp-inspired many-format audio player with a deep bench of effects and processing — skin-adjacent energy, playlist habits, and a signal path that feels like gear, not a system “open with…” stub.

Same Lab muscle, two jobs:

  • chainDRiVE — engineer and print files (batch, parameters, honesty).
  • CHAiNAMP — live with those files (play, process, enjoy, keep going).

Splitting them keeps the converter sharp and lets the player grow the way classic desktop players did: formats first, then personality — spectrum, EQ, effects, the stuff you leave running while you work.

Support as many codecs as we can — honestly

The goal is breadth: decode and play as much of the real world as platforms allow, and encode with enough detail that radio, phone, and archive destinations don’t fight you. That means living with uneven browser and OS support, software fallbacks where they’re practical, and a UI that admits when a path isn’t ready.

We’re not going to pretend every acronym on a store listing is shipping. Some families — xHE-AAC is the clearest example — are still too difficult to implement cleanly across all platforms we care about. We’ll keep probing, keep fallbacks honest, and list what’s actually usable instead of padding a feature matrix for screenshots.

Codec ambition without platform honesty is just marketing. We’ll chase “as many as possible,” and we’ll say when a format is experimental, partial, or not there yet.

More on the transcoder thesis: Why Audio Transcoders Still Matter. Product surface while we build: chainDRiVE.