Concept proposal · on-set workflow

Proxies in Shade minutes after cut, not at wrap.

Shadebox is a small battery-powered box that rides with each FX6. It takes the camera's proxy clips over the network as they're recorded and uploads them to Shade. Editors, producers and clients can watch takes while the crew is still on set.

1 per cameraup to three on set
0 cards pulledmedia stays in the camera
5 waysto connect camera and box

Why

Proxies wait for card swaps

Today proxies leave set when cards get offloaded, at lunch or at wrap. Post can't start, and clients can't see anything until then.

Offload takes time

Pulling cards, copying and uploading takes someone's time on every shoot day, and it's easy to miss a card or a camera.

Nobody can see what's missing

There's no single place on set showing which takes from which camera have landed in the cloud and which haven't.

How it works

Camera → box → Shade, automatically

The FX6 already has built-in FTP transfer for its proxies. Shadebox is the FTP server it sends to, plus an uploader that sends each clip on to your Shade drive.

Sony FX6 A, B & C cameras proxy + XML FTP · cable or Wi-Fi Shadebox queue · checksum · retry upload + verify set Wi-Fi · phone · cell Shade project/day/camera Editors Producers Clients

Roll

The camera records to its own cards as usual. When a take ends, the FX6 sends its proxy to the box.

Land & queue

The box only queues a clip once it has fully arrived, records a checksum, and files it by camera and shoot day. Flagged takes jump the queue.

Upload & verify

The box uploads each clip to Shade and checks that what arrived matches. If the internet drops, clips wait safely and upload when it's back.

The box is never in the live video path: the village monitor feed is untouched, and the box only ever sees finished proxy files.

Interactive prototype

This is the on-set screen. Try it.

The box has a 4.3" touchscreen. Below is its actual interface running in your browser, with three simulated cameras rolling takes. Tap around the screen, or follow the tour.

·Open full screen ↗ ·💬 Note on this screen ·Simulated data. Nothing is uploaded.

Make something happen

Proposed functions

Six screens, built for gloves and glances

Big touch targets, a dark screen that won't light up the set, and status you can read from across the cart.

◉

Home

  • A card per camera with a big status colour
  • Received, queued and in-Shade counts
  • Last take and live upload progress
  • Pause and hold-until-wrap within reach
▤

Clips

  • Filter by camera, status or flagged
  • Play on screen or on the village monitor
  • Flag, rate and add notes
  • Re-upload, or free up local space
⇄

Network

  • The FTP address to set on the camera
  • Choose cable, box Wi-Fi, camera Wi-Fi or set router
  • Uplink status: set Wi-Fi, phone or cell
☁

Shade

  • Project, shoot day and folder template
  • Bandwidth limit and hold until wrap
  • Upload XML sidecars, or skip them
  • QR code that opens the folder
⚙

Settings

  • Unit A, B or C, which sets its network address
  • Camera names
  • Brightness and sleep
  • Storage use
ⓘ

System

  • One-tap FTP and internet self-tests
  • Event log for every clip
  • Updates, reboot and safe shutdown

Built not to lose a clip

  • Only complete files count. The box queues a clip once the camera has finished sending it, never a partial.
  • Checked on arrival. Every clip is checksummed when it lands, and its size is verified on Shade after upload.
  • Outages are expected. Clips wait on the box and upload automatically when the internet returns, without counting as failures.
  • Power cuts are safe. An upload interrupted by a dead battery restarts on the next boot.
  • Low battery shuts down cleanly before the box browns out.
  • Nothing is ever deleted in Shade. "Delete local" only frees space on the box, and asks first if a clip isn't uploaded yet.
Connectivity

Five ways to connect. One address on the camera.

Each box has a fixed address, so a camera set up for box A keeps the same FTP target in every mode. The camera link and the internet uplink use separate radios.

ModeCamera ↔ boxInternetGood for
Wired, USB-C adapterFX6 → USB-C Ethernet adapter → boxBox Wi-Fi to set router, phone or cellMost reliable; handheld or rigged
Wired, USB-C directFX6 USB-C straight into the boxSameFewest parts (in research)
Wi-Fi: camera joins boxThe box makes its own networkSecond radio, phone or cellAnywhere, no set router
Wi-Fi: box joins cameraThe camera makes the networkSecond radioFallback
Wi-Fi: shared set routerCamera and box both on the routerThe routerStudio days, three cameras
UnitSet FX6 FTP server toCamera addressBox Wi-Fi name
A192.168.66.11192.168.66.21SHADEBOX-A
B192.168.66.12192.168.66.22SHADEBOX-B
C192.168.66.13192.168.66.23SHADEBOX-C
Hardware

Off-the-shelf first, pocket-sized later

Version 1 (proposed)

  • Raspberry Pi 4, chosen for its hardware H.264 playback
  • 4.3" touchscreen and HDMI out for the village monitor
  • 512 GB high-endurance card: days of proxies per camera
  • Runs off V-mount, with clean low-battery shutdown
  • Fully enclosed, one per camera

Later: tiny version

  • Custom board around a Raspberry Pi Compute Module
  • Small status display plus buttons, with full control from a phone or iPad
  • The USB-C Ethernet adapter built in, so it's one cable to the camera
  • Roughly a third of the size
Roadmap

Where it stands

Built
Upload engine. FTP in, queue, checksum, upload to Shade, verify, retry, outage buffer, pause and hold. Tested end to end on a development machine.
Built
Screen prototype. The interface on this page, running on the same interface code the box will use.
Next
Real FX6 and real Shade. Test every connection mode with a camera, and upload real proxies to a Shade test folder.
Next
On the Pi. The touchscreen app on the real box and 4.3" panel.
Later
Playback and HDMI out, the enclosure, and three units built. Then the direct USB-C mode, and a one-page connection guide for crew.
Ideas
Camera status on the box: record light, battery and card time left. One screen showing all three boxes, iPads in village browsing proxies with no internet, a Slack ping when clips land, other destinations such as Frame.io or Drive, and an end-of-day report.
Questions for SVG

What we'd like your input on

Folder structure in Shade. Is project / shoot date / camera right, or do you organise another way?
Shade access. Which drive should a box upload to, and can we have an API key limited to it?
XML sidecars. Does post want the camera's XML metadata alongside each proxy, or proxies only?
Pilot. Which upcoming shoot would make a good first test, and with how many cameras?
On set. Who would watch the box day to day: camera team, DIT or producer? That decides what goes on the home screen.
Your notes

What would you change?

Maddie, Poncho, Chris, Alex: leave a note about anything you like, don't like, would adjust or wish it could do. Notes are shared, so +1 the ones you agree with.

Loading notes…