Sound mixer UX: separate layers from playback

Show the active layers as a manageable set

CardiMate shows four named layers with individual sliders under a named sound scene. Castbox combines three active layers with a larger catalog of categories and locked choices. The layouts make a useful distinction: what is available to add versus what is already contributing to the current mix.

Give every active layer a recognizable name and a direct route to its level. If a layer’s catalog tile remains selected, keep that state consistent with the active set. A separate active-layers area helps when the catalog is long or filtered. People should not have to remember which of many tiles they tapped in order to remove one sound.

Make loading and unavailable assets visible at the layer level. A selected tile should not imply audible playback while its file is still downloading. If one sound fails, preserve the rest of the mix and offer retry or removal for that sound. Avoid replacing the entire mixer with a global error when three other layers can still play.

Distinguish quieting a layer from removing it

ShutEye shows three active sound rows with sliders and remove controls, plus Clear All, a timer and Save Mix. Sleepiest presents three layers in My New Mix with Save and Cancel. A slider and a remove action can coexist because they change different parts of the composition.

Define zero volume, mute and removal separately. Zero can retain the layer at the bottom of its level range. Mute can temporarily silence it while remembering a previous level. Remove takes it out of the mix. You do not need all three controls, but the available actions should have consistent consequences and accessible labels tied to the sound name.

Treat Clear All as a collection action, not a playback shortcut. A person trying to stop sound should not have to erase their mix. Keep Pause or Stop distinct and make clearing recoverable when possible. If Clear All affects an unsaved draft, explain that scope; if it updates a saved preset immediately, provide a stronger warning and an undo path appropriate to that persistence model.

Keep playback controls separate from composition tools

White Noise shows a named mix, layer sliders and a menu with Duplicate, Rename, Delete and Edit Sounds, while keeping player and output controls nearby. Ease combines a sound catalog with an active-mix overlay, remove controls, play and timer actions. Both need to communicate what continues when the editing surface closes.

Keep play and pause attached to the whole audible mix unless a control is explicitly per-layer. A layer slider should not unexpectedly start playback when the person only wants to prepare a mix. If live preview is part of editing, make that behavior evident and give a direct way to stop it without discarding composition changes.

Separate output routing and device volume from relative layer balance. Changing headphones or the device volume should not rewrite all saved layer levels. If a master mix level exists, label it distinctly from the device’s own output volume. A person should be able to lower everything temporarily without losing the balance they created between rain, wind and a background track.

Make fine adjustment possible without precise dragging

Feelsy shows an active Rain layer and a slider within Custom Mix, alongside a gesture hint. Focustown exposes individual percentages and a Reset All control under its soundscape settings. Numeric feedback can make a relative level easier to revisit, but it should not suggest a scientifically calibrated listening level unless the product actually provides one.

Use accessible slider labels such as Rain level, and announce the current value and available adjustment. Provide reliable small increments for keyboard, switch and screen-reader interaction. A decorative slider that only responds to a narrow drag target can make a simple balance task unnecessarily difficult, especially while several sounds are already playing.

Decide whether the displayed value is a product-relative percentage or a measured audio quantity. Most consumer mixers can use relative levels without exposing technical audio units. Keep the mapping consistent and avoid sudden jumps near the ends. If changing a level uses smoothing to prevent abrupt transitions, verify it with actual audio; the recorded interface alone does not establish how another product sounds.

Explain the relationship between main tracks and background layers

Slumber separates Main Track from a set of background sound levels and shows a delayed-ending control. Remly displays Sounds 4/10 and Music 0/1 with Add Music and Save Mix. Those interfaces reveal that not every audio item necessarily occupies the same kind of slot. A primary narration and an ambient layer may follow different rules.

Name category limits before the person reaches them. If only one music track can be active, selecting another should clearly replace the previous one or ask for confirmation when useful. A ten-sound allowance should not silently count a main track as an eleventh item. Keep counters attached to the category they describe and update them only when a layer has actually been accepted.

A timer should explain what ends: all playback, the main track or a particular layer. Saving a mix should also state whether it saves the timer. Otherwise a person can reopen a familiar mix and be surprised by an old countdown. Treat timing as a separate preference unless the product explicitly presents it as part of the saved scene.

Represent a mix independently from the audio engine

Store a mix as a named collection of stable asset IDs, relative levels and supported layer settings. Keep that definition separate from the current audio-engine state, download progress and output route. A temporary interruption should not mutate the saved preset, and restoring playback should not require reconstructing the mix from whichever UI tiles happen to be visible.

Define whether editing a saved mix changes it immediately or creates a draft. A draft supports Cancel and Save; immediate editing needs clear persistence and an undo strategy. Saving should capture a consistent composition, including layers still loading only if the product can restore them reliably. If an asset becomes unavailable later, show the missing layer rather than silently replacing it with a different sound.

Handle audio interruptions, output changes and background transitions deliberately. Preserve the composition while accurately reporting whether playback is active. Avoid automatically resuming into a new output route without considering the product’s audio-session behavior. Test the real audible result, not just state flags or moving visualizers. The mixer’s interface and the audio engine should agree about what is currently playing.

Review balance, recovery and saved state together

Create a mix, lower one layer, mute another, remove a third and save. Reopen it after relaunch and confirm that each action has its stated meaning. Include a locked sound, a failed download and a reached layer limit. The person should understand what can play now, what is pending and what is unavailable without losing the usable part of the mix.

Test a route change, interruption, timer expiry and app backgrounding. Confirm that pause preserves the selected layers and that clearing the mix does not behave like pause. If a timer fades playback, listen to the transition and inspect what happens to the saved levels afterward. A fade should not leave every layer permanently saved at zero unless that was an explicit edit.

Check large text, focus order and announced slider values. Labels must remain associated with the correct layer when rows are removed. After deletion, move focus to a sensible neighboring control rather than the top of the catalog. Avoid claims that a particular mix treats a condition; explain the controls and let users choose the listening experience they prefer.

Review the mix as four separate states

Use these checks on a working build, not only on the polished reference state.

• ✓The catalog and active layer set are distinguishable.
• ✓Level, mute and removal have clear independent meanings.
• ✓Pause stops playback without erasing the composition.
• ✓Per-layer levels remain separate from master and device volume.
• ✓Saved presets have an explicit draft or immediate-save model.
• ✓Category limits and unavailable sounds are explained locally.
• ✓Timers and interruptions preserve a predictable recoverable mix.

Connect the mixer to access and recovery

The feature-gating examples help explain locked sound choices without discarding an otherwise usable mix.

Use the error-state examples to design per-layer retry when an asset cannot be loaded, rather than blocking every sound.