Suno Studio

I designed this independent Suno concept around a specific editing problem: a producer likes the track but wants to change the drums in the chorus. The change should affect one instrument, in one section, while keeping the rest intact.

Define where the change belongs

A broad prompt leaves a lot open to interpretation. I centered the concept on a selection that combines a section and a part: chorus and drums, for example. Establishing that scope first would give a producer a clearer way to describe what they want and judge what comes back.

Work with the structure of a track

I used a digital audio workstation as the starting point because its arrangement of sections and layers gives an edit context. A request such as “simplify this drum groove” belongs somewhere in the composition. The design question was how to make that relationship visible while keeping the surrounding track available as a reference.

Say what should stay the same

Choosing where to edit is only part of the request. A producer may want a different instrument with the same rhythm, or a new bassline that follows existing chords. Those examples helped define the direction: the boundaries of a change deserve as much attention as the change itself.

The interface leaves a technical question open

The result is an interface concept, not a validated editing system. I have not established whether a model could reliably make these changes while preserving everything outside the selection. That would be the next thing to test, alongside whether producers can predict the scope of an edit before they run it. The exercise clarified the problem I want to pursue: helping someone develop a track through small, deliberate changes they can trust.