Rethinking the knob for the software era.

When audio moved into software, the hardware came along as decoration — knobs, sliders, and meters drawn on screen because engineers already trusted them. But a drawn knob breaks the physics of the real one: your hand drags in a straight line while the graphic rotates. Redesigning Neutron 3 gave us the room to ask what fifty years of habit had been hiding — what a control looks like when it's designed for how people actually use software.

ROLE: UX/UI Designer
TEAM: iZotope
TIMELINE: 2018
PRODUCT: Neutron 3

Neutron 3 interface — the shared design system in use across its modules

Every inherited control bought something and paid for it somewhere else. Knobs are compact and dense enough to leave room for visual feedback, but hard to read comparatively — a row of them is a row of tiny angles. Sliders read instantly and compare beautifully, but they're space-hungry, and click-anywhere-to-jump behavior can wreck a fine adjustment. Scrub text is precise in almost no pixels, but strips away any sense of range or position.

Before designing anything new, we audited what we had — where each control earned its place, where it was habit:

Five knob controls at values from 0 to 100, with colored value rings — Knobs — compact and dense, but their circular motion doesn’t translate to a mouse, and edge indicators are hard to compare at a glance.

Five slider controls at values from 0 to 100, with colored fills — Sliders — easy to read and compare, but space-hungry, and the expectation that you can click anywhere to jump can wreck fine adjustments.

Five scrub-text value fields showing 0, 25, 50, 75, and 100 — Scrub text — precise and tiny, but you lose any visual sense of range or position.

Grid of early Gauge concept explorations — outline, fill, and slider variants — Early concepts — exploring how to show a control’s purpose, range, value, and units in a smaller footprint. The outer-ring idea stood out.

The brief had three goals: preserve screen space, make parameter changes easier to read, and improve precision while adjusting sound. The concept that stuck used the outer ring of a circle to carry the value — a knob's compact footprint with a slider's readability, and nothing pretending to rotate. The ring simply fills as the value rises. That became the Gauge.

Familiar enough for audio professionals to trust — but designed entirely for the screen it lives on.

Anatomy of the Gauge control — ring, ring fill, inner fill, arrow indicators, readout, and label

The ring concept was mine; making it real was a team sport. Mike McNasby, our Manager of Platform Design, built a quick CodePen prototype — close enough to code to feel the interaction, fast enough to keep iterating. Internal testing said we were onto something, and each round added a refinement:

A center fill that illuminates as the value increases.
A parameter label that reveals units once you click in.
Directional arrows that appear on demand — showing only the direction still available at the extremes.

After a few rounds of refinement, we validated the design with customers. A few needed time to adapt, but most either loved it or didn't notice the change at all — a good sign we'd improved the control without disrupting anyone's workflow.

This one's live — click and drag the Gauge to feel how it works.

The Gauge shipped as a core part of Neutron 3 — and became a foundation for how iZotope designs controls:

A new interaction pattern for complex audio parameters.
Better parameter visibility in less screen space.
A reusable component that seeded the visual language for future products.

Most of all, it moved iZotope past hardware-inspired design. The Gauge proved questioning inherited patterns — not replicating them — produces controls that feel native to software while earning the trust of experienced engineers.

Rethinking the knob for the software era.

Every control was a compromise.

A knob's footprint, a slider's honesty.

From CodePen to customers.

One control became a language.