stemstudio.
Generated palette illustration. Exact project colors shown above.
Your track. Ready for the next idea.
Working with separated audio should not mean losing track of files and versions. OOG built a local Mac workspace for listening, shaping and exporting stems, keeping the source and the next usable files together.
OOG’s contribution: Local audio-workspace and playback interfaces, import/transport/file workflows, sound-shaping controls, saved versions and export handling, with native desktop and engine-integration development.
Stem Studio is a local Mac workspace for separating vocals and instruments, reviewing playback and exporting audio. The interface brings splitting, listening, EQ, compression and cleanup together with native folders, saved versions and paired exports in a local audio workflow. The broader project includes import and playback, engine/model choices, waveform and transport controls, and saved-result organization. A newer native desktop preview extends the original browser workspace with local file and URL-import code, selected-track editing, library/result reuse and platform-specific packaging. These implementations share a local audio goal while retaining distinct interfaces and source histories.
What we built
Local application · Interface design
A local music workspace designed around listening, adjusting and exporting. The browser interface connects to native folders and a local processing service, with stem previews, paired exports, saved versions and sound-shaping controls. Source selection, audition and output handling remain explicit steps. The original browser workspace uses its Stem Studio identity; the native desktop preview has a separate equipment-style interface. Import, playback, trim/loop, model choice and export context are kept visible rather than reduced to a single split action.
- Stem previews & paired exports
- Equalization, compression & cleanup
- Native folders & saved versions
- Local file and URL-import source workflows
- Player, transport, waveform and source/result selection
- Engine/model selection and output manifests
- Trim, loop, batch export and reuse of saved results
- Native desktop packaging and platform-specific integration
Listen. Shape. Export.
Native folders, audio controls and saved versions share one workspace.
The files stay part of the workflow.
Native folder access and the local processing service connect the source media to split previews and paired exports. Saved versions let the operator keep iterations organized while EQ, compression and cleanup controls shape the sound before export.
Know what you are listening to.
The source includes local file selection and website-media import, waveform and duration views, source/result selection, play/pause/stop and seeking. Native desktop work adds track selection, loops and editing/export controls so the selected input, auditioned result and next split source can be understood separately.
Choose the process and keep its context.
The project contains multiple separation-engine and model paths, with output choices and processing records. The native preview includes replacement music engines alongside the earlier engine lineage; model identity, configuration and output context stay associated with processing. Engine integration is development work, not a claim of perfect isolation on every recording.
Keep the result useful.
Paired and multi-stem outputs, processed copies, saved versions, result libraries and batch export support the next creative step. Browser processing offers presets, EQ, compression and cleanup; native work adds selected-track editing and result reuse. Format handling and platform packaging are part of that workflow.