Rivya AI Docs

Rivya Studio Guide

Use Rivya Studio for signed-in Chat, Image, Video, and Audio workflows with uploads, credits, history, notifications, and continuity.

Last reviewed on 2026/08/29

Use this guide when you need to choose the right signed-in Rivya Studio surface for a real task.

Studio is where Chat, Image, Video, and Audio work become account-backed workflows with uploads, credits, saved history, notifications, and follow-up paths.

What Studio Means In Rivya

Studio is not one editor. It is a set of focused workspaces:

  • Chat Studio for planning, reasoning, rewriting, image-assisted analysis, and tool-connected sessions

  • Image Studio for still visuals, reference-led image work, product assets, and ad or landing-page graphics

  • Video Studio for motion, product demo clips, image-guided video, and short campaign assets

  • Audio Studio for available voice, narration, dialogue, music, and sound-sketch workflows; paused sound-effect and cleanup pages remain catalog references

All Studios share the same account, wallet, history, and notification layer.

Start In Chat When The Task Is Still Open

Chat Studio works well when the task still needs thinking.

Use it for:

  • turning a vague idea into a brief

  • comparing possible workflows

  • rewriting a prompt

  • analyzing an uploaded image before generation

  • preparing a campaign asset list

  • using AI Calculator or AI Solver when the job is tool-shaped

A good chat result often becomes a better prompt for Image, Video, or Audio Studio.

Move Into Image When The Deliverable Is A Still

Image Studio is the right surface when the next useful output is a still visual.

Use it for:

  • product photos

  • ecommerce stills

  • landing-page hero concepts

  • paid-social images

  • reference-led product or brand visuals

  • static directions that may later become video

If you cannot review the still image clearly, it is usually too early to animate it.

Move Into Video When Motion Is The Deliverable

Video Studio is for motion, not for making an unclear visual idea feel more advanced.

Use it when:

  • the product action matters

  • a still image already proves the direction

  • a launch teaser needs movement

  • a product demo needs a short clip

  • an image or reference should become motion

Video can cost more and be less predictable than still images. Use it when motion is part of the actual deliverable.

Move Into Audio When The Job Becomes Sound

Audio Studio is the right surface when the output is heard.

Use it for:

  • voice-over

  • narration

  • text-to-speech

  • dubbing or localization

  • short sound sketches, ambience, or loops through an available model

  • cleanup or isolation only when a matching model is marked available; Audio Isolation is currently paused

If audio supports a video, settle the visual direction before finalizing the audio layer. ElevenLabs Sound Effect V2 and Audio Isolation cannot currently create tasks; Suno Sounds is available for new sound sketches but does not repair recordings.

When To Switch Studios

Switch Studios when the project stage changes.

A normal chain might look like:

  1. Chat clarifies the brief.

  2. Image proves the visual direction.

  3. Video animates a useful still or product action.

  4. Audio adds available voice, dialogue, music, or sound-sketch work when the visual direction is ready.

  5. History keeps important outputs available for later reuse.

Do not switch just because another Studio looks more advanced. Switch because the next output type changed.

How Studio Keeps Work Connected

Studio work stays connected through:

  • the same account

  • the same credit wallet

  • saved chat and generation history

  • notifications for important async events

  • task status and result records

  • paths back to model and workflow pages

That continuity is what makes a cross-format project feel like one project instead of disconnected sessions.

Common Studio Mistakes

Avoid these patterns:

  • starting in video when the visual direction is not proven

  • using audio before the script or scene is clear

  • uploading references without explaining their role

  • treating public quick-use pages as saved production workflows

  • ignoring history after a useful result appears

  • switching models before understanding what failed

  • treating a visible but unavailable catalog page as a runnable Studio path

A strong Studio workflow is usually slower at the first decision and faster everywhere after that.