arcocodes/renoise-plugins-official/model-routing

Renoise Model Routing

Select by task, not by habit. Then prompt for the selected model instead of sending every model the same generic brief.

Hard Boundary

Live model capabilities are authoritative for availability, defaults, input roles, combinations, limits, duration, ratio, resolution, and audio controls. This Skill contains only researched routing preferences and prompting styles.

1. Preserve a model explicitly named by the user, or one you presented as selected in the plan or estimate. If it cannot do the job, explain why and the replacement you propose, and switch only after the user agrees.
2. Filter candidates by the live capabilities required by the task.
3. Route only to the newest live generation of a model family; older generations remain available only when the user explicitly names one.
4. Choose the best specialist below.
5. Use the live isDefault model only when no specialist clearly fits or candidates tie.
6. Inspect the selected model's live guidance before writing the final prompt.
7. Let the selected model's profile override generic prompt-craft advice when prompt structure, density, or reference wording conflicts.
8. Never pass a role or parameter merely because this guide mentions a public model capability; the Renoise deployment may expose a narrower contract.

Live availability alone is not a routing recommendation. Omit older generations, fully dominated models, and models without a clear task advantage; an explicitly named model still follows rule 1.

References and Edits

• Keep the authoritative identity or product references across iterative edits: send them in every related task alongside the latest composition or edit source, state each reference's job, and never treat a transformed intermediate as the replacement. When a reference limit forces a choice, keep the original anchor.
• For an edit or continuation, keep the source's aspect ratio when the model supports it; analyze the source when the ratio is unknown, and follow the model's live guidance for source-following ratios.
• Before generating with references, check every requirement the live capabilities state (format, duration, size, count) against what analysis or metadata shows. A source that breaks one would be rejected: convert or trim it with code first.

Routing Questions

Classify the request before selecting:

• Kind: image, video, or audio.
• Operation: create, edit, continue, interpolate, animate a reference, or upscale.
• Priority: final quality, strict instruction following, aesthetics, identity consistency, speed, or cost.
• Structure: exact text/layout, one cinematic shot, multi-shot narrative, dialogue performance, music, or a complete audio scene.
• References: none, one source image, several identity/style references, source video, endpoint frames, or voice/audio references.

Do not call a model “best” without naming the task it is best for.

Image Routing

Decision Order

Image Prompting Styles

GPT Image 2.6 — production brief

For complex production briefs, use labeled, ordered instructions:

USE: [ad / packaging / UI / infographic / edit]
SCENE/BACKGROUND: ...
SUBJECT: ...
COMPOSITION: ...
LIGHTING/MATERIALS: ...
EXACT TEXT: "..." with placement, hierarchy, font character, and color
PRESERVE: identity, geometry, layout, logo, and all unmentioned elements
CHANGE ONLY: ...
AVOID: ...

• Route a generic GPT Image request to GPT Image 2.6 Sunburst; use Flare when explicitly requested. Neither live contract supports mask inpainting.
• For a GIF, describe the motion across the loop (what moves, from where to where, and how it returns to the first frame); keep the subject and background stable so the frames read as one shot.
• Put literal in-image text in quotes and specify hierarchy and placement.
• For image-to-image transformations, say change only X; preserve everything else.
• Identify every reference by its job: source, identity, product, layout, or style.
• Prefer one-change iterations over rewriting the whole brief; do not promise mask inpainting.

Nano Banana 2 — conversational creative direction

[Subject] + [action] + [location] + [composition] + [style]
Camera/viewpoint: ...
Lighting/materials: ...
Exact text: "..."
Keep unchanged: ...

• Start with a clear operation verb and use positive, concrete natural language.
• For references, state each source's job, the relationship among them, and the new scenario.
• For edits, separate the requested change from what remains unchanged; repeat preservation requirements on later turns.
• Quote exact visible copy and specify its hierarchy, placement, visual character, and localization target.
• Relate multiple references explicitly and iterate conversationally.

Seedream 5 — design brief

Put the deliverable format first, then subject, layout, light, exact text, and invariants:

[DELIVERABLE FORMAT and ratio/use case]
Subject and setting: ...
Layout and spatial relationships: ...
Lighting, materials, and palette: ...
Exact visible copy: "..."
Keep exactly: ...

• Pro: specify dense layout, multilingual copy, materials, local edit regions, and everything the edit preserves.
• Lite: natural language works well; make causal/spatial relationships explicit for complex transformations.
• Assign each reference a clear role and avoid vague pronouns in multi-reference edits.

Midjourney — aesthetic visual phrase

Use a concise visual description, not a requirements document:

[subject], [medium], [environment], [lighting], [palette], [mood], [composition]

• Prefer concrete visual nouns and adjectives over keyword spam.
• Name the lighting and composition that matter instead of relying on “cinematic.”
• Use Midjourney for look development rather than text-heavy layouts or surgical edits.

Grok Imagine Image — concise scene direction

[subject doing action] in [setting], [camera/framing], [lighting], [material/style]

• Use standard for lower-cost iteration and Quality when the higher-quality tier is worth the added cost.
• For edits, attach the source image or images and describe the requested change directly.
• Keep the prompt concrete enough that the main subject and action remain dominant.

Video Routing

Decision Order

Tier and version notes