Sixty, Seventy-Two, Ninety: The Frame Rate Conversation Your Venue Isn't Having

There's a particular sound in an immersive venue about four minutes into a screening. Not a gasp, not a laugh. A slight shuffle, a hand finding the headset strap, someone leaning back to see if the horizon has stopped wobbling. Front-of-house staff know it. Producers often don't, because by the time the feedback form comes back it's been filed under "content" or "the headset was heavy" rather than the number nobody wrote down.

Frame rate is the least glamorous variable in spatial media and, in our experience of watching UK test screenings go sideways, one of the most decisive. It's baked into the name of this site for a reason. Sixty isn't a slogan — it's a floor that a lot of work quietly falls below, and it's the difference between a piece that feels effortless and one that asks the audience to work.

What sixty actually buys you

In a flat 24fps film, judder is a look. It's part of the grammar, and our brains have spent a century learning to read it. In a headset, judder is a fault. The moment the viewer controls the camera, their vestibular system starts cross-checking what their eyes report against what their inner ear is telling them, and a low frame rate hands it a discrepancy to chew on.

The friction is worse in 360° than in most other formats because the whole frame is in play. Pans that would be a graceful blur on a cinema screen become a stutter at the edge of vision, where peripheral motion sensitivity is highest. Add a stereo pair and you're doubling the work per frame while asking the eyes to converge on something that keeps slipping.

Sixty frames per second doesn't make anyone feel awe. It makes them stop noticing. That's the job.

The headroom question

Seventy-two and ninety exist, and they're not vanity. Ninety is common on standalone headsets because it lines up neatly with display refresh and gives reprojection less to do. It's genuinely better on fast lateral movement, on handheld capture, and on anything where the camera travels rather than sits.

But be honest about the bill. Going from 60 to 90 is fifty per cent more frames to capture, stitch, encode, decode and cool. In practice the storage and bitrate penalty often runs higher than the raw frame count suggests, because encoders work less efficiently on shorter runs of similar data. On a location shoot, that extra throughput has a physical cost: more cards, more offload time, more heat in the rig, more battery pulled from the same enclosure that's already powering two sensors and a fan.

The pragmatic split we'd suggest is by motion, not by ambition. Stately observational pieces, gallery installations where the viewer mostly stands and looks: 60 is fine and the saved budget goes further on lighting or sound. Anything with a moving camera, a moving subject crossing the near field, or a fast head-turn moment: reach for 72, and for 90 if the headset can hold it without dropping frames under load.

A caveat worth pinning to the wall: a locked 60 beats a stuttering 90 every single time. Consistency is the comfort setting. Variable frame rate in a headset reads to an audience as unreliability, and once they've felt it once they spend the rest of the piece waiting for it to happen again.

British light is the awkward variable

Here's where UK production gets specific. Our best-loved locations for capture — cathedrals, listed interiors, museum stores, railway arches, community halls with dimmable nothing — are dark. Not atmospherically dark, genuinely underlit. And our available daylight is generous with overcast softness and stingy with hours; by mid-afternoon in December you're shooting at a light level that would make a broadcast camera engineer wince.

Low light and high frame rate pull in opposite directions. More frames per second means less exposure time per frame, which either pushes you to open the aperture (killing depth of field and, in stereo, risking mismatched focus) or to raise gain and inherit noise. Noise is far more punishing in a headset than on a monitor — it's moving in your peripheral vision, and compression algorithms spend bitrate trying to describe it.

So the trade-off is real, and it's usually resolved in pre-production or not at all. Options include: adding light where the building will allow it (and starting that conversation with the custodian early, because listed-building consent is not a same-week affair); accepting 60 and using the extra exposure time; or restricting the piece's motion vocabulary so that the slower frame rate never gets tested. That last one is a legitimate creative choice, not a defeat.

Where the number goes missing

Frame rate falls through gaps because it belongs to four different people at once. The capture team sets it, the stitching and post pipeline may render at a different rate, the delivery encode has its own ideas, and the headset's refresh runs independently of all of them. A piece can be shot at 60, mastered at 30, and displayed on a 90Hz panel with reprojection filling the gaps, and nobody in the chain has done anything wrong — they've just each optimised their own bit.

A checklist to hand over before the first test screening

• State the delivery frame rate on paper, in the same document as running time and audio format. If it isn't written down, it isn't agreed.
• Confirm the headset's refresh rate and whether reprojection is active. Know what the fallback looks like when the device is warm and halfway through a busy Saturday.
• Test on the venue's actual device, not the studio's. Thermal throttling in a small, warm, screenlit room is a different beast from a cold edit suite.
• Ask whether the piece will be shown standing, seated or both. Seated audiences tolerate a lower frame rate; standing ones have more to lose.
• Run a two-minute clip with a deliberate slow pan and a deliberate fast head-turn, and watch faces rather than the screen.
• Note the ambient light in the space. A bright room changes perceived contrast and can mask or exaggerate judder.
• Agree who owns the decision if the frame rate has to drop during the run. It should not be a front-of-house call made at 6pm on a Friday.
• Book the exit-survey question properly: not "did you enjoy it" but "was there a moment you wanted to stop". That's where the frame rate tells the truth.

None of this is expensive. It's a page of questions and a willingness to write a number down. But it moves frame rate out of the realm of technical trivia and into the place it belongs — alongside seat height, audio description and running time, as part of how a piece meets the people watching it.

The 60 in 3D60 isn't a boast about specification. It's a reminder that comfort in spatial media is engineered, not wished for, and that the quietest settings are usually the ones doing the most work.