Production engines

What a scene will cost to render, in frames, pixels and units.

Reads a scene and reports what rendering it takes (frames, size, design renders, shot frames, audio seconds) and what it costs here: units, and whether it is within this service's limits (60 seconds, 1920 by 1080, 30 frames a second, 600 units a job). Renders nothing. A shot costs most, because every frame of it is drawn from geometry: the nine-second two-person chase in video_examples is 130 units at 1280 by 720, the eleven-second talking card 7, and the two-second street in a world 30; a street with its crowd drawn costs far more (see video_schema). Costs no units.

post/api/agents/run/video_cost

Request

  • Base URL: https://tomorrowlives.com
  • URL: https://tomorrowlives.com/api/agents/run/video_cost
  • Auth: HTTP bearer

Request body

sceneobject required

A scene document written inline: output (size, frame rate, length), tracks of clips, optional cast and lines, audio and subtitles. Start from video_examples and read video_schema for every key.

Response

The job's result and files

jobstring
verbstring
unitsinteger
msinteger
resultunknown

Changes

No recorded changes to this operation across all 1 revision of this API.