Glimpse
Glimpse shows your scene in the real LED room, in 3D and live. Use it to check how the work looks in the room. Make your changes on the canvas.
The room is a 3D model of the venue, with its lighting, floor reflections and glow. Every LED wall in the room shows what the canvas draws, while you work.
Before Starlight 0.2.16, Glimpse was called Previz. Only the name changed. Your token, your looks and your projects stay as they are.
Open Glimpse
Glimpse opens in a panel. It shows the room, with the live canvas on every LED wall. Each wall shows a surface (one LED output, for example N or STAGE).
- Press ⇧R / Shift+R. You can also pick Window › Glimpse (⇧R). Or right-click an empty part of the canvas and pick toggle glimpse.
- Wait while the venue (the 3D model of the room) loads. The panel shows each step and the progress, for example reading venue · 40%.
- Drag the panel by its title to dock it, that is, to attach it to the window. Beside the canvas, at canvas height, is a good place (Float, dock and pin).
- To close Glimpse, press ⇧R / Shift+R again, or press Esc in the panel.
- The command palette has it too: toggle glimpse panel.
- The panel has one header row above the room. On the left are the camera chips. On the right are walk, orbit, ▶ tour and ⚙.
- Keys you press in the panel stay in the panel. The walk keys work only after you click the room.
- The venue comes from the Glimpse site, so Glimpse needs the internet. The first open downloads it. Later opens only check it for changes.
- If the venue cannot load, the panel says could not load the venue. Under it are the reason and the venue's address. Check your connection, then click retry.
- Starlight saves where the panel is. It does not save the camera, the mode or the ⚙ settings.
What the walls show
Each wall in the room shows what the canvas draws for it, live.
- When you edit, scrub (drag through time) or play, the room follows, frame by frame. The light that the walls throw on the room follows too.
- The names connect them: a surface of your project feeds the room wall with the same name.
- The room walls
N,E1,E2,SandWgo around the room, from left to right.STAGEis the stage wall. - Upper or lower case does not matter:
stagefeedsSTAGE. An exact match wins over a match in another case. - A surface named
panoramafeeds the room walls from N to W that have no surface of their own. Starlight splits it across them, by their widths in pixels. - Any other room wall stays dark. If nothing matches, the panel says no surface named N / E1 / … or "panorama" — the walls stay dark.
- The room shows only the final picture. It never shows the selection outline, the gizmo (the handles that move a layer), or a node in the viewer (v).
- Canvas focus hides surfaces on the canvas, but not in the room. While Glimpse is open, Starlight keeps drawing the hidden surfaces for the room. Their videos keep playing.
| Room wall | Size in pixels |
|---|---|
| N | 6400 × 1600 |
| E1 | 3200 × 1600 |
| E2 | 3840 × 1600 |
| S | 4800 × 1600 |
| W | 6400 × 1600 |
| STAGE | 1920 × 1080 |
- These are the sizes of Glimpse's built-in room. Give your surfaces the same sizes, so that each one fits its room wall exactly.
Look around the room
Move the camera to see the piece from where the guests will be.
- Click a camera chip (a small button) in the Glimpse header, for example check-in. The camera flies to that place in the room.
- Click walk or orbit to move freely (see the table).
- Click ▶ tour to play the guest walk-through. Click ■ tour to stop it.
- Double-click the room to go back to the default view.
| Control | What it does |
|---|---|
| camera chips | Fly to one of the venue's camera places (entry, check-in, centre and the others). This also turns on walk. |
| walk | Click the room first. Drag to look around. Move with w a s d or the arrow keys. e goes up and q goes down. Hold ⇧ / Shift to move faster. Scroll to step forward or back. Walls, columns and the LED walls stop you. |
| orbit | Drag to turn around a point. Scroll to zoom. The camera stays inside the room: it slides along a wall or under the ceiling. |
| ▶ tour | The guest walk-through, on a loop. A camera chip, walk or orbit also stops it. The button shows only when the venue has a tour. |
| double-click the room | Back to the default view. In walk, the camera flies back to the entry place. In orbit, it frames the entry view again and keeps orbiting. It also stops the tour. |
- In a narrow panel the chips become a dropdown on the left (check-in ▾). It reads camera ▾ when you have moved away from a camera place.
- Walk, orbit and tour become a dropdown on the right (walk ▾, orbit ▾ or tour ▾).
- A row in a dropdown does the same as its button. A tick marks the current one.
- To open a dropdown from the keyboard, press ↓, ↑, ⏎ / Enter or Space on it.
- In an open dropdown, ↑ ↓, Home and End move. Type a letter to jump to a row, for example c for check-in.
- Press ⏎ / Enter or Space to pick. Esc or Tab closes it. A click outside closes it too.
- All Glimpse keys: Keyboard & mouse.
Feed size, not full size
Glimpse shows a smaller copy of each surface, called the feed. It does not show the full size.
- By default, each surface reaches the room at 1024 pixels at most on its long side. This number is the feed width. For example, N (6400 × 1600) reaches the room at 1024 × 256 at most.
- While Glimpse is open, the canvas keeps every surface at least ¾ of the feed width sharp. This holds even when you zoom out (⇧1 / Shift+1 fits every surface). Zoomed out, N reaches the room at 800 × 200.
- If you zoom the canvas in (1 is 100%), the room does not get sharper.
- So use the room to judge layout, colour, motion and how the surfaces work together. Check small details on the canvas at 100% (1).
- To review at full size, publish a look.
To change the feed width or the venue:
- Open
project.yamlfrom the project folder in a text editor. - Add a
room:block, as below. Leave out a line to keep its default. - Save the file.
- Pick File › Reload Project from Disk (⌘R / Ctrl+R).
room:
feedWidth: 1024 # 512 | 1024 | 2048
feedFps: 30 # 15 | 30 | scene
venueUrl: https://…/venues/halcyon-arena/ # default: the Glimpse site's room
feedWidthcan be 512, 1024 (the default) or 2048.feedFpsis the room rate: how often, at most, the room takes a new frame and draws. It can be 15, 30 (the default) orscene.scenemeans every new frame of the scene, at the scene's fps. A lower rate is lighter on the computer.venueUrlis the address of a venue folder. It must start withhttps:.- For a venue on this computer,
http://localhost/…,http://127.0.0.1/…andhttp://[::1]/…also work. - Starlight adds a
/at the end of the address if it is missing. - A value that Starlight cannot use is ignored. It stays in the file as you wrote it.
- A new venue address loads the new room.
Exposure, brightness and stats
The ⚙ button holds the room's light settings and shows how fast it runs.
- Click ⚙ at the far right of the Glimpse header.
- Drag a slider, or type a value. You can also middle-drag a number to open the value ladder (Edit a value).
- Press Esc, or click outside, to close it.
| Row | What it is |
|---|---|
| exposure | How bright the whole room is: 0.2 to 2 (default 0.85). |
| LED brightness | How bright the walls are: 0 to 2 (default 1). |
| room rate | How often, at most, the room takes a new frame and draws: 15, 30 or scene (every new frame of the scene). It starts at feedFps from project.yaml (30 if not set). Click a button to change it for now. |
| resolution | How many pixels the room is drawn with: 1× (the default, lighter) or 1.5× (sharper on a high-density screen, but about twice the work). Starlight keeps your choice on this computer. |
| reflections | How sharp the reflection in the floor is: low (the default, lighter) or high (as on the Glimpse site). Starlight keeps your choice on this computer. |
| feed width | The feed width from project.yaml, for example 1024 px. You cannot change it here. |
| venue | The venue from project.yaml, by its short name, for example halcyon-arena. Point at it to see the address. |
| walls fed | How many room walls show a surface of your project, for example 6/6. |
| canvas → room copy | The time it takes to copy the canvas to the walls, per frame, for example 0.8 ms/frame. It says idle when nothing changed in the last second. |
| room | The room's own frame rate, in frames per second (fps). |
- The first seven rows are under settings. The last three are under stats.
- The stats update once a second while the box is open. They show — while the venue loads.
- Tab moves between the fields inside the box.
- Exposure, LED brightness and the room rate are not saved. They go back to the defaults when you close the panel. To keep a room rate, set
feedFpsinproject.yaml.
Keep it fast
Glimpse shares the computer with the canvas. These points keep both of them smooth.
- When Glimpse is closed, it uses no computer time. It stays loaded for one minute after you close it, so it opens again at once. Docking it in a new place is instant too.
- Only surfaces that changed are copied. A still scene costs nothing.
- All the surfaces go to the room in one copy per frame. Before Starlight 0.2.30 there was one copy per surface, and on Windows each copy made the computer wait.
- The room draws only when something changes: a new frame on a surface, a camera move, the tour, or a setting. When nothing changes, it draws nothing.
- Glimpse pauses when Starlight is in the background. When you click another app, the room stops. Click Starlight and it goes on.
- The room draws at most 30 times a second by default. To change this, use room rate in ⚙ (Exposure, brightness and stats).
- By default the room uses the lighter resolution (1×) and reflections (low). Raise them in ⚙ if the computer has power to spare.
- Playing is cheap. Six surfaces at 1024 cost about 1 ms per frame on an M2 MacBook Air. The canvas plays at the scene's fps. The room takes each new frame, up to the room rate (30 a second by default).
- Keep the feed width at 1024 on a MacBook Air. At 2048 you lose about 20 fps there.
- Canvas focus saves less while Glimpse is open, because Starlight keeps drawing the hidden surfaces for the room. Close Glimpse when the canvas needs all its speed.
- The room lowers its own resolution when its frame rate drops under 40 fps. It raises it again when the frame rate recovers.
- To check the cost, keep Glimpse open and ask Claude for
playback_stats. Keep Starlight in front while it measures. It says how many times a second the room draws (room) and how many frames a second the canvas sends to the room (feed). - It also says where each frame's time went (budget): the surfaces, the Glimpse feed, the room's draw, and wait (time Starlight spent waiting, usually for the graphics chip). Starlight counts this all the time, at almost no cost.
- To find what makes the canvas slow, ask Claude to switch one Glimpse part off for one 10-second measurement at a time (
glimpseAb:no-upload,no-feed,no-room-draw). The part comes back on by itself after the measurement. The run that plays fast again names the part that costs the time.
Publish to Glimpse
Publishing puts a scene on the Glimpse site at full size. The team and the client can then review it in a browser.
On the site the scene becomes a look: the 3D room with one video per surface. There is no Publish button. You ask Claude to do it.
- Connect this computer (you do this once). Open Settings › Keys with ⌘, / Ctrl+,.
- In the Glimpse row, click Connect to Glimpse.
- Approve the code on the Glimpse page that opens in your browser. The row then shows who you are connected as.
- Save the scene (⌘S / Ctrl+S). Publishing uses the saved scene.
- In the Claude panel, ask for it, for example: publish 01-opener to Glimpse.
- Read Claude's dry run, a test that changes nothing. It says which look the publish replaces, or that it makes a new look. It shows the surfaces, any surface it skips, and which walls go empty.
- If the publish replaces a look, Claude asks you, for example: Replace the look 'Electric Forest' (made by Beti, updated 28 October 2026 at 14:05)? Check the name, who made it and the date.
- Say yes. Claude renders (makes) one H.264 video file per surface at full size and uploads them. Each surface's video is its own length, as Glimpse plays it (below).
- Starlight also uploads two smaller playback copies of each video, so surfaces play smoothly in browsers. You do not need to do anything.
Which look. You can publish into any look on Glimpse. It can be a look from Starlight or a look that someone uploaded in the browser.
- Tell Claude the name of the look, for example: publish 05-forest into the look Electric Forest. Capital letters and extra spaces do not matter.
- Claude's dry run tells you about that look: its name, who made it, how (Starlight or the browser), when it changed last, and its surfaces.
- Claude asks: Replace the look 'Electric Forest' (made by Beti, updated 28 October 2026 at 14:05)? Say yes only if this is the right look.
- Some older looks have the same name, because they were made before names had to be different. Then Claude shows each of them, with who made it, the date and its id. Tell Claude which one.
- If you do not name a look, Claude uses the look that this scene went to the last time. If the scene went to more than one look, Claude asks which one. For a new scene, Claude makes a new look.
- Two looks cannot have the same name. If the name of a new look is already used, the dry run says so. Claude asks if you want to publish into that look instead. If you do not, the new look gets the next number: Electric Forest v2, then Electric Forest v3.
- The names of Glimpse's six built-in looks are used too.
- After the publish, Claude tells you the name that Glimpse saved, for example: published as Electric Forest v2 because Electric Forest exists.
- If you publish all surfaces into a look that was uploaded in the browser, its panorama (
all) goes. If you publish only some surfaces, the other walls and the panorama stay.
Each surface's own length. Glimpse starts all walls together, and then each wall loops on its own length. So each surface's video is its own loop (Each surface's own length).
- One publish is enough for surfaces of different lengths. For example, the look Electric Forest has N and W at 10 seconds, E1 and E2 at 14.53 seconds, and S at 17.2 seconds.
- The dry run says each surface's length, for example: Each wall's movie loops on its own length: N 10 s, E1 14.53 s, E2 14.53 s, S 17.2 s, W 10 s.
- If a surface must keep the scene loop, the dry run says why, for example: N keeps the 17.2 s scene loop. N mixes a 10 s video (n.mp4) with the text "GOAL" animated over 17.2 s.
- Do not change the scene's length to give one surface another length, and do not publish the surfaces one by one for it.
The playback copies. A browser plays a very wide H.264 video slowly, so a 6400-pixel surface can stutter. The copies fix this:
- The HEVC copy has the full size of the surface. The site plays it on a computer that can play HEVC smoothly.
- The H.264 copy has half the size (at least 1920 and at most 4096 pixels wide). The site plays it on other computers and on phones.
- Your full-size H.264 video stays the master. The site plays it only when a surface has no copies.
- Each copy has the same frames as your video and no sound. It also has a full picture every second, so the surfaces stay in step.
- The copies take about 10 seconds per surface on a Mac. Starlight makes them while the earlier videos upload.
- The export monitor shows each step, for example N: HEVC copy 42 % (Follow or cancel an export).
- If a copy cannot be made, the look is still published without that copy. Claude tells you which copy is missing and why. The export monitor's message says it too.
- Some looks were published before Starlight made copies. If you publish only some surfaces of such a look, Starlight also adds the missing copies to its other walls. Their videos stay as they are. To add only the copies, ask Claude to publish the scene with no surfaces: nothing renders again.
- The Mac uses its video chip (VideoToolbox). A Windows PC uses its NVIDIA chip (NVENC) when it has one, else a slower software encoder.
- Six surfaces take about ten minutes on a MacBook Air. The publish continues in the app, even if Claude stops waiting.
- While it renders, the export monitor (the ring next to the time and the line along the bottom) shows the progress (Follow or cancel an export). You cannot start an export until it ends.
- Each video is 30 fps, unless you ask Claude for another frame rate. It goes to
renders/previz/<scene>/first (in a shared project, in Starlight's folder on this computer: these files do not sync), with its two copies beside it (.hevc.mp4and.h264.mp4). This folder is only for publishing, so a publish never replaces a file you exported with ⌘E / Ctrl+E. - While it publishes, the computer does not sleep, and quit or Open Project asks first (Quit or switch during an export).
- If the site has no device sign-in, click paste a token instead. Paste a token (a sign-in code) from the site's owner.
- Claude publishes only the surfaces named after a room wall. It skips a surface named
panoramaorall, any other surface, and a surface wider than 8192 pixels. - The dry run also warns about a surface whose size is not the room wall's size. The room then stretches that video to fill the wall.
- The dry run also names the room walls that no surface of yours feeds.
- The dry run also names every file that cannot render: missing, online-only, broken, a cutout or a transparency this machine cannot make. A real publish with such a file stops before it renders a surface. Fix the files first (When a file cannot render).
- Publishing a scene again replaces its look, after you say yes.
- If you ask Claude to publish only some surfaces, it replaces those surfaces. The look's other walls stay as they are.
- The look keeps its name and notes when you publish it again, unless you ask for new ones.
- Claude does not replace any look, yours or someone else's, until you say yes to its name.
- If a publish is cancelled or fails, Starlight deletes the files it already uploaded.
- To use a look's videos in a scene, ask Claude to pull (download) the look. Its media goes to
assets/previz/<look>/, as one version of the project. - Pulling the same look again replaces its files in place. Scenes that use them show the new videos.
The whole team and the client can see a published look. Claude publishes only when you ask.
Stages: plan in 3D
Plan a shot in 3D before you spend money on a generation. Select a surface and press ⇧S / Shift+S . The Stage panel opens beside the canvas.
Claude
The Claude panel runs Claude Code, an AI assistant, beside the canvas. You ask in plain words, Claude changes the project, and you watch the canvas.