A music editor that keeps the work together

A project should hold the conversation and the actual music. Keep your recordings, alternate versions, processing and exports together so the next session starts from real work.

Try it in your studio

Free to start. No card required.

Step 1

Open the project

Choose the conversation and recordings for this piece of music. Keep unrelated songs in separate projects.

Step 2

Shape the arrangement

Use Simple mode or open Pro controls when you need them. Ask the producer for a specific change and compare it.

Step 3

Save a clear result

Export the version you intend to use, check the player and retain earlier takes for a later decision.

Start with the controls that matter

Simple mode keeps the focus on tracks, transport, recording, undo, analysis and the producer. It is useful when you want to finish a musical task without opening every engineering control at once.

Use Pro mode when you need the wider editing surface, mixer, buses and automation. More controls do not automatically make a better mix; they give you more precise ways to express a decision you can hear.

Make edits you can understand

Keep track names and source roles clear. A dry vocal, an old demo, a reference mix and a generated backing should not be interchangeable just because all four are audio files. Check the selected track before applying an edit.

Use clip timing, trim, gain and fades to build the arrangement. Effects change tone and dynamics; automation makes those changes vary over time. When a parameter is automated, the curve can override the static control you are looking at. Ask the producer to inspect the current settings before changing an established chain.

Keep a route back to the song

Saved conversations and project files let you return to earlier instructions and useful versions. The producer can retrieve earlier project work instead of asking you to upload an existing file again. A saved export remains a separate artifact, so later timeline edits do not silently change it.

Some effects are available in browser playback and local bounce but do not have a cloud-render equivalent. The editor should tell you when the chosen export route cannot reproduce a chain. Keep the complete project and verify the file you actually download, especially before handing it to another person.

Common questions

Is the editor available on every device?

The full timeline editor is a web surface. On smaller screens, the producer conversation and saved-result playback are the practical way to keep working.

Why does a cloud export refuse an effect?

Browser effects and the cloud engine have different supported implementations. Use a supported chain or local bounce when the editor identifies an effect without a cloud equivalent.

Welcome back

Pick up where your producer left off.