Skip to Content
Starlight

Assets & fonts

Assets are the files your scenes show: images, videos, audio, colour LUTs (files that change the colours) and fonts. The Assets panel is where you bring them in, put them on a surface (one LED output, see Glossary) and keep them organized.

Open the Assets panel toggle ⇧A / Shift+A

The panel shows one tile for each file in the project's assets/ folder. It shows one folder at a time, like Finder (File Explorer on Windows).

  1. Press ⇧A / Shift+A, or choose Window › Assets.
  2. Hover a tile to see its path and the scenes that use it. An unused file says unused.
  3. Right-click a tile for all its commands (Asset menu).
  4. Double-click an image or video tile to see it full size in the canvas pane. Press ← or → to see the previous or next one in this folder, and Esc to close it (the preview).
In the panelWhat it is
●A scene uses this file.
▦ ♫ LUT ?A video, an audio file, a colour LUT, a file type that Starlight does not know. An image tile shows the picture. An audio tile also shows its waveform once Starlight has analysed the sound.
import…Import one file (Import media).
refresh (two arrows)Read the project from disk again. The button stays grey until it is done. It is the same icon as sync in the Generations panel.
+ folderMake a folder here (Folders). It is grey in a linked folder.
ingestPrepare videos that are not prepared yet (Video ingest).
⇄ ✎ ×Replace, rename, delete (Rename, replace, delete).
12 assetsHow many files the project has. Inside a folder it reads 3 here · 12 total.
assets ⇢ sharedOne tab for the project's assets/ and one for each linked folder. The tabs show only when the project has linked media (Linked media).
fontsThe brand fonts, listed under the tiles (Fonts).
  • An empty project says no assets — drop a file or Import.
  • Starlight hides its own folders: assets/originals/, and the folders whose names start with a dot (.proxies, .mattes, .cutouts, .depth, .stages).
  • Stage captures are normal assets, in assets/stages/.
  • A line at the bottom of the panel says what happened, for example imported logo.png, or why a command was refused.
  • The panel docks and floats like every panel (The workspace).

Import media

Importing copies a file into the project's assets/ folder. Your original file stays where it was.

  1. Drag one or more files from Finder (Explorer on Windows) into the Starlight window.
  2. The Assets panel opens on the folder where the files landed. The new tiles flash.

You can also click import… in the panel and pick one file. The dialog lists images, videos and .cube files. To import audio or a font, drag the file in.

FileWhat happens on import
PNG, JPEG, WebP, GIF, SVGUsed as it is.
HEIC, HEIF, TIFF, EXR, AVIF, BMP, TGA, DPXConverted to a PNG before the import ends. Scenes use the PNG.
MP4, MOV, M4VCopied, then prepared in the background (Video ingest).
WebMA WebM with transparency becomes an .mp4 with a new name, and is prepared. Any other WebM is used as it is.
MP3, WAV, M4A, AAC, FLAC, OGGUsed as it is. Drag only.
.cubeA colour LUT. Use import…, or the + in a lut effect (LUTs). Dragging it into the window does nothing.
TTF, OTF, WOFF, WOFF2Goes to fonts/ (Fonts). Drag only.
A folder of numbered framesBecomes one video (see below).
  • An image dropped on a surface on the canvas is also placed there. A video or audio file dropped on the canvas is only imported.
  • Drop a folder of numbered frames (PNG, EXR, TIFF, DPX, TGA or JPEG) to get one video at 30 frames per second. Transparency is kept.
  • The folder needs at least two frames. If the numbers have a gap, Starlight uses the longest run without a gap.
  • The frames are kept in assets/originals/<folder>/. The video tile appears when its ingest is done.
  • The copy gets a safe lowercase name: My Logo.PNG becomes my-logo.png. If that name is taken, -2 is added.
  • Each import makes a version, a saved copy of the project that you can go back to (Versions).
  • If an import fails, the notice line says import failed and why.
  • A generation's import also copies into assets (Generations).

Video ingest and proxies

