-
Notifications
You must be signed in to change notification settings - Fork 37
feature: integrate per-stem volume sliders into the mixer popover #7
Copy link
Copy link
Open
Labels
audioAudio engine, latency, routing, VST/NAMAudio engine, latency, routing, VST/NAMcap:1:audio-mixFaders, mixer state, analyser integration, and per-source balanceFaders, mixer state, analyser integration, and per-source balancecap:1:stemsStem ownership, stem state, stem mute/restore, and stem-specific playback behaviorStem ownership, stem state, stem mute/restore, and stem-specific playback behaviorpluginRelates to a slopsmith pluginRelates to a slopsmith pluginuxuser-experienceuser-experience
Description
Activity
Metadata
Metadata
Assignees
Labels
audioAudio engine, latency, routing, VST/NAMAudio engine, latency, routing, VST/NAMcap:1:audio-mixFaders, mixer state, analyser integration, and per-source balanceFaders, mixer state, analyser integration, and per-source balancecap:1:stemsStem ownership, stem state, stem mute/restore, and stem-specific playback behaviorStem ownership, stem state, stem mute/restore, and stem-specific playback behaviorpluginRelates to a slopsmith pluginRelates to a slopsmith pluginuxuser-experienceuser-experience
Follow-up from #378 / #94.
slopsmith#94 introduces a fader registry (`window.slopsmith.audio.registerFader`). For sloppak songs with separated stems, each stem (guitar, bass, drums, vocals, piano, other) already has its own GainNode in `window._stemsState`, exposed today via the existing stem panel. Folding them into the mixer popover would give the user one surface for all audio balance: Song · Amp · Guitar Stem · Bass Stem · ...
Considerations
Out of scope for this issue
Acceptance criteria
Reference: parent feature #378, registry implemented in #94.