Skip to content
LorvaraDocs

Recomposing, and what it costs

Confirming a shot list writes every row’s prompt text. After that, the list is live: editing a row means deciding whether the prompt it already made should be written again.

Why it costs anything

Section titled “Why it costs anything”

Composing runs the Prompt Agent over a row in shot composition, not the Studio conversation: two passes, reading the brief and writing the prompt. That is model work, so it is metered like any other model work, at a flat rate per composed row.

It is worth being precise about what that buys, because the two are easy to confuse:

Press What it does What it costs
Confirm & compose / Save & re-compose Writes prompt text The per-row rate, times the rows composed
Generate, in the Studio Makes the picture or video The model’s own price, which depends on the model, size and duration

Nothing on Scenes & Shots generates anything.

Section titled “The footer”

On a list you have already confirmed, the foot’s button reads:

Save & re-compose 2 changed shots · 30 CR

The count is the list’s own tally of what would actually be composed: a row with no prompt yet, or a row whose source has changed since the record stored it. It is the same comparison the route makes, so the button cannot promise a number the press would not honor.

A change that is not a re-composition still needs saving. Renaming a scene, editing a scene description, dragging a shot, accepting a guess: all of them change the list and none of them changes a row’s source. The button says so: Save the review — nothing to re-compose. With nothing changed at all it reads Save & Recompose · 0 changes and rests.

One card at a time

Section titled “One card at a time”

When you edit a single card among twenty, that card grows its own control:

Recompose Prompt · 15 CR

with a line saying why it appeared: Description changed — not applied yet, or the name of whatever moved on the brief.

The press composes exactly that one row. Other cards’ unsaved edits are neither saved nor composed, which is the point of having it: it is the way to apply one edit without paying for, or overwriting, the other nineteen.

The control appears for two reasons, and says which:

  • the card’s own source changed — its description, mode, duration, cuts or references no longer match what the record was composed from;
  • the brief moved — something this shot names has been edited on the brief since this prompt was composed. The control names the entries.

If neither is true, there is no control. A prompt that already matches its row and its brief is not offered a re-composition it does not need.

Keep, or Replace

Section titled “Keep, or Replace”

Re-composing overwrites a prompt’s text. When that text is something you typed in the Studio, Lorvara stops and asks rather than writing over it.

The whole press is refused (nothing is written) and the list shows a bar naming the prompts and two answers:

  • Keep the Studio version — that prompt is saved with the list but not re-composed. Your text stands.
  • Apply my changes — the shot is composed from its shot line and the result replaces the text it holds.

A prompt that still holds exactly what Lorvara wrote is not protected, because there is nothing of yours to lose. The Studio’s own Recompose asks the same question, and answers it with Replace it anyway.

Batch prompts

Section titled “Batch prompts”

The project page’s Batch prompts block runs the same composition over every prompt on the page, and carries the same price on the button: Compose 6 prompts · 90 CR.

Shot-list prompts land on their records with their references, in their row’s mode. Standalone prompts, ones you wrote yourself, show their composition on the job card only; their own text is not written over. A prompt that fails is reported on its own, never as a failed batch.

Section titled “What to read next”