After import, Starlight prepares each video so it plays and exports smoothly. This step is called ingest. It runs for MP4, MOV and M4V files, and for a WebM with transparency.

  • Ingest writes an all-intra working file at the same path. Every frame is stored whole. So scrubbing (dragging through time) and export can jump to any frame at once.
  • Up to 4096 px on each side, the working file is H.264. A bigger video is HEVC on Mac and Windows, because the graphics chip can play HEVC at that size.
  • A video whose longer side is more than 1920 px also gets a proxy. A proxy is a quarter-size copy that the canvas plays when you zoom out. When you zoom in on a surface, that surface's videos play the full file. Export always uses the full file.
  • Ingest runs in the background, one video at a time. You can keep working while it runs (see below).
  • The untouched original goes to assets/originals/. Versions do not save it.
  • A video wider than 8192 px is scaled down to 8192 px.
  • The working file is 8-bit, with colour at half resolution (4:2:0). That is all the canvas can show. A video with more than 8 bits, or with full colour resolution (4:4:4), also gets a deep file: the same frames at 10 bits or more, with all of its colour. A 16-bit export (HEVC 10-bit, ProRes, EXR) reads the deep file, so dark gradients and coloured edges stay as clean as the source. The canvas and 8-bit exports do not use it. The ingest line names each file, for example source HEVC 10-bit 4:2:0 → working H.264 8-bit 4:2:0 + deep HEVC 10-bit 4:2:0.
  • An export decodes each deep file on the graphics card when the card can: HEVC deep files on Windows (NVIDIA, and other cards for 4:2:0) and on a Mac. The card gives exactly the same picture as the CPU, only faster. Starlight checks this for each file before it uses the card. A ProRes deep file decodes on the CPU. The export result and the diagnostics log say who decoded each clip, for example deep HEVC 10-bit 4:2:0, ffmpeg NVDEC (10 bits).
  • Videos ingested before deep files get theirs by themselves: when you open the project, each video that the scenes use is checked once, in the background. This work waits while the transport plays, while the Glimpse panel is open and while an export runs, and it waits behind your imports. Only a file that is on this computer is read.
  • To make them all now, choose File › Make Deep Files for This Project…. A box says how many clips get one, how much space they take at most and about how long it takes. A deep file is made only when it leaves 2 GB free on the disk.
  • Transparency (alpha) is kept for ProRes 4444, QuickTime Animation, PNG-in-MOV, PNG frames, WebM with alpha and, on a Mac, HEVC with alpha. Starlight packs the colour and the alpha into one video (a packed matte). Macs and Windows PCs both play it with its alpha (Video with transparency).
  • A WebM without alpha, or an AV1 video with alpha, is used as it is. To keep AV1 alpha, export it again as ProRes 4444 or as PNG frames.
  • If ffmpeg is missing or the encode fails, the original stays as it is. The notice line says ingest failed for … — using the original as-is.
  • In a shared project the file stays as you imported it. The working file goes to this machine's media cache (a folder on this computer) instead.

What to deliver for a surface. For the best export, ask the animators (After Effects) for this:

  1. One file for each surface, at the surface's exact pixel size (for example 3200 × 1600) and the venue's frame rate (30 fps).
  2. Work in a 16-bit project (16 bpc). Render a master as Apple ProRes 4444, channels RGB (not RGB + Alpha).
  3. Convert the master to HEVC 4:4:4 10-bit (the command is in the docs, docs/assets.md, "Delivering clips for surfaces"). ffprobe must say hevc (Rext) and yuv444p10le.
  4. Import it. The ingest line must say deep HEVC 10-bit 4:4:4 (on a PC with an NVIDIA RTX card) or deep ProRes 12-bit 4:4:4 (on a Mac).

Do not deliver H.264 or other 8-bit files for surfaces: they have no deep file. A file with real transparency is packed at 8 bits (see Video with transparency), so render RGB.

