Rivya AI Docs

Rivya AI Music Workflow Guide

Choose Rivya music workflows for Suno Music drafts, sounds, lyrics, Extend Music, Vocal Separation, WAV conversion, and Studio history.

Last reviewed on 2026/04/28

Use this AI music workflow guide before you choose between a playable song draft, a short sound sketch, lyric-first ideation, or follow-up actions in Rivya.

The easiest way to get music wrong in Rivya is to assume every music-looking model does the same job.

It does not.

The current music branch is live, but it is intentionally split into three different starting points.

This page is the workflow reference for Rivya's current music branch. If you want the more decision-oriented guide about how to start the first real music task, How to Create AI Music with Rivya is the better paired read.

Start With What You Need First

Before you choose a music model, decide what has to exist first:

  • a playable song draft
  • a short sound sketch, loop, or ambience idea
  • lyric options before any audio is generated

That first decision usually matters more than the model brand itself.

What the Current Music Branch Includes

Today, the live music branch is built around:

Those are all real live entries, but they are intentionally narrow. Rivya is exposing the smallest stable subset instead of pretending the whole music-production stack is already here.

Suno Music Is the Song-Draft Path

Suno Music is the right first move when you want a playable track draft from one brief.

That makes it the better fit for:

  • first songs for videos, demos, or podcasts
  • instrumental-first drafts
  • rough music concepts that need to sound like a real track, not just an idea

You can decide whether the run should be instrumental, and successful results can continue into Extend Music.

On the result side, the current product also exposes WAV conversion and vocal separation as follow-up actions.

Suno Sounds Is the Short Audio Sketch Path

Suno Sounds is more useful when you need one short sonic idea rather than a song structure.

That usually means:

  • ambience beds
  • background textures
  • loop ideas
  • environmental or tonal sketches

It is the better path when BPM, key, or looping matter more than verses, chorus structure, or whether a track should have vocals.

Successful results can continue into Vocal Separation.

Suno Lyrics Is the Words-First Path

Suno Lyrics is the right entry when the first problem is lyrical direction, not audio output.

Use it when you want to test:

  • title ideas
  • hooks
  • verse direction
  • chorus shape

The important boundary is that it returns structured text cards, not playable media. That makes it the better start when you want to pressure-test the words before you spend on a track run.

Follow-Up Actions Matter Here

The music branch is not only about the first generation. The result-based actions are part of the workflow too.

Right now, the practical rule is:

  • Extend Music is the follow-up path for successful Suno Music results
  • Vocal Separation is available from successful Suno Music or Suno Sounds results
  • WAV conversion is currently exposed as a follow-up on successful Suno Music results

Those are actions on successful results, not separate standalone model pages.

When This Is the Wrong Branch

This is not the best place to start if the real job is:

  • spoken narration or voice-over
  • multilingual speech
  • multi-speaker dialogue
  • cleanup of an uploaded recording

Those tasks belong to the broader Audio Workflows in Rivya page instead.

Public Pages vs Studio

Use the public music-facing pages when you want:

  • a first catalog pass at /audio
  • a side-by-side comparison in AI Models
  • a model-first start from a detail page

Move into Studio when the work becomes a real saved workflow:

  • repeated iteration
  • account-backed execution
  • result follow-up actions
  • history you want to keep using

That is the normal transition once the first result is no longer just a test.

A Fast Way to Choose

If you want the shortest reliable decision path:

  1. choose Suno Music if you need a playable song draft
  2. choose Suno Sounds if you need a short sonic sketch, loop, or ambience layer
  3. choose Suno Lyrics if you need words before audio
  4. treat follow-up actions as part of the workflow, not as an afterthought

That is usually enough to keep the first run focused.

Music Workflow Checklist

When the audio task becomes song, sound sketch, or lyrics work, check:

  • Decide whether the next output should be a full music draft, a sound texture, or structured lyrics.
  • Use Suno Lyrics when words and song structure need testing before audio spend.
  • Use Suno Sounds for short sound sketches, ambience, or practical audio layers.
  • Use Suno Music when the task is a playable song draft rather than general voice work.
  • Keep music expectations separate from voiceover, dialogue, and cleanup tasks.

Recheck Before Calling It A Music Suite

Recheck when the task expects deep DAW-style production, full mastering, stem editing, or music-only workflow depth. Rivya has live music paths, but it is not positioned as a deep music-only suite.

Table of Contents