Rendering & jobs

Rendering turns lines into takes. You choose which lines, languages and how many takes; Acteme shows the cost, reserves the credits and works through the batch in the background.

Starting a render

There are three ways to start one:

• Selected lines. Tick lines in the Script tab and press Render in the selection bar.
• The whole project. Press Render in the project toolbar and choose which lines.
• One scene. Use the render button on a scene's header to render each line in that scene as its own file.

Which lines

Languages, takes and model

• Languages. In a multilingual project, pick which languages to render. Each language is rendered from its translation with that language's voice. Lines without a translation are skipped and listed in the warnings.
• Takes per line. Up to 10. Each take is a separate performance and costs the same as one line. One take is fine for barks; for hero lines, render three and pick one.
• Model. Character / project default uses the character's model if it has one, and the project's otherwise. Choose Pro or Lite here to override it for this render only.

Cost estimate

As you change options, the dialog shows how many takes will be rendered, their credit cost and your balance afterwards, plus warnings such as lines that can't be rendered. The numbers are exact: the same calculation reserves the credits when you press Render.

If your balance is too low, nothing is queued. Top up or render fewer lines; see Credits & plans.

Jobs

Each render becomes a job, with one item per take. Jobs run in the background, so you can keep working or close the tab. The project shows a progress indicator, and lines fill in with audio as their takes finish.

The Jobs page lists every job with filters for active, problems and finished. Open a job to see:

• counts of done, cached, failed and canceled items;
• credits reserved and refunded;
• warnings recorded when the job was queued;
• items still in flight;
• each failed line with its error.

Job status

Retries and failures

When the speech service is under heavy load or having an outage, affected items wait and retry automatically. The job shows Waiting for capacity meanwhile, and the studio offers a browser notification for when it finishes. Items that still can't be rendered eventually fail and are refunded. Other temporary errors are retried automatically too. Errors that a retry can't fix, like content the model refuses or a voice that no longer exists, fail immediately. Either way, you're only charged for takes that were actually rendered.

Canceling

Press Cancel on a running job to stop it. Items already rendered keep their takes; everything still queued is canceled and refunded.

How many jobs run at once

Each plan can run a fixed number of jobs at the same time; see the plan table. Starting another one while you're at the limit shows which jobs are still running, so you can wait or cancel one.

A single job can contain up to 20,000 lines.

Cached items

Before rendering, every item is checked against the takes you already have. If an identical take exists, its audio is reused and the item's credits are refunded. This typically happens with lines that share text, like barks, and with lines that were deleted and imported again. See Core concepts.

Use Stale and draft for day-to-day renders. It only picks lines whose audio is out of date, so nothing you already approved is rendered again.

How long audio is kept

Rendered audio is deleted automatically once your plan's retention window ends, counted from when it was rendered:

Each take shows its deletion date. When the last take of a line is deleted, the line goes back to draft. Export or sync anything you want to keep before then. Upgrading extends the audio you already have to the new plan's window; downgrading only affects new renders. Rendering a take you already have (a cached item) restarts its window.