Follow the progress. The notice line at the top of the window shows one line for all the videos that wait for ingest. For example:

  • ingesting 9 / 24 · north.mp4 — working file (HEVC) 42%. 9 of the 24 videos are done. Starlight works on north.mp4 now. It makes its working file in HEVC, and that video is 42% done.
  • The steps of one video are starting, checking the file, working file (H.264) or working file (HEVC), and proxy.
  • The count includes every video in the queue: videos you drop or import, videos that Claude imports, ingest in the Assets panel, and linked videos for the media cache.
  • At the end the line says 24 ingested, or 24 ingested · 2 failed. The line goes away after 2 seconds.
  • Each video that failed also has its own message. That message stays until you close it. Help › Recent Messages… lists them too.
  • A very long file name is shortened in the middle, for example halcyon_tipoff_main…approved.mp4.
  • The line shows only this computer's videos, also in a shared project.
  • To stop an ingest from the Assets panel, click cancel in that panel (see below). The ingest of an import always runs to its end.

Keep working while it runs.

  • The project opens at once. Starlight does not wait for any ingest.
  • A video that is not ready yet plays its original file. It can scrub more slowly.
  • When the working file is ready, the layer changes to it by itself. Your unsaved edits, your selection and the playhead stay where they are.
  • Ingest runs at a low priority, so the canvas, playback and the controls come first. When it encodes on the processor, it leaves two processor cores free. Because of this, ingest can take a little longer.
  • Nothing ingests while an export runs, or a reel or a Glimpse publish. The export gets the whole computer. The line says ingesting 61 / 216 · paused while an export runs. A video that was halfway through when the export started stops at once and starts again from the beginning after the export. Its original stays as it was. When the export ends, the ingest goes on by itself.

A video that changed on disk gets a new proxy by itself. Sometimes a video changes after its ingest. For example, you replace it in Finder (Explorer on Windows), or Dropbox brings a new version. You do not need to do anything.

  • Starlight sees the change. It checks when the project opens, when a file changes, and again every 5 minutes.
  • From that moment the layer plays the new file. It never plays the old proxy.
  • Starlight then makes the new working file and proxy in the background. The notice line says, for example, updating proxies for 2 changed files. The line goes away when the work is done.
  • When they are ready, the layer changes to them by itself. Your edits, your selection and the playhead stay.
  • This work waits while the transport plays, while the Glimpse panel is open, while an export runs, and while the canvas is close to dropping frames. It also waits behind your imports. It encodes one video at a time, at the lowest priority of the computer, so it uses only the power that nothing else needs.
  • Only a file that is on this computer is checked. A file that is online-only in Dropbox waits until it is on this computer.
  • When only the date of a file changes, and not its content, nothing is encoded again.
  • Your earlier original is kept. It stays in assets/originals/ with a new name, for example north (replaced 2026-11-05 14-03-07).mp4. You can delete it there when you do not need it.
  • A video that you copied in and never ingested is not changed. Use ingest for it (below).

Ingest videos that were not prepared. A video you copied in with Finder (Explorer on Windows), or whose ingest stopped early, is not prepared yet.

  1. Click ingest in the panel's toolbar. Every video that needs it is queued.
  2. Or right-click one video tile and choose ingest (all-intra + proxy). It is grey, with already ingested, when the video is ready.
  3. Watch the progress line in the Assets panel, for example ingest 1/3 · …. The notice line shows the count for the whole queue.
  4. To stop, click cancel on that line. Queued videos are dropped and the running one stops. Your originals are not changed.
  • ingest is grey while a batch runs.
  • When you click it, a line sums up the result, for example queued 2 clips · 1 already ingested.
  • WebM files and stills that need converting are skipped. Import them again instead.
  • A video that you moved in Finder (Explorer on Windows) gets its old proxy back first. It is not encoded a second time.

Video with transparency (alpha)

A video with alpha has parts you can see through, for example a logo sting over the surface. Starlight keeps the alpha when it ingests the video. It packs the colour and the alpha into one working file, a packed matte. The graphics chip plays it on a Mac and on a Windows PC, with its alpha. So the same scene looks the same on both.

These files keep their alpha on every computer:

  • ProRes 4444 (.mov), rendered with alpha.
  • QuickTime Animation and PNG-in-MOV (.mov).
  • WebM with alpha (VP8 or VP9).
  • A folder of PNG, TIFF or EXR frames with alpha.

