App Overview

STEM: Live Stem Separation icon

STEM: Live Stem Separation

Michael Ivertowski · Music

Plug in your audio interface, start the record, and the vocal is on its own fader

$14.99

PRICE
$14.99
No in-app purchases
BUSINESS MODEL
Paid
No overall Grossing estimate available
RATING
N/A
No ratings yet

Evidence scope: No current overall US chart position is available. Category-chart positions shown in discovery are a separate scope. Revenue is a directional model estimate, not verified earnings.

Build your own version

Build Kit

Make this idea yours

A product spec, screen plans, and build steps for your coding agent.

First kit free with a verified email

Add to a Remix

Combine features and design from your favorite apps.

Your first Build Kit is free with a verified email.

What's included

A product spec, phased build plan, differentiation notes, and screen references.

  • START_HERE
  • AGENTS
  • EVIDENCE
  • SPEC
  • BUILD_PLAN
  • DIFFERENTIATION
  • skills/
  • screens/
Preview a sample Build Kit No email needed

Illustrative example: an invoice app for independent contractors. Your kit is tailored to the app you choose; this is not its generated content.

Feature spec

Goal: Send a clear invoice after finishing a job.

  • Add a client, line items, a due date, and payment instructions.
  • Preview the total before exporting a PDF.
  • Keep an editable draft if export fails.

Screen plan

Invoice editor: Client at the top, editable line items in the middle, total and preview action at the bottom.

States: Empty draft, validation errors beside each field, exporting, and a retry action that preserves the draft.

Differentiate and validate

Hypothesis: Contractors need faster repeat invoices more than more templates.

First experiment: Test duplicating a previous job with five contractors. Watch where they hesitate before expanding the feature set.

The full kit adds a phased build plan, evidence notes, tool prompts, and implementation guidance. It is a plan for your coding agent, not a finished app.

Usage: Mechanics are fair game; never reuse the original name, branding, assets, or verbatim copy.

JavaScript is required to complete mailbox verification.

Free quick prompt For a smaller starting point

Quick prompt

> SELECT BUILD PLATFORM:

Good fit for mobile-first iOS and Android prototypes with managed app scaffolding.

// RORK SYSTEM PROMPT







            

Loading build analysis and prompts…

JavaScript is required to complete mailbox verification. Return to this prompt preview.

Continue in Rork copies the full prompt to your clipboard first, then opens Rork in a new tab.

Continue in Rork >

Affiliate link: CloneChart may earn a commission at no extra cost

App evidence

Original App Store material. Ratings and screenshots describe the existing app, not proof of demand for your version.

Screenshots

< Scroll to see more >
App Store description

Plug in your audio interface, start the record, and the vocal is on its own fader. STEM splits what is playing — or what is coming in from your mixer — into vocals, drums, bass and everything else, live, on your iPad or iPhone. Each stem lands on its own pair of hardware outputs, so your desk does the mixing. No upload. No render queue. No waiting for a track to be analysed before you can play it. LIVE IN, STEMS OUT Feed STEM from your interface — a turntable through your mixer, a booth output, an instrument — and it separates what is coming in, with the engine aimed at a live source instead of a file. The mix you did not make, taken apart. EVERY STEM ITS OWN OUTPUTS Each stem takes its own pair of hardware channels — vocals to 3-4, drums to 5-6 — up to 16 channels, assigned in a routing matrix that remembers each interface. Outputs start muted until you confirm the routing, because a misrouted stem into a PA is the mistake worth preventing. On a device alone the four stems fold down to stereo, and the console says so. TWO DECKS, ONE CROSSFADER One setting runs a second deck: its own separation engine, its own four stems, its own routing. A crossfader between them, constant-power or cut. HANDS ON THE HARDWARE Map any MIDI CC by tapping a control and moving the knob. Soft takeover means a hardware fader never makes the mix jump, and positions are sent back, so motorised faders and LED rings follow the console. A CONSOLE, NOT A DIALOG Long-throw faders with a 0 dB detent, mute and solo per stem, LED metering, a master strip with BS.1770 loudness. Per-stem three-band EQ and a resonant filter — ladder or state-variable, your choice. Cue any stem to a headphone pair before you bring it up. Save the whole desk as a scene and recall it. SENDS, INSIDE OR OUT Up to four stereo sends, each per stem and post-fader. Send one to a hardware pair for your outboard, or to the built-in tempo-synced delay or plate reverb. STEMS WHILE IT PLAYS Load a track and it comes apart as it plays. Seek anywhere and the stems follow, because the separation is happening now rather than being read from a file somebody prepared earlier. TAKE THE STEMS WITH YOU Write a loaded track back out as four 24-bit WAV files, latency-compensated so they sit at zero in a DAW, rendered by the larger offline model. MEASURED, NOT QUOTED Latency, load and real-time margin are read from the running session and shown while you work. The app never displays a number it has not measured. iPad, iPhone AND Mac Use the console in portrait or landscape on iPad and iPhone. The same app also runs on Apple-silicon Macs. Real-time performance depends on your device and session settings. PRIVACY No accounts, no analytics, no network. Your music never leaves the device. AUV3 PLUG-IN — Load STEM as an effect in AUM: audio in, the remix on the first bus and each stem on its own bus. In a host with one output, such as GarageBand, the first bus plays the remix. PREVIEW AUDIO “Rooted In Peace” by Admiral Bob (ccMixter), with “In Peace” by snowflake. CC BY 3.0. Excerpted and processed by STEM. ccmixter.org/files/admiralbob77/33646 · creativecommons.org/licenses/by/3.0/

Written user reviews are not shown here. Check current App Store reviews >

Opportunities

AI-GENERATED OPPORTUNITY HYPOTHESES

These are generated suggestions, not verified review quotations. Check current App Store reviews and speak with users before treating a possible gap as a requirement.

Build scope

Plan a focused first version with your coding agent. These are planning assumptions, not a delivery guarantee.

Define the first version

Choose one audience and one core workflow. Use the kit to agree on its screens, data, and acceptance criteria before building.

Set boundaries

Decide which secondary features, integrations, and platform support can wait. Your version does not need to reproduce everything in the original.

Check the hard parts

Validate external services, specialist technology, data access, and ongoing costs for your chosen scope.

SUGGESTED BUILD STACK
BUILD KIT DIFFICULTY

Not assessed in a Build Kit yet.

A reliable timeline needs an agreed scope and a technical check. Ask your agent to estimate the phases in BUILD_PLAN.md after that review.