"EVS Multicam “REM” — what those 338h37m really mean (and why it matters)"
- szymborskipiotr
- 11 minutes ago
- 2 min read
EVS Multicam “REM” — what those 338h37m really mean (and why it matters)
If you work on EVS in Multicam, you’ve definitely seen REM: xxxhxxm at the top of the screen and heard someone say:
“Cool — we’ve got hundreds of hours left.”
Yes… but that number is often misunderstood.
What “REM” actually tells you
In Multicam, REM (Remaining) is EVS translating available disk capacity into time based on your current recording setup (codec/bitrate, audio, etc.).
The key point:
That remaining time is shared across all active record inputs (cameras).
So if your server shows something like REM: 338h37m, and you’re recording on multiple camera inputs, the real mental model is:
You’re looking at the total time budget for all your record trains together.
Per-camera remaining time is roughly REM ÷ number of active record inputs.
So with 8 cameras, you’re thinking in the range of tens of hours per camera, not 338 hours per camera.
You can see this in practice when you punch up a single angle and EVS shows a per-camera remaining figure — for example 44h01m17 on SILVER — while the top bar still shows the larger 338h37m total.
Why this matters in real OB reality
Because sooner or later someone will ask you:
“Are we safe to roll all day?”
“Can we keep everything ISO-recorded until tomorrow?”
“Can we add two extra cameras for the second match?”
The right answer depends on whether you’re thinking in total server time or per-input time.
REM is your early-warning system — but only if you read it correctly.
Mini checklist (fast and practical)
More record inputs = less time per camera
Higher bitrate / more audio tracks = less remaining time
Any config change mid-show can change the REM math
If you want more EVS workflows explained like this (fast, practical, OB-tested), check out Broadcast Academy — manuals + VODs built for operators and engineers:
Comments