HEVC with alpha needs a Mac. Apple's HEVC with alpha (from Final Cut Pro, Motion or Compressor) keeps its alpha in a part of the file that only macOS can read. On Windows, and on a Mac without the Xcode Command Line Tools, Starlight cannot read that alpha. It then:

  • keeps the file as it is and does not ingest it, so a Mac can still read the alpha later;
  • shows α! on the file's tile in the Assets panel (hold the pointer over it for the reason);
  • says it on the line at the bottom left of the canvas: no transparency on this machine (HEVC with alpha needs a Mac): logo.mov.

The layer then shows the video without its transparency on that computer. To fix it, do one of these:

  1. Best: export the video again as ProRes 4444 with alpha, or as WebM with alpha. Then replace the file (the ⇄ button on its tile). Every computer then reads the alpha.
  2. In a local project: import or ingest the file on a Mac. The packed working file that the Mac writes plays on Windows too.
  3. On a Mac without the tools: install the Xcode Command Line Tools. Then click ingest in the Assets panel.
  • In a shared project, each computer prepares its videos in its own media cache. So if anyone opens the project on Windows, give it alpha videos from the list above, not HEVC with alpha.
  • WebM with alpha is not used as the working file. A computer plays it without the graphics chip, and that is too slow for a surface-size video, above all when you scrub or export.

Place an asset on a surface

Placing an asset adds a layer that shows the file.

  1. Drag a tile from the panel onto a surface on the canvas.
  2. Let go where you want it. The layer lands on that surface, at that point.
  • Where a drop lands in detail: Drop media on a surface.
  • You can also drag a tile, or a file from Finder (Explorer on Windows), onto the node graph. It becomes a node at the graph's current level, and Properties opens on it (Drop a file or asset).
  • Or right-click a tile and choose place on canvas. The layer lands in the centre.
  • A done job in the Generations panel drags onto a surface in the same way. If it is not in Assets yet, Starlight imports it first. If the import fails, a notice says why, and the scene does not change (Use a result).
  • It goes into the comp (a named group of layers) that is open in the graph. If no comp is open, it goes into the scene's first comp.
  • If the scene has no comps yet, Starlight makes a comp named dropped and shows it on the first surface.
  • An image becomes an image layer inside a transform (transform > image). A video becomes a looping, muted video layer.
  • An audio file becomes an audio layer with no picture. In the node graph its node is a round dial. Drag the dial to move through the track.
  • A LUT is not a layer. You use it in a lut effect (LUTs).
  • A linked file that is online-only or missing cannot be placed (Linked media).
  • Every way to place is a normal edit: a drop on the canvas or the graph, and place on canvas. The scene is not saved until you press ⌘S / Ctrl+S. ⌘Z / Ctrl+Z undoes it (the notice says, for example, undid: place logo.png).

Organize assets in folders

Folders keep a big project easy to browse. They are real folders inside assets/.

  1. Click + folder.
  2. Type a name and press ⏎ / Enter. Esc cancels.
  3. Drag a tile onto the folder to move the file into it.
  4. Click the folder to open it. Click assets in the path above the tiles to go back.
  • To move a file up again, drag its tile onto a name in the path.
  • The path above the tiles shows when you are inside a folder, or when there are folders to open.
  • Right-click a folder for Rename Folder and Delete Folder (Folder menu). Rename works like a new folder: type the name, then ⏎ / Enter.
  • You can only delete an empty folder. Otherwise Starlight says folder is not empty … — move them out first.
  • Folder names become lowercase, with dashes instead of spaces. A name needs at least one letter or digit.
  • If the folder already has a file with that name, the moved file gets -2.
  • Moving a file, or renaming a folder, updates every scene that uses it. Nothing breaks.
  • You cannot make folders or move files in a linked folder. Use Finder (Explorer on Windows) there.
  • Each change makes a version (Versions).

Rename, replace or delete an asset

Each tile has three buttons: ⇄ replace, ✎ rename and × delete. The right-click menu has the same commands (Asset menu). Hover a button to see which scenes it affects.

