Suno v6 features vs Sume Music: what Sume does and does not do

Sume Music does less than Suno v6 on song-level editing: according to TechCrunch, v6 can edit parts of a song, take text, image and video references, and isolate stems; Sume's Music Router takes a text prompt and one optional image, and returns a finished audio file per job. If your query is "can Sume do what Suno v6 does", the answer is partly: it generates music from text and an image, but it has no part-editing, no stem output and no video or audio reference.

Here is the full list, so you can decide before you build.

Which features line up?

Each row lists a v6 capability as TechCrunch reports it and what Sume documents.

What can you do with the file Sume returns?

Join or cut it. Timeline audio concatenates up to 20 Sume-hosted parts into one gapless file or slices one file into ranges, for a flat $0.01 per job, and a Timeline render can lay a track under a voiceover with gain and ducking. That covers trimming a long track to a scene, though it is not the same as regenerating one section of a song. If a scene needs a different mood halfway, generate two short tracks and join them instead of asking for one track with a hard change inside it.

How is length controlled?

Not by a parameter: duration and duration_seconds are rejected. State the length in the prompt, for example "a 30-second track", and use section markers if you need structure. Check the result's length before you build a timeline around it. The Music 1.0 page lists the hard constraints.

What should I do?

If your workflow needs part-editing or stems, use a tool that offers them and keep Sume for text-to-music beds. If a finished track under a video is enough, a fixed-price Sume job with a stored file is simpler. Whichever you choose, write down the capability you rely on, because a feature missing from your tool is cheaper to discover before a client deadline than during it.