About Cue

What Cue is

Ask anything about your track. Cue replies in plain language and gives you a visual answer: EQ curves, compressor settings, reverb envelopes, synth patches, chord progressions you can hear. Calibrated to your genre, BPM, and key.

Every guide on /learn renders from the same data Cue uses inside the chat. The shape that drives a kick-drum EQ visualization in a chat reply also renders the visualization on the guide. One source of truth, two surfaces.

What Cue isn't

Not a co-producer. Doesn't generate finished music. Doesn't make creative decisions for you. Honest about being an AI: no fake history, no studio credits, no roleplaying as a famous engineer.

You stay the artist. Cue is the thinking partner.

How the guides are written

Concrete starting points, not exhaustive references. Specific values you can dial in immediately, and the reasoning behind them. When something genuinely depends on context, we say so and explain the trade-off.

Every guide shows its last-updated date. If a recommendation is outdated or wrong, email us and we'll fix it.

Built by Isaac

I built Cue because I kept watching the same pattern. A producer hits a wall, opens Google, twelve tabs later still doesn't have an answer that fits their track, and reaches for a music generator instead. Not because the shortcut is what they wanted. Because the slow path lost.

Cue is an attempt to make the why arrive as fast as the generated track. So when musicians get stuck, learning stays an option.

Independent developer and music producer based in Sweden. Cue ships frequently. Feedback, bug reports, and feature requests: hello@startcue.io.

Privacy

PostHog for product analytics. EU, UK, and Swiss visitors see a consent banner before anything fires. No conversation content is sold or used for training outside the request itself. Full details in the privacy policy.