Replace a file. Every scene that uses the old file switches to the new one.

  1. Click ⇄ on the tile, or right-click it and choose replace….
  2. Pick the new file. The dialog lists images, videos and .cube files.
  3. If no scene uses the old file now, Starlight asks about it. Click remove or keep.
  • The new file is copied into the old file's folder, under its own safe name. For example, a replace of assets/players/logo.png puts the new file in assets/players/. The old file is not overwritten.
  • The panel line says how many references changed, for example replaced a.png → b.png · updated 2 references.
  • A new video is prepared like any import (Video ingest).
  • If any scene would break, nothing changes.
  • The dialog does not list HEIC, TIFF, EXR and other stills that need converting. Import those first, then replace.

Rename a file.

  1. Click ✎ on the tile, or right-click it and choose rename.
  2. Type the new name and press ⏎ / Enter. Esc cancels.
  • Rename works only when no scene uses the file. Otherwise ✎ is grey. A used file can still be moved or replaced.
  • The new name is made safe, as on import: lowercase, with dashes. If the name is taken, -2 is added.
  • If you leave out the extension, the old extension is kept. The file stays in its folder.

Delete a file.

  • Click ×, or right-click the tile and choose delete.
  • You cannot delete a file while a scene uses it. Its tile has a green dot, its × is dim, and delete in the menu is grey and names the scenes.
  • If you click the dim ×, the line at the bottom of the panel says which scenes use the file: can't delete logo.png — used by intro. Remove the file from those scenes first, or replace it. The line stays in view while you scroll.
  • Otherwise Starlight asks first: Delete logo.png? A version checkpoint is made.
  • If another app has the file open, the delete fails and the line says so. Close the file there and try again. On Windows this includes a media player and the Explorer preview pane.
  • Deleting a generated file also deletes its .gen.json record (Where results go).
  • reveal in finder in the menu shows the file in Finder. On Windows the item says show in explorer.
  • Linked tiles have no ⇄, ✎ or × (Linked media).
  • Each change makes a version, so you can go back to an earlier version (Versions).

Your unsaved edits are safe

Asset operations never touch the open scene's unsaved edits.

  • This is true for import, refresh, move, rename, folders, replace, delete and drops into the window.
  • A layer you deleted stays deleted. The scene stays unsaved until you save it.
  • Move, folder rename and replace also update the open scene's file references.
  • A file that only an unsaved layer uses still counts as used. You cannot delete or rename it.

Use linked media (Dropbox)

Linked media is a folder outside the project, for example the team's Dropbox media folder. Scenes use its files in place, without a copy in assets/ (Glossary).

  1. Open project.yaml in a text editor.
  2. Add a media: block. Give each folder a short name: lowercase letters, digits, - or _. It must start with a letter or a digit, and have 32 characters at most.
  3. Save the file.
  4. Choose File › Reload Project from Disk (⌘R / Ctrl+R).
  5. The folder appears as a tab, ⇢ shared, next to assets in the panel.
  6. Drag a tile from that tab onto a surface, like any asset.
media:
  shared: "~/Library/CloudStorage/Dropbox/shows/halcyon-arena/media"
  plates: ../plates     # relative to the project folder
  • The folder can be a full path, a path that starts with ~/, or a path relative to the project folder.
  • A scene names a linked file like this: media:shared/plates/N.mov.
  • Linked tiles are read-only in Starlight. Rename or move them in Finder (Explorer on Windows).
  • Starlight never writes into a linked folder. import… and drops always copy into assets/.
  • A linked video is ingested into this machine's media cache the first time a scene uses it.
  • A tab shows ⚠ when its folder has a problem, and ☁ with a number when some files are online-only.
  • An empty tab says why, for example … is not on this machine — set its folder in Settings › Media.
BadgeMeans
●Cached: ingested into this machine's media cache. Fast to scrub.
○Local: downloaded, not ingested yet. A video is ingested the first time a scene uses it.
☁Online-only: the file is not on this computer yet. Click make available offline in the panel's notice, or Make Available Offline in the tile's right-click menu.
✕Missing on this machine.
?Unknown: the check took too long. Click rescan in Settings › Media.

Right-click a linked tile for four commands (Linked file menu):

  • Place on Canvas: grey while the file is online-only or missing.
  • Reveal in Finder: shows the file in Finder (Explorer on Windows).
  • Make Available Offline: downloads an online-only file.
  • ingest into the media cache: prepares a local MP4, MOV or M4V now. It says already cached when it is done.

