Broadcast Monitor ยท Hardware & Performance
Match the computer, capture path, and scope settings to your real production workload.
Match the computer to the job. A few HD views are a different workload from several UHD sources, large scope windows, full-resolution traces, and simultaneous video output.
For Blackmagic capture, use a supported DeckLink or UltraStudio device with Desktop Video 14.4 or newer. Check the exact resolution, frame rate, connection, and bit depth you need.
As a practical planning target, start with a recent multicore PC, 16 GB of system RAM, and capable hardware graphics. A dedicated GPU gives more room for multiple scopes; integrated graphics should be evaluated with your actual sources and layout before relying on them for a show.
Begin with one HD source and the views you need. Add scopes while watching each pane's reported update rate and the application's responsiveness.
Plan around a desktop-class multicore CPU, a dedicated GPU, and 32 GB of system RAM as a starting budget. Several sources, full-resolution CRT traces, larger plots, decoding, and Professional video output all add work.
CPU performance still matters: some formats and analysis modes use CPU processing. Extra memory alone will not fix a CPU or GPU bottleneck.
These are planning recommendations, not certified minimum specifications or frame-rate guarantees. Development GPU checks have run on an NVIDIA GeForce RTX 4070 Ti SUPER; that is a tested reference, not a required purchase. Integrated-GPU and lower-end configurations have not yet been qualified in the documented performance tests.
For high-bit-depth SDI or HDMI measurements, choose capture hardware and a signal format that preserve that precision. A USB camera or network decoder may deliver an 8-bit converted picture even when the original camera signal had more detail. A faster GPU cannot recover information lost before capture.
Confirm that your computer has the connection and bandwidth required by your capture device. For network sources, allow enough network capacity for the formats and number of streams you plan to receive.
Use generated color bars to learn and configure the workspace, then evaluate representative video with your intended sources, scope sizes, and other production applications running. Color bars are simpler to render than some detailed or noisy footage.
Useful exposure and camera-matching scopes do not always need to update on every source frame. Half frame rate or density rendering can reduce the workload; use full-rate updates when following rapid changes matters. Tell us your sources and intended layout for help planning a setup.
A scope earns its place in a production by showing meaningful measurements and keeping up with the work. Broadcast Monitor is developed with attention to both signal accuracy and the cost of processing every frame.
For supported native capture formats, measurement scopes read the source samples directly, preserving available 10-bit and 12-bit precision instead of measuring an 8-bit picture preview. Display conversion stays separate from signal analysis.
The precision available depends on the source and capture path. A source delivered as 8-bit video remains 8-bit; the scopes do not invent missing detail.
Color calculations account for supported Rec.601, Rec.709, and Rec.2020 signal metadata. Brightness modes distinguish encoded luma from linear-light luminance, so the selected measurement has a defined meaning.
Automated checks compare optimized calculations with reference results, including native sample values, color conversions, and scope accumulation. GPU checks also compare supported measurements with CPU references.
Views of the same input share capture, and supported paths reuse conversions and GPU uploads. GPU acceleration and multicore CPU processing divide the work according to the selected tool and format. Supported audio phase, waveform, spectrum, waterfall, and level-history views also use GPU rendering, helping large displays remain responsive without repeatedly drawing their traces on the CPU.
When a scope cannot keep up, it takes the latest available frame instead of building a growing queue of old images. That keeps monitoring focused on what is happening now.
Full input resolution analyzes every source pixel. Optional reduced sampling trades spatial coverage for speed; it can miss small details. Half frame rate lowers how often waveform and vectorscope views update without changing their spatial sampling. Learn how to balance detail and responsiveness.
Signal precision, spatial sampling, and update rate are different things. Understanding the controls helps you keep useful measurements on screen while managing your computer's workload.
Maximizing a pane also helps concentrate processing on the view you are using. Hidden scope analysis pauses while input connections, file playback, and enabled audio listening continue. Restore the layout to resume current readings; the hidden meters do not keep measuring during suspension. With program output running, all panes continue rendering for that output.
Full input resolution includes every source pixel in the analysis. Reduced sampling processes fewer positions to reduce work, so a tiny highlight or brief spatial detail may be missed. Keep full resolution when those details matter.
Half frame rate makes waveform and vectorscope views update at half the input cadence, up to 30 updates per second. It leaves spatial sampling unchanged. It can suit a steady camera-matching task, while rapid changes benefit from more frequent updates.
CRT trace (GPU) connects selected samples into traces. Turning it off uses density rendering, which can reduce the workload. Connecting samples changes the visualization; it does not add measured signal detail. Supported renderers can also fall back when necessary.
Watch the update rate in each pane and evaluate your actual video, not just a test pattern. Source resolution, image complexity, plot size, scope count, and other applications all affect performance. See the computer and capture-hardware guidance.
Continue the tour, or choose any topic from the navigation above.