Skip to Content
Starlight

Export video

Export renders your scene to video files: one file per surface (one LED output), at the surface's full resolution. To render means to draw every frame and save it.

There are four ways to export:

  • the whole scene, with the export sheet (⌘E / Ctrl+E)
  • one surface, from the surface's right-click menu
  • the whole scene until its song ends
  • the reel: every scene of the show, one after another

The File menu and the command palette have the scene, song and reel exports.

Export a scene ⌘E / Ctrl+E

This exports the open scene. Each surface that is ticked becomes its own file.

  1. Press ⌘E / Ctrl+E, or choose File › Export Scene…. The export sheet (a small window) opens.
  2. Under format, click a format (Formats).
  3. Under fps, click 30 or 60 (Frame rate).
  4. Under motion blur, keep off, or click a shutter, for example 180° (Motion blur).
  5. Under surfaces, untick any surface you do not need.
  6. Under size, keep surface, or click design for a master at the artboard's size. size shows only when a ticked surface's artboard has another size than the surface (Export a master at the plate's size).
  7. Under length, keep own loop (each surface loops on its own length), or click scene loop (every surface has the same length) (Each surface's own length).
  8. Under destination, keep renders/<scene>/ or click choose… (Destination).
  9. Press ⏎ / Enter, or click export.
Part of the sheetWhat it shows
export · <scene>The title. On the right, the scene's own frame rate, for example renders at 30.
formatEvery format, with its file type and alpha when it keeps transparency. It reads probing ffmpeg… while Starlight checks what this machine can write.
fpsThe delivery frame rate, and interpolate when the rate differs from the scene's.
motion bluroff, or the shutter: 90°, 180°, 270° or 360°. When it is on, samples (4, 8, 16 or 32) and how much longer the export takes, for example each frame renders 8 times (about 8× the render time).
surfacesEvery surface with its size, and how many are ticked, for example 4/6.
sizesurface (each file at the surface's LED size) or design with its size, for example design (3840×2160). Only when a ticked surface's artboard has another size than the surface.
lengthown loop or scene loop. Under it, how long each surface's file will be, for example N 10 s · E1 14.53 s · S 17.2 s, and why a surface keeps the scene loop.
mediaThe file check. It reads checking…, then all files ready, or how many files cannot render. Then it lists those files, the layers that use them, and render anyway (When a file cannot render).
destinationThe folder, choose… and reset. Under it, the first file's name, and +5 for the other surfaces. If files with these names are already there, a yellow line says so, for example replaces 2 files: opener_N_…_hevc10.mp4, …
the bottom line⏎ export · esc cancel, or the reason you cannot export yet. Then the export button. When files will be replaced, the button reads replace… (Replace an older export).
  • When the export ends, Finder (Explorer on Windows) opens on the first file.
  • Esc, or a click outside the sheet, closes it without exporting.
  • Pressing ⌘E / Ctrl+E again inside the sheet also exports.
  • While the sheet is open, other single keys do nothing. They cannot change the canvas behind it.
  • export is greyed when no surface is ticked, when this machine cannot write the format, or when a file cannot render and render anyway is not ticked.
  • When you click export, the sheet remembers your choice for this project: format, fps, interpolate, motion blur, the ticked surfaces, the length and the folder. It does not remember size: the sheet always opens at surface.
  • The sheet does not open while an export runs.
  • When a file is already there, the first press of replace… (or ⏎ / Enter) only asks: press again to replace 2 files. Press again to export.
  • A greyed format reads unavailable: this machine cannot write it. Point at it to see why. Point at any other format for a short description.
  • A badge on a format names the hardware encoder (the chip that compresses the video): videotoolbox, nvenc, amf or qsv (Encoders).

Each surface's own length

Each surface's file is its own loop. A surface that plays a 10-second clip gets a 10-second file. A surface that plays a 17.2-second clip gets a 17.2-second file. When a media server (or Glimpse) starts the files together, each surface loops on its own length, as on the canvas.

Starlight finds the length of each surface like this:

  1. It looks at everything on the surface that moves. Things that do not move do not count.
  2. A looping clip repeats after its own length. Keyframes repeat with their clock. A trimmed clip, and a layer that shows for only part of the loop, repeat with the scene loop.
  3. The surface's length is the longest of these, when every other one fits into it a whole number of times. For example, a 2-second pulse and a 10-second clip make a 10-second surface.
  4. The length must also be a whole number of frames. For example, 14.53 seconds at 30 fps is 436 frames.
  • Otherwise the surface keeps the scene loop. The sheet says why, for example: N keeps the scene loop. N mixes a 10 s video (n.mp4) with the text "GOAL" animated over 17.2 s. To fix it, give the title its own 10-second clock, or cut the clip to the loop.
  • Music, and an effect that never repeats, also keep the scene loop.
  • A surface where nothing moves keeps the scene loop.
  • Click scene loop in the sheet when every surface must have the same length, for example for a media server that restarts all surfaces together.
  • Do not change the scene's length to give one surface another length. That changes the scene for everyone.
  • The reel and the full-track export always use the scene loop on every surface.
  • Each file carries the scene's sound only for its own length. When a surface is shorter than the scene loop, the end line says so. Click scene loop to keep the whole sound on every surface.
  • Glossary: a loop is the time after which a file starts again. A period is the time after which one thing repeats.

When a file cannot render

Before an export draws its first frame, Starlight checks every file that the exported surfaces use. If a file cannot render, the export does not start. Starlight names every such file, with the scene and the layer that use it. So a missing picture never becomes a hole in a delivered file without a word.

The list saysWhat it meansDo this
missingThe file is not in the project. It was deleted, renamed or moved.Put it back at its path, or change the layer (Find missing media).
online-onlyThe file is in Dropbox, but not on this machine. Or Starlight has not finished checking its folder in Dropbox yet.Make it available offline (Online-only files). If the folder is still being checked, wait a moment and export again.
cannot be readThe file is there, but Starlight cannot open it on this computer. The file is damaged, or this computer cannot decode its format. The list gives the reason, for example this computer cannot decode HEVC video.Export the file again from its app, then import it again. For HEVC: export on a computer that can decode HEVC.
no cutoutThis machine cannot remove the background of the photo (Cutouts).Export on a Mac with the Xcode Command Line Tools.
no transparencyThis machine cannot decode the transparency (alpha) of the clip. The clip would render as a box.Export on a Mac, or export the clip again as ProRes 4444 or a PNG sequence and import it again.
  1. Press ⌘E / Ctrl+E. Under media, the sheet lists the files.
  2. Fix the files. Then press ⌘E / Ctrl+E again.
  3. Or tick render anyway, then click export. Each file in the list renders as an empty spot.
  • Only the ticked surfaces count. A file that only a surface you do not export uses does not stop the export.
  • Sound counts for every surface. An image sequence has no sound, so its audio files are not checked.
  • A cutout that fails never renders as the full photo. With render anyway, its spot is empty.
  • Starlight never remembers render anyway. You choose it again for each export.
  • The export from a surface's menu, the full-track export and the reel have no sheet. When one stops, the line at the bottom names the files. Click show files to see each file with its scene and layer. Click render anyway to export again with empty spots.
  • The reel checks every scene before the first scene renders. So a problem in the last scene stops the reel at the start, not at the end.
  • A finished export with problems never reads as a plain success. The line ends with, for example, WARNING: 2 files rendered as empty spots: missing: hero.png, logo.png.
  • Claude's export_scene, export_scenes and export_reel stop in the same way and list the files. They render anyway only with allowMissing: true (MCP).
  • A Glimpse publish stops too, before it exports a surface. Fix the files first (Publish).

Pick a format

Each format suits a different job. Alpha means the file keeps transparency. The table follows the order in the sheet.

FormatFilePictureAlphaUse it for
H.264.mp48-bit, 4:2:0noPreviews and show control systems.
HEVC 10-bit.mp410-bit, 4:4:4 (best) or 4:2:0 (compatible)noThe file a media server plays. Servers play HEVC on the GPU (the graphics chip). The default on Windows. Pick the quality under quality (HEVC quality).
ProRes 422 HQ.mov10-bit, 4:2:2noThe master file that you colour-correct, edit and keep. Also for servers that want ProRes. The default on a Mac.
ProRes 4444.mov10-bit, 4:4:4, 16-bit alphayesOverlays that need transparency.
HAP Q.movdecoded on the GPUnoOnly when a media server asks for HAP.
PNG sequencea folder of .png8-bit RGBAyesSingle frames for compositing and visual effects (VFX) apps.
EXR sequencea folder of .exr32-bit float RGBno32-bit float frames (RGB) for VFX.
  • Send HEVC to the media server. Keep ProRes or EXR as the master.
  • Use H.264 for previews only. Hardware H.264 players cannot play more than 4096 px.
  • 4:2:0 keeps the colour at half the width and half the height of the picture. 4:4:4 keeps the colour for every pixel. On an LED wall, small red or blue text can look soft in 4:2:0. In 4:4:4 it stays sharp. The file is a little bigger.
  • H.264 is the default when this machine cannot write the platform's default format (HEVC on Windows, ProRes on a Mac).
  • You can still pick ProRes on Windows. It runs on the CPU there, so it is about half as fast as HEVC, and the computer is busy while it runs.
  • A video needs an even width and height. When a surface's size is odd, Starlight adds one black column or row at the right or bottom. HAP Q pads to a multiple of 4. Image sequences keep the exact size.
  • Video files are marked as Rec.709 colour.
  • A project can set its own default formats (Project defaults).

HEVC 10-bit and the encoders

An encoder is the program that compresses the frames into a file. Starlight picks the fastest encoder this machine has.

FormatMacWindows
HEVC 10-bitVideoToolbox (the Mac's media engine). An option, not the default.The GPU encoder: NVENC, AMF or QSV, in that order. Without one, libx265 on the CPU (slow). This is the default.
HEVC 10-bit 4:4:4libx265 on the CPU (slow). VideoToolbox cannot write 4:4:4.NVENC (NVIDIA graphics cards). Without it, libx265 on the CPU (slow).
ProRes 422 HQVideoToolbox when this machine's ffmpeg has it, else the CPU. This is the default.The CPU (slow)
H.264, ProRes 4444, HAP Q, PNG, EXRThe CPUThe CPU
  • On Windows, each GPU encoder must first pass a short test encode. If the test fails, Starlight tries the next one. HEVC and HEVC 4:4:4 have separate tests, because some graphics cards can write HEVC but not HEVC 4:4:4.
  • A surface longer than 8192 px on either side skips NVENC, AMF and QSV. It uses libx265.
  • No HEVC encoder takes a surface longer than 16384 px. The export stops before it starts and names the limits.
  • Media servers also stop at 16384 px. This is why every surface gets its own file.
  • HEVC files have a complete frame every second, so a server can jump to any second. A 4:4:4 file uses the RExt profile. A 4:2:0 file uses Main 10.
  • HEVC files carry the hvc1 tag, so QuickTime can open them.
  • The sheet warns you when a surface is too big for the encoder. It says, for example: <surface> is over <encoder>'s 8192 px — falls back to the next encoder.
  • It also warns you when HEVC or HEVC 4:4:4 runs on the slow libx265: libx265 is software — slow at 6400 px.
  • To see the encoder for any format, hold the pointer over the format in the sheet. A GPU encoder also shows as a small label next to the format name, for example nvenc.

HEVC quality: best, compatible, draft

When you pick HEVC 10-bit, the sheet shows quality. Click one of three presets. The one you click is highlighted.

PresetPictureUse it for
best · 4:4:410-bit, 4:4:4, quality 12, adaptive quantisation (AQ) 8The default. The master for the media server, and for a second encode (for example NotchLC). Fine colour edges and dark areas stay clean.
compatible · 4:2:010-bit, 4:2:0 (Main 10), quality 12, AQ 8Older players, QuickTime and some media servers. They cannot play 4:4:4.
draft10-bit file, 4:4:4, quality 20; 8-bit clips, no ditherDraft: fast, 8-bit, for reviews. Starlight reads each clip's 8-bit working file, not its deep file. On a Windows PC a surface of four 10-bit clips exported about 60 % faster than best. The file is smaller. Its name ends in -draft, so it never replaces a best file.
  • Draft is for reviews, not for the show. Its clips are 8-bit, so a slow, dark gradient in a 10-bit clip can show steps. It has no dither, so the sheet hides the dither box for it. Use best for the files you deliver.
  • Under the presets you can type a quality number from 1 to 51. A lower number is better and makes a bigger file. Leave it empty to use the preset's number, which shows in grey. You can also type the AQ strength, 1 to 15. AQ keeps fine texture in dark areas. The sheet remembers both. Click another preset to start again from its numbers.
  • Some encoders cannot write 4:4:4: AMD (AMF), Intel (Quick Sync) and the Mac (VideoToolbox). There, best and draft make a 4:2:0 file on the GPU. The sheet says so in one line, and the export result says so too.
  • A 4:4:4 file ends in _hevc444, a 4:2:0 file in _hevc10. When an older file of the other kind is there, the sheet says that it stays, for example This export writes …_hevc444.mp4; the old …_hevc10.mp4 stays.
  • A Glimpse publish never uses a 4:4:4 file, because browsers cannot play it. It renders its own movie.
  • A project can set its own quality in project.yaml (Project defaults). Claude can set it for one export.
  • Each level wins over the one before: the app default, then project.yaml, then the sheet, then one Claude export. A Claude export starts from your last choice in the sheet. A different preset starts again from its own values.
  • The diagnostics log shows the settings and the full ffmpeg command of each export (Export diagnostics).

16-bit frames and the dither

HEVC 10-bit, HEVC 10-bit 4:4:4, ProRes and EXR files keep more than 8 bits of colour. For these formats, Starlight renders each frame with 16 bits for each colour, and sends these frames to the encoder. A slow, dark gradient then keeps all its steps. On a dark LED wall, the steps of an 8-bit gradient can show as bands.

  • H.264, HAP Q and PNG keep 8 bits. They get 8-bit frames, as before.
  • The dither. The encoder rounds each pixel to a 10-bit level. In a very slow gradient, this rounding can still make soft bands. The dither adds a very small, fixed pattern before the rounding: less than half of one 10-bit level in the brightness and in each colour channel of the file. The edge of each band then becomes a fine mix of the two levels, and the eye sees a smooth gradient. It works for coloured gradients too, for example a dark red haze.
  • The dither is on for HEVC 10-bit and ProRes. It is off for EXR, because EXR stores float values and is not rounded to 10 bits.
  • To turn it off or on: in the sheet, untick or tick dither (10-bit). The sheet shows it only for HEVC and ProRes, and remembers it. A project can set it in project.yaml (dither: false, Project defaults). Claude can set it for one export.
  • Each level wins over the one before: the app default, then project.yaml, then the sheet, then one Claude export. The export result and the log show the dither that was used.
  • The dither never changes black or full white. An LED that is off stays off.
  • The pattern is the same in every frame and in every export. Two exports of the same scene are the same. When a surface renders in parts on several workers, the parts meet with no seam.
  • The colours do not change. Black, white and every grey are the same as in an 8-bit export.
  • If the graphics card cannot render 16-bit frames, Starlight renders 8-bit frames, and the export result says why. The export still finishes.
  • A clip with more than 8 bits, or with 4:4:4 colour, is read from its deep file (Video ingest and proxies). A surface that renders in parts on several workers decodes each clip the same way in every part. A computer decodes at most 8 deep files at once. When the clips of one surface would need more than that on all the workers, the export uses fewer workers, and the result says why. A draft reads the 8-bit working files instead.
  • A 16-bit frame is twice the size of an 8-bit frame. With the dither, a 6400 × 1600 frame takes about 60 ms longer to render. The encoder is usually slower than that, so the export often takes no longer.
  • EXR files hold 1.0 for white. The values are the colours the surface shows (BT.709), not linear light.
  • The diagnostics log names the frames of each ffmpeg run, for example 16-bit frames, dithered.

Deliver at another frame rate

The scene always renders at its own fps (frames per second). The sheet can deliver the file at another rate.

  1. Press ⌘E / Ctrl+E. The sheet's header shows the scene's own rate, for example renders at 30.
  2. Under fps, click the rate you need.
  3. For smoother motion, tick interpolate. It shows only when the rates differ.
  4. Press ⏎ / Enter.
  • Without interpolate, frames are copied or dropped. This is fast. A line says so, for example 30 → 60 by duplicating frames.
  • interpolate creates new frames between the frames. It is slow: several minutes for each 6400 px surface.
  • interpolate does not work with formats that keep alpha. With ProRes 4444 or PNG it is greyed.
  • The sheet offers 30 and 60. It also offers the project's own rate, if project.yaml sets one (Project defaults).
  • The first time, the sheet picks the rate from project.yaml. Without one, it picks the scene's own rate when that is 30 or 60, and otherwise 30.
  • The file has exactly the right number of frames for the delivery rate, so it still loops cleanly.

Motion blur

On a big LED wall at 50 or 60 fps, fast motion can look like it jumps from place to place (strobing). Motion blur smears each moving thing along its path during the frame, as a camera with an open shutter does, and as After Effects' motion blur does. It is for exports only: the canvas never shows the blur. With motion blur on, the exported file looks different from the canvas on purpose.

  1. Press ⌘E / Ctrl+E.
  2. Under motion blur, click a shutter. 180° is the usual choice (After Effects' default).
  3. Under samples, keep 8, or click more for a smoother blur.
  4. Press ⏎ / Enter.
  • Shutter: how much of each frame the shutter is open. 180° is half the frame, 360° the whole frame (the longest blur), 90° a quarter. The shutter is centred on the frame, so a frame shows the moment it shows on the canvas, in the middle of its blur.
  • Samples: how many moments Starlight renders and averages for each frame. More samples make a smoother blur. Fewer samples can show a fast thing as a few faint copies.
  • It costs render time. Each frame renders once for each sample: with 8 samples, the render takes about 8 times as long. The sheet says so under the row. While the export runs, its progress window has a blur line, for example 180° · 8 samples · each frame renders 8 times, and the line after the export names it. The progress still counts the file's frames, and its time left is measured as it goes.
  • It is off by default. A project can turn it on for every export in project.yaml (motionBlur, Project defaults). The sheet's choice wins over it, and the sheet remembers it.
  • export <surface> (Export one surface), Export Scene — Full Track Length and the reel use the sheet's last choice too. Claude's exports do not: Claude turns it on only for an export that asks for it.
  • The canvas, the stills Claude takes, the scene list pictures and the colour checks never blur. A Glimpse publish never blurs either.
  • A video clip keeps its own frame for the whole frame: a filmed clip already has its own motion blur. A pre-rendered node renders live, with the blur (unless the export uses the pre-render files: those hold their frame, as a video does).
  • The blur is worked out with 16 bits for each colour, then the frame is made 8-bit (H.264, HAP Q, PNG) or 16-bit (HEVC, ProRes, EXR) as the format needs. Soft edges keep their colour.
  • A file that loops seamlessly stays seamless: the blur of the first frame continues the blur of the last frame. Any other file (an animation that plays once, Full Track Length, the reel) holds its first and last moments, as After Effects does at a comp's start and end: the first frame blurs only forward, and the end never shows through it. When a surface renders in parts on several workers, the parts are the same as one whole export.
  • If the graphics card cannot render with 16 bits, the export still finishes, without motion blur, and the line after the export says so in yellow, for example motion blur off on N: ….

Choose where the files go

By default the files go to the project's renders/ folder. You can pick another folder, for example a shared folder on the media server.

  1. Press ⌘E / Ctrl+E.
  2. Under destination, click choose… and pick a folder.
  3. Press ⏎ / Enter. The files go into <folder>/<scene>/.
  • Click reset to go back to renders/. reset shows only when you chose a folder.
  • A long path is shortened with … at the start. Point at it to see all of it.
  • Starlight refuses a folder inside the project, other than renders/. Files there would become part of the project's versions.
  • In a shared project, Starlight refuses any folder inside the shared folder.
  • export <surface>, the full-track export and the reel use the same folder. The reel goes into <folder>/reel/.

Where the files land

Each file name says the scene, the surface, the size, the delivery fps and the codec.

renders/<scene>/<scene>_<surface>_<W>x<H>_<fps>fps_<codec>.mp4     # or .mov
renders/<scene>/<scene>_<surface>_…_png/                          # an image sequence: one folder per surface
renders/reel/reel_<surface>_<W>x<H>_<fps>fps_<codec>.mp4         # the reel
renders/previz/<scene>/…_h264.mp4                                      # a Glimpse publish
  • <surface> is the surface's name (surfaces: in YAML).
  • <codec> is h264, hevc10, prores422hq, prores4444, hapq, png or exr. H.264 and HEVC are both .mp4, and ProRes and HAP Q are all .mov. The codec in the name keeps each format in its own file.
  • Files you exported before this change keep their old names. Starlight does not rename or replace them.
  • While a surface renders, its file is a hidden file that starts with .~, for example .~opener_N_…_hevc10.partial.mp4. It gets its real name only when it is finished. So a media server never plays a half-made file, and Dropbox never uploads one: Dropbox does not sync files whose names start with .~.
  • A space in a name becomes -. So do / \ : * ? " < > |.
  • The sheet shows the first file's name under destination, before you export.
  • Starlight never saves renders/ in the project's versions.
  • In a shared project, renders/ is in the shared folder, as in a local project. The files sync to the other artists. A 6400×1600 HEVC surface is about 100–200 MB, so a whole room is about 1 GB in everyone's Dropbox.
  • Only a Glimpse publish's videos and the pre-renders stay on this computer, in Starlight's folder.
  • Renders from Starlight 0.2.34 or older. In a shared project they went to Starlight's folder on each computer, and they are still there. Starlight does not move them. On Windows: %APPDATA%\Starlight\projects\<project>\renders\. On a Mac: ~/Library/Application Support/Starlight/projects/<project>/renders/. <project> is the project's name and a short code, for example room-4afeae. Settings › Project › how you work has a button that opens Starlight's folder for the project; the old renders are in its renders folder. To share an old render, move it into the project's renders/ folder. Leave .prerender and previz where they are.
  • To match the names in the media server's pixel map, change the template (Project defaults).

Export a master at the plate's size

A surface's file is the surface's LED size. Sometimes you need a bigger file, for example a 4K master for the client. You do not need a new surface for it. The export can draw the surface at another size.

Example: the scene's artboard is 3840×2160 (the size of the plate video). The surface is 1920×1080, and its fit is fill. The surface plays at 1920×1080. The master can be 3840×2160.

  1. Press ⌘E / Ctrl+E.
  2. Under size, click design (3840×2160).
  3. Check the file name under destination. It has the new size, for example reviews_main_3840x2160_30fps_hevc444.mp4.
  4. Press ⏎ / Enter.
  • Starlight draws every frame at the new size. It does not make the small file bigger. Text, shapes and SVG pictures are sharp at the new size. Videos and pictures use their full files. A blur or a feather looks the same as on the surface.
  • design works when the surface's fit is fill, cover or contain, and the artboard has the surface's shape. With fit none or a tile fit, the artboard is not the surface's picture, so the export stops and says why. Untick that surface, or export it at surface.
  • A surface whose artboard is its own size stays at its size.
  • The bigger file uses the same format, quality, 16-bit frames and dither as a normal export.
  • The largest size is 16384 px on a side. Your graphics card or the encoder can have a smaller limit. Then the export stops before the first frame and says the limit.
  • The sheet does not remember size. The other exports (one surface, to the end of the song, the reel) and a Glimpse publish always use the surface's size.
  • Claude can export any size of the surface's shape with size, for example size: "design" or size: "3840x2160" (The MCP tools).

Set export defaults for the project

An export: block in project.yaml sets the defaults for everyone who opens the project (project.yaml).

export:
  formats: [hevc, prores422hq]
  fps: 60
  naming: "{scene}_{surface}_{w}x{h}_{fps}fps_{codec}"
  aliases: { north: N, stage: STAGE }
  quality: { preset: best }
  dither: true
  motionBlur: { shutterAngle: 180, samples: 8 }
KeyWhat it sets
formatsFormats in order of preference. The first one this machine can write is the default. Ids: h264, hevc, prores422hq, prores4444, hapq, png-sequence, exr-sequence. prores also works: it means prores422hq.
fpsThe default delivery rate: 24, 25, 30, 50 or 60.
namingThe file name template. Tokens: {project} {scene} {surface} {w} {h} {fps} {format} {codec}. It must contain {surface}. It is a file name, so it cannot contain / or \. The default is the one in the example above.
aliasesOther names for surfaces in {surface}, for example north: N.
qualityThe HEVC quality (HEVC quality). preset: best (the default), compatible or draft. Fields that change the preset: chroma (444 or 420), quality (1–51, lower is better), aq (true or false), aqStrength (1–15), maxrate (auto, or Mbit/s), gop (seconds between complete frames), bframes (0–4). A wrong value stops the export, and the message says which value is wrong.
ditherThe dither of the 16-bit frames: true or false (16-bit frames and the dither). Without it, the dither is on for HEVC and ProRes and off for EXR. Another value stops a HEVC, ProRes or EXR export, and the message says so.
motionBlurMotion blur for every export (Motion blur): true (a 180° shutter, 8 samples), false, or { shutterAngle, samples } (the shutter more than 0 and at most 360 degrees, 2 to 32 samples). Without it, motion blur is off. Another value stops an export that uses it, and the message says so; an export that sets motion blur itself (the sheet's choice, Claude's) never reads it.
  • {format} writes the format's id, for example hevc. {codec} writes the short codec, for example hevc10.
  • Keep {codec} or {format} in your template. Without it, a HAP Q export and a ProRes export of the same scene get the same name, and the second one replaces the first (Starlight asks first).
  • Once you have used the sheet, your last choice there wins over these defaults.
  • Starlight ignores a value it cannot use. The value stays in the file as you wrote it.
  • A template problem shows in the sheet, in place of the file name, before you export.
  • If two surfaces would get the same file name, the export stops before it starts.

Export one surface

This exports a single surface of the open scene.

  1. Right-click the surface on the canvas, or its root node in the node graph.
  2. Choose export <surface>, for example export north.
  • It uses the format, fps, motion blur and folder of your last sheet choice. It has no sheet.
  • If the surface's file is already there, Starlight asks first: Replace 1 file? Click Replace to export, or Cancel. The old file stays until the new export is finished.
  • The item is greyed while another export runs.
  • At the end the export monitor reads, for example: export done · intro · 1 file (Follow or cancel an export).

Export to the end of the song

This export runs until the longest audio track ends, so the whole song plays out.

  1. Choose File › Export Scene — Full Track Length.
  2. Or open the command palette (⌘/ / Ctrl+/) and pick export scene · full track.
  • Starlight rounds the length up to whole loops, so the video still loops cleanly. Every surface uses the scene loop here, so every surface has the same length.
  • A looping track counts once, at its full length. A track with an offset counts from its offset.
  • The sound of a video with muted unticked counts as a track too.
  • With no audio, it exports one loop.
  • It uses your last sheet choice, with every surface.
  • If files with these names are already there, a box lists them and asks first.
  • The end line says how many loops it made, for example · 3 loops.

Export the reel ⇧⌘E / Ctrl+Shift+E

The reel is every scene of the show, joined into one file per surface.

  1. Set the format and fps once with ⌘E / Ctrl+E.
  2. Press ⇧⌘E / Ctrl+Shift+E, or choose File › Export Reel…. The command palette has export reel too.
  • There is no sheet. The reel uses your last sheet choice. A PNG or EXR choice becomes H.264, because a reel must be video.
  • Scenes render in the order of the scene list (Change the scene order). Starlight skips names that start with 99.
  • Before the first scene renders, Starlight checks the files of every scene (When a file cannot render).
  • Each scene first exports to its own renders/<scene>/, as usual.
  • Then Starlight joins the videos of each surface into renders/reel/. It copies them without new compression, so this is fast and loses no quality.
  • The reel file names use the naming template, with reel as the scene name.
  • Before it starts, a box lists every file that is already there (scene files and reel files) and asks: Replace 12 files?
  • The reel cuts straight from one scene to the next. It has no audio.
  • Every surface of every scene uses the scene loop, so all surfaces change scene at the same moment.
  • Every scene must deliver at the same fps. If your scenes use different rates, pick one fps in ⌘E / Ctrl+E first.
  • The export monitor's blue line fills for the whole reel, the mint line for the scene it writes now, and the violet line for the surface. The text after the ring says the same, for example 18% overall - about 5 min left - scene 2 of 6 @ 40% - surface 2 of 3 @ 70% (f1234/3600). Point at the ring to see the names, for example b-song · 2 of 6 · 3 surfaces (Follow or cancel an export).
  • At the end it reads, for example: export done · reel of 6 scenes · 6 files. Finder (Explorer on Windows) opens on the first reel file.

Unsaved edits are exported

You do not need to save before you export.

  • ⌘E / Ctrl+E, export <surface>, the full-track export and the reel use the open scene as the canvas shows it.
  • The reel's other scenes use their saved files. If they have unsaved changes (a dot in the scene list), save them first with File › Save All (⌥⌘S / Ctrl+Alt+S).
  • An export that Claude runs, and a Glimpse publish, use the saved scene. Save first (⌘S / Ctrl+S).
  • Canvas focus never leaves a surface out of an export, and a stage never shows in one (Focus, Stages).

Audio in the file

Starlight mixes every audio layer of the scene into each surface's video. It also mixes in the sound of every video layer with muted unticked.

  • Each layer keeps its own volume, offset and loop. Starlight adds the layers together without making them quieter, so each volume stays as you set it.
  • Starlight leaves a layer out when it is muted, bypassed (turned off), at volume 0, or set to export: false.
  • An un-muted video plays at full volume, once per clip file, with the clip's offset and loop. A video file with no sound adds nothing.
  • The live 🔊 monitor (what you hear in the app) never changes the file.
  • An .mp4 file gets AAC audio at 192 kb/s. A .mov file gets uncompressed 16-bit audio (PCM).
  • The sound ends exactly at the last frame. If the song is shorter, the rest is silent.
  • Each surface's file is its own length (Each surface's own length), so a shorter surface carries a shorter part of the sound. Click scene loop in the sheet to keep the whole sound on every surface.
  • Image sequences and the reel have no audio.
  • An audio file that is missing or online-only stops the export (When a file cannot render). With render anyway, Starlight leaves it out.
  • The end line counts the tracks, for example · 1 audio track.

Follow or cancel an export

The export monitor shows every export while it runs, also an export that Claude starts for you, or a Glimpse publish. It shows up to three levels. Each level has its own colour:

  • Blue: the project. All the scenes of the export. It shows only when the export has 2 or more scenes (the reel, or several scenes that Claude exports).
  • Mint green: the scene. All the surfaces of the current scene. It shows only when the scene has 2 or more surfaces.
  • Violet: the surface. The file that Starlight writes now. It always shows.

The parts of the monitor:

  • The ring: a small circle in the bottom-left corner, next to the time (▶ 8.63s / 16.00s). It is violet and fills for the surface that Starlight writes now.
  • The text after the ring, for example 62% overall - about 12 min left - scene 3 of 4 @ 40% - surface 2 of 3 @ 70% (f1234/3600). It reads in order of importance:
    • 62% overall: how much of the whole export is done. about 12 min left: about how long the whole export still needs. These have the colour of the highest level that shows.
    • in mint: which scene it is (scene 3 of 4) and how much of that scene is done (@ 40%);
    • in violet: which surface it is (surface 2 of 3), how much of that surface is done (@ 70%), and its frames (f1234/3600: frame 1234 of 3600).
    The time left shows when Starlight can estimate it, after a few seconds. Click the text to open the box, as with the ring.
  • Overall always means the whole export: all scenes and all surfaces.
  • Only the levels that mean something show. Examples:
    • 1 scene with 3 surfaces: 40% overall - about 3 min left - surface 2 of 3 @ 70% (f1234/3600). The overall part is mint, because the scene is the highest level.
    • 4 scenes with 1 surface each: 40% overall - about 9 min left - scene 2 of 4 @ 70% (f1234/3600). The overall part is blue. The scene part is violet, because the one file of that scene is the surface.
    • 1 scene with 1 surface: 70% - about 1 min left (f1234/3600). Everything is violet. There is no "overall", because the export is one file.
  • While the canvas plays, the text ends with · paused is faster in grey, and the box says Exports are faster while playback is paused.
  • When the window is narrow, the text gets shorter from the right. First paused is faster goes, then the frames, then the surface (its @, then its count), then the scene (its @, then its count), then the time left. The overall percentage always stays.
  • While another area fills the window (`), the ring and its text show in a small box in the bottom-left corner, over that area.
  • The lines: thin lines along the bottom edge of the window, just above the yellow loop bar. There is one line for each level that shows. From the bottom up: the project (blue), the scene (mint), the surface (violet).

An export can use more than one worker (Settings › Media › export workers: 1, 2, 3 or 4). Until you pick one, the default is 2 on Windows and 1 on a Mac. On a Windows PC, 2 workers were faster for every export. On a Mac, 2 workers were slower for H.264. The row shows the count in use and why, for example 2 (the Windows default). With more than one worker, Starlight writes several surfaces, or several parts of one big surface, at the same time, and joins the parts into one file at the end. When several surfaces are written at the same time, no single surface is "the current one". Then there is no violet line. The mint scene line is the lowest line, the ring is mint, and the text counts the finished surfaces, for example 33% overall - about 3 min left - 2 of 6 surfaces done (f2400/7200). The frame count is then for the whole scene. The box says how many parts run now, for example 3 parts at once.

A Glimpse publish is one export, with one ring and one set of lines for all its surfaces. After the surfaces, the same ring shows the playback copies and the uploads, for example N: HEVC copy 42%, and the box says publishing. Stop in the box then stops the publish, and the look on the site stays as it was (Publish to Glimpse).

The reel (⇧⌘E / Ctrl+Shift+E) is one export with all its scenes, so its blue line and its overall percentage are for all the scenes. When Claude exports several scenes, they count as one export. There is one ring, one blue line and one time left for all the scenes, and one ✓ at the end, for example export done · 4 scenes · 12 files. Each scene still gets its own files in its own folder, and nothing is joined. show in Finder then opens the renders folder, with one folder for each scene. If Claude exports one scene at a time, each scene is a separate export, and the monitor shows each scene on its own (Starlight does not know how many scenes Claude will export next).

Only one export runs at a time. If you start a new export while the last one still shows ✓, the lines are always for the export that runs.

When Claude exports, Claude also shows how far the export is, for example frame 1200 of 4500 · intro · N (62%). The percentage is the same as on the ring. If Claude stops waiting, the export still runs. To stop it, use the ring or ask Claude.

To see the detail:

  1. Point at the ring. A small box opens above it.
  2. Read the box. It has one row for each level that shows, from the top: project, scene, surface. Each row has its label in its colour, a name with its numbers, a small bar and the percentage. For example:
    • project: all 4 scenes · 5 of 12 files done, 62%;
    • scene: c-song · 3 of 4 · 3 surfaces, 40%;
    • surface: N · 2 of 3 · f1234/3600, 70%.
    Then the time so far and about how long is left, and the folder. Point at the surface row to see the name of the file.
  3. To keep the box open, click the ring. Click anywhere else to close it.
  4. Click show in Finder (show in Explorer on Windows) to open the folder.

When the export ends:

  • Done: the ring shows a ✓ in the colour of the highest level, and the lines are full. The text reads, for example, export done · intro · 6 files, with show in Finder. After 8 seconds it all goes away. While you point at it, it stays. It goes 3 seconds after the pointer leaves.
  • Failed: the ring, the lines and the text turn red. The text reads export failed: and the reason. It stays until you click × or the text (When an export fails).
  • Canceled: the ring and the lines turn grey. The text reads export canceled and the scene, for example export canceled · intro. It goes away after 4 seconds. A canceled export is not an error, also when Claude canceled it.
  • Finder (Explorer on Windows) also opens by itself on the first file after ⌘E / Ctrl+E, a surface export and the reel.
  • If the export finished with a warning, a line above the time says so, for example exported 6 surfaces · HEVC 10-bit 60fps → revealed in Finder — WARNING: 2 files rendered as empty spots. Click × on that line when you have read it.

To stop an export:

  1. Point at the ring and click stop in the box.
  2. Or press Esc. Esc first closes what is open (the help, Find, the scene list, the versions, the timeline) and clears the selection. When nothing else is left, it asks: Cancel the export? The finished surfaces are kept. Click Cancel Export.
  3. Or ask Claude, for example Stop the export. Claude cancels it in the same way (cancel_export). It does not ask again, because you asked Claude.
  4. Starlight removes only the unfinished files (and their parts). If a surface had an older file, the older file stays as it was. Surfaces that are finished stay too.
  5. The monitor then reads export canceled. If the monitor reads export failed after something stopped ffmpeg from outside Starlight (for example Task Manager), that is not a cancel. Cancel with the box, Esc or Claude.
  • Only one export runs at a time. The three export items in the File menu are greyed until it ends.
  • Every file is loop-perfect: it has exactly loops × loop length × fps frames.
  • If a frame count is short, the message above the time ends with WARNING: frame-count mismatch.
  • Each frame waits until every video clip shows the right picture. A slow clip makes the export slower, but never repeats a frame.
  • If a clip does not reach its picture in 20 seconds, the export stops. The export failed: message names the clip and the time, for example video "clips/loop.mp4" did not show its frame at 1.233 s. Point at the ring to read the whole message.
  • With render anyway, that frame renders with the picture the clip shows. The message above the time then ends with, for example, WARNING: 2 video frames may repeat (clips/loop.mp4 at 1.233 s), and the file is not loop-perfect.

Replace an older export

When you export a scene again, Starlight warns you before it replaces files. The old file is never lost before the new one is finished.

  1. Press ⌘E / Ctrl+E. If files with these names are already there, a yellow line lists them, for example replaces 2 files: … Point at the line to see every name.
  2. Press replace…, or ⏎ / Enter. Nothing starts yet. The line reads press again to replace 2 files.
  3. Press confirm, or ⏎ / Enter again. The export starts.
  • If you change the format, the fps, the surfaces or the folder, the sheet checks again, and you must confirm again.
  • Each surface renders into a hidden file first. The old file is replaced only when the new file is finished.
  • If you cancel, or the export fails, the old file stays as it was.
  • export <surface>, the full-track export and the reel have no sheet. A box lists the files and asks first.
  • An export that Claude runs does not ask. Its result says which files it replaced.
  • An image sequence is a folder. Starlight replaces the whole folder, so no old frames are left behind.
  • On Windows, a file that another program has open cannot be replaced. The export then stops with could not put "…" in place, and the new render is kept as the hidden file (When an export fails).

Quit or switch during an export

An export can take a long time. While it runs, Starlight protects it.

  • The computer does not go to sleep. The screen can still turn off. This is also true for the reel and a Glimpse publish.
  • These ask first: quit, closing the window, Open Project…, Open Recent, a project on the Projects screen, New Project…, Reload Project from Disk (⌘R / Ctrl+R) and Force Reload App.
  • The question is, for example, Stop the export and quit? Click Keep Exporting to go on. This is also what Esc does.
  • Click Stop and Quit (or Stop and Open, and so on) to stop. Starlight stops the export first, then does what you asked.
  • When the export stops, the finished surfaces are kept. The surface in progress stops, and its old file stays as it was.
  • Do you also have unsaved scenes? Then Starlight asks about the export first. After the export stops, it asks Save changes? (Save changes before you leave).
  • Starlight never renders the rest of an export from another project.

Export diagnostics

The app log records every export's result, and the last lines of any ffmpeg error. ffmpeg is the tool that writes the files.

  1. To read the log, choose Help › Troubleshooting › Reveal Logs in Finder (Windows: Show Logs in Explorer).
  2. To report a failed export, choose Help › Troubleshooting › Export Diagnostics… and send the zip (Diagnostics).
  • The zip lists ffmpeg and the formats it can write.
  • Each time ffmpeg writes a file, the log has two lines. The first line has the full ffmpeg command. You can paste it into a terminal to run it again (on Windows, use Command Prompt). The second line has the result, the time, the file size in bytes and the number of frames.

When an export fails

Find the message you see, then do what the second column says.

You seeDo this
A format is greyed in the sheetPoint at it to see why. This machine's ffmpeg cannot write it. Pick another format.
… can't encode "<surface>" — no encoder takes W×HThe surface is too big for every encoder of that format. Export it as ProRes 422 HQ or an EXR sequence.
export destination is inside the projectChoose renders/ or a folder outside the project.
scenes deliver at different fps (reel)Pick one fps in ⌘E / Ctrl+E. Then press ⇧⌘E / Ctrl+Shift+E.
interpolate can't carry alphaUntick interpolate, or pick a format without alpha.
surfaces "a" and "b" both export as …Two surfaces get the same file name. Fix naming or aliases (Project defaults).
naming template …The naming template is empty, is a path, has an unknown token or has no {surface}. Fix it in project.yaml.
an export is already runningWait for it, or point at the export ring and click stop.
export not started — 2 files cannot render: …Fix the files, or choose render anyway (When a file cannot render).
WARNING: … rendered as empty spotsYou chose render anyway. Fix the files and export again before you deliver.
video "…" did not show its frame at … sThe clip decodes too slowly, or it is damaged. Ingest it (Ingest), then export again.
WARNING: … video frames may repeatYou chose render anyway, and a clip did not reach some frames. Ingest the clip and export again.
could not put "…" in place — … Is it open in another app?The new render is finished, but the old file is open in another program (often a player or a media server, on Windows). Close that program. The new render is kept beside the old file as a hidden file whose name starts with . and ends in .partial.mp4 (or .mov). Export again, or rename the hidden file yourself.
the open project changed during the exportAnother project was opened while the export ran. Open the project again and export again.
No soundSee Audio in the file.
Very slowinterpolate is on, or HEVC runs on libx265, or ProRes runs on Windows. Surfaces render one after another.
ffmpeg not foundThis is unusual: the app includes ffmpeg. On Windows, the message says to reinstall Starlight, which puts ffmpeg back. On a Mac, it says brew install ffmpeg. To use another copy, set the environment variable STARLIGHT_FFMPEG to the full path of an ffmpeg program (ffmpeg.exe on Windows).
WARNING: frame-count mismatchExport again. If it happens again, send diagnostics.

On this page