The online-only notice. When linked files are online-only, a line at the bottom of the panel says so. For example: 3 linked files online-only (1 used by scenes): ….

  • Click make available offline on that line. The files download in the background.
  • While they download, the line reads making available offline 2/5 — …. Click stop to stop. The files already done stay on your disk.

Relink on your machine. A linked folder may not exist at the same path on your machine. Point it at your own copy in Settings › Media. This changes only your machine.

  • The media cache settings are on the same Settings page.
  • On a Mac, make available offline downloads the files, but Dropbox may make them online-only again later.
  • To keep a folder on your Mac, right-click it in Finder and choose Make available offline.
  • In a shared project the project's own assets show the same badges. They stay editable.

Find missing media

An empty layer can mean a missing file

A layer whose file is missing, online-only or broken draws only one white pixel, so you see almost nothing. The layer is still in the graph and in Properties. An export does not render such a file without asking: it stops before the first frame and names the file (When a file cannot render).

The canvas names these files in a line at the bottom left, in the warning colour:

  • missing media: a.png, b.mov: the file is not in the project. It was deleted, renamed or moved. Starlight says this only after it has finished checking the file's folder.
  • could not load: c.mov: the file is there, but Starlight cannot read it. It is damaged, its format is not supported, or it is online-only in Dropbox. Starlight says this only after a check has answered.
  • still loading: d.mov: the file is slow to answer (a busy disk, Dropbox, a clip still being written). The project opens without waiting for it. The layer shows the file when it arrives, and your unsaved edits stay.
  • If Dropbox does not answer in time, Starlight asks again by itself: after 2 seconds, then less often, at most once a minute. The line says still loading until the file loads.
  • An online-only file says could not load. When you make it available offline (in Starlight, Finder, Explorer or the Dropbox app), the layer shows it by itself. You do not need to reopen the project. If you used Finder, Explorer or Dropbox, click the Starlight window: Starlight looks again when its window comes to the front.
  • still loading also shows while Starlight is still checking a folder in Dropbox. This happens in a shared project or a linked media: folder when Dropbox is slow to answer, or when the folder is online-only. Starlight does not call these files missing. When the check is done, the file shows, or the line says missing media.
  • The line names up to three files, then how many more, for example (+2 more).
  • The line goes away when the file is back.
  1. Select the layer. Properties shows its src (the file path).
  2. Put the file back at that path, or restore a version that had it (Versions).
  3. For a ☁ or media: file, make it available offline, or set its folder in Settings › Media.
  • A missing brand font shows missing in the panel's fonts list. Its text uses the fallback fonts (Fonts).

Cut a subject out of a photo

A cut-out removes the background of a photo, so only the subject shows (for example a player). A Mac makes the cut-out. Starlight saves it in the project, so every computer shows the same cut-out, on a Mac and on Windows.

  1. Select an image layer.
  2. In Properties, click + add effect… and choose cutout.
  3. Wait a moment. Properties shows a preview of the cut-out subject.
  • You can also open the command palette (⌘/ / Ctrl+/), type cutout and pick the effect.
  • The cut-out is made once and saved in the project, as assets/.cutouts/<name>-<code>.png. The code comes from the photo. A changed photo gets a new cut-out. An old cut-out file is never written over.
  • The cut-out goes with the project. In a shared project it syncs through Dropbox, like the other assets. In a local project it is in the project folder and in its versions.
  • The cut-out file does not show as a tile. It shows on the canvas and in exports.
  • To make a cut-out, a Mac needs macOS 14 or later and the Xcode Command Line Tools (they include Swift).
  • Windows cannot make a cut-out. It shows the cut-out that a Mac saved in the project.
  • Older versions of Starlight kept each cut-out on one computer only. The first time Starlight uses such a cut-out, it moves it into the project.
  • A media: photo, or an online-only photo in Dropbox, must be available offline first.
  • To compare with and without the cut-out, bypass the effect, that is, turn it off for a moment (Bypass an effect).
  • On any platform, a generation can also remove the background, for a cost. Pick the option transparent (remove background after) when you generate.

"cutout not made yet – open on a Mac to make it". You see this line at the bottom left of the canvas when a layer has a cutout effect, no Mac has made its cut-out yet, and this computer cannot make it. The layer shows the whole photo until the cut-out is there. Properties shows the same words. To fix it:

  1. Open the project on a Mac that has the Xcode Command Line Tools.
  2. Open each scene that uses the photo. The Mac makes the cut-out and saves it in the project.
  3. In a shared project, wait for Dropbox to sync the new file in assets/.cutouts/. In a local project, copy the project folder to the other computer again.
  4. Open the scene again on the other computer. The line goes away and the layer shows the cut-out.
  • On a Mac without the tools, the line says install the Xcode Command Line Tools on this Mac, or open on another Mac, to make it.
  • If Vision finds no subject in the photo, the line says no foreground subject found. Use another photo, or remove the background with a generation.
  • Make all cut-outs on a Mac before you export on Windows. Without its cut-out, the layer is the whole photo.

Add and use a colour LUT

A LUT (look-up table) is a .cube file that applies a colour look, for example a film grade.

  1. In the Assets panel, click import… and pick the .cube file. It shows as a LUT tile.
  2. Select the layer you want to change. To change everything below it, use an adjustment layer (Adjustment layers).
  3. In Properties, click + add effect… and choose lut.
  4. In the effect's file list, pick the .cube file.
  5. Set strength (0 to 1) to mix the look with the original colours.
  • The + button beside the file list imports a .cube and picks it in one step.
  • Dragging a .cube file into the window does not import it. Use import… or +.
  • Adobe and Resolve .cube files work: 3D LUTs up to size 256, and 1D shaper LUTs.
  • Under the list, a line shows the LUT's title and size, for example 33³ + 1D 1024.
  • — none — in the list turns the LUT off. A file that is gone shows as (missing).
  • If the file cannot load, an error shows under the file list, and the effect changes nothing.
  • If you edit the file on disk, the look updates.
  • The other colour effects: Colour effects.

Fonts and the fallback chain

Brand fonts are the font families listed in project.yaml under brand.fonts (Brand kit). Each family points at a file in fonts/. They load before the first frame is drawn.

  1. Drag the font file (.ttf, .otf, .woff or .woff2) into the window.
  2. Starlight copies it to fonts/ and adds it to brand.fonts. The family is named after the file: Knockout Heavy.otf becomes knockout-heavy.
  3. Select a text layer. In Properties, pick the family in the font list.
  • Did you copy a font into fonts/ with Finder (Explorer on Windows)? Click ↻ beside the font list. It finds the new file and adds it the same way.
  • Brand fonts load again when you open or switch to a project, and when a font file changes. You do not need to restart Starlight after you replace a font file.
  • Each project uses its own brand fonts and the fonts installed on this computer. It never uses a brand font from the project you had open before. Text in a family that is neither uses the fallback chain below.
  • If a family name is taken, -2 is added. A family that is already listed keeps its name.
  • In YAML, a text layer names its family like this: font: knockout-heavy. The font's own name also works: font: Knockout Heavy finds the family knockout-heavy.
  • A font that is installed on this computer works by its name too: font: Arial, font: Segoe UI Semibold (Fonts, media and LUT files).
  • Each row of the panel's fonts list shows the family, its file, and missing when the file is gone. With no brand fonts, the list says no fonts registered.
  • To swap a family's file, click ⇄ on its row in the panel's fonts list (or right-click › replace…). The family name stays, so every text that uses it updates.
  • ⇄ is also how you supply a font that shows missing.
  • After a font replace, the old file stays in fonts/. Starlight does not offer to remove it.

The fallback chain. If a brand font's file is missing, text uses a heavy condensed font instead. Starlight tries these in order: Impact, Haettenschweiler, Arial Narrow Bold, Arial Narrow, Oswald, Anton, Bebas Neue, then any sans-serif.

  • Only fonts installed on this computer count. Starlight never downloads fonts.
  • Brand fonts work offline, because they are files in the project.
  • To fix a missing font, put a bold condensed .otf file at the path that the family names. All text in that family then uses it. You do not need to edit any scene.

On this page