Telycam

Meet Telycam at Upcoming Events in 2026

Alen — Wed, 29 Jul 2026 06:55:30 +0000

Meet Telycam at Upcoming Events in 2026

Join us at leading broadcast and ProAV exhibitions worldwide. Explore our latest PTZ camera solutions, production workflows, and integrated video technologies.

September 11—14

IBC 2026: Amsterdam

A global meeting point for the media and entertainment industry, IBC connects broadcasters, technology providers, and innovators shaping the future of content creation.

RAI Amsterdam, Amsterdam, Netherlands

BOOTH LOCATION

11.A03

REGISTRATION CODE

IBC10867

August 19—22

BIRTV 2026: Beijing

One of China’s most influential broadcast and audiovisual exhibitions, BIRTV brings together industry professionals to explore the latest innovations in media technology and production workflows.

HALL

BOOTH

3010

China International Exhibition Center (Chaoyang), Beijing, China

Contact Telycam

Sales Inquiries

sales@telycam.com

Call Us

+86-755-33275155

Name

Phone Number

Email Address*

country

Message

PTZ Camera Optical Zoom Explained

Alen — Tue, 28 Jul 2026 07:49:47 +0000

PTZ Camera Optical Zoom Explained

How to Calculate Field of View for Any Room

When someone asks "how much zoom do I need for this room," the answer almost never starts with a zoom number. A 20x optical zoom PTZ camera in a small conference room and the same camera in a large auditorium produce completely different results — not because the camera changed, but because the distance did.

Optical zoom specifications tell you the ratio between a camera's widest and most telephoto focal length. They don't tell you what the camera will actually see in your specific space. For that, you need two pieces of information: the zoom specification, and the distance from the camera to the subject. Put those two numbers together, and you can calculate exactly how wide or how narrow the camera's field of view will be — and how much of the physical space it will cover at any zoom level.

That is what Telycam's Optical Zoom Calculator is built to do. Enter the distance from the camera lens, and it returns the horizontal field of view in degrees, and the actual width and height coverage in meters, across the full zoom range — from wide end to fully telephoto. This article explains the concepts behind those numbers, so you know how to interpret the results and use them to make the right camera placement and zoom selection decisions for your space.

What Is Optical Zoom, Really?

Optical zoom is a camera’s ability to magnify a distant subject by physically adjusting the lens elements inside the camera. Instead of enlarging an existing image, the lens changes its focal length to bring the subject closer while maintaining image detail.

A simple way to imagine optical zoom is switching from a wide window view to looking through a telescope. The view becomes narrower, but the distant subject appears larger and clearer without sacrificing image quality.

Unlike digital zoom, which simply crops and enlarges part of the image, optical zoom creates real magnification through the lens itself.

TECHNICAL SPECIFICATION

The 20x Magnification Logic

Optical zoom is usually described with a number such as 12x, 20x, or 30x. But this number is often misunderstood.
A 20x optical zoom lens does not mean the camera makes objects appear 20 times larger. Instead, it means the lens has a zoom range where the longest focal length is 20 times greater than the shortest focal length.

4mm → 80mm

20x

This is where most purchasing decisions go wrong. A 20x zoom number tells you the range of magnification available, but it says nothing about what the camera will actually see in a specific room. Two cameras can both be labeled "20x optical zoom" and produce completely different fields of view, because field of view depends not just on focal length but on the camera's sensor size. A larger sensor produces a wider field of view at the same focal length than a smaller one — which means zoom numbers alone are not comparable across different camera models without knowing the sensor specification.

Optical Zoom vs. Digital Zoom: Why the Distinction Matters

Optical zoom achieves magnification by physically adjusting the lens elements — changing the focal length through actual glass movement. The image quality at any zoom level is determined by the full resolution of the sensor, because the entire sensor is being used to capture the image at that focal length.

Digital zoom works differently. It takes the image the sensor has already captured and crops into the center of it, then enlarges that cropped portion to fill the frame. No additional detail is captured — the same number of pixels is simply spread across a larger apparent area. The result is a magnified image with reduced sharpness and detail, equivalent to cropping and scaling in post-production.

Imagine taking a photo on your phone, cropping the center portion, and stretching it back to full size. The subject appears larger, but no new detail has been added. As you increase digital zoom, the image usually becomes softer and less detailed.

Optical Zoom

Physical glass movement that preserves every pixel of the sensor's data.

Zero resolution loss
Mechanical precision
Consistent MTF performance

Digital Zoom

Electronic cropping of the center pixels, enlarged through software interpolation.

Loss of detail & sharpness
Visible noise artifacts
Computational "guesses"

For live production, this distinction is consequential. A PTZ camera with 30x optical zoom at its maximum telephoto end is using the full sensor to capture a narrow field of view with full resolution. The same camera using digital zoom beyond its optical range is delivering a degraded image — more magnification, less usable picture quality. When evaluating PTZ cameras for a specific deployment, optical zoom range is the relevant specification. Digital zoom is not a substitute.

Understanding Your
Optical Zoom Calculator Results

An Optical Zoom Calculator is designed to answer one essential question: From a specific shooting distance, how much of a scene will your camera actually capture?

Instead of guessing whether a PTZ camera can properly frame a stage, speaker, or large venue, the calculator precisely estimates the camera's visual coverage at both extremes of its optical range—fully zoomed out and fully zoomed in.

Once you input the shooting distance, the calculator generates six key coverage metrics: Wide HFoV, Narrow HFoV, Wide Width, Wide Height, Narrow Width, and Narrow Height. While these specs might seem dense at first glance, they simply describe the camera's field of view from two perspectives: the broadest shot possible versus the tightest close-up achievable.

Wide vs. Narrow: Understanding the Optical Range

Every PTZ camera operates across two viewing extremes:

• Wide (Fully Zoomed Out): The lens captures the broadest possible view of your space—such as an entire stage, a large classroom, or a sports field. Think of it as stepping back to look at the whole room with your naked eyes.
• Narrow (Fully Zoomed In): The lens zooms in to magnify a small target area in crisp detail—such as a presenter’s facial expressions or an athlete’s movement. It’s like picking up a pair of binoculars to focus directly on a single person across that same room.

By evaluating both extremes simultaneously at your specified shooting distance, the calculator reveals the full operational reach of the camera's zoom lens.

Understanding HFoV (Horizontal Field of View)

Wide HFoV and Narrow HFoV measure the camera's optical viewing angle in degrees at both ends of its zoom spectrum:
• A larger degree value means a broader "viewing cone"—capturing a wide arc of the scene directly in front of the lens.
• A smaller degree value narrows that cone into a magnified "tunnel"—focusing deeply on a far-off subject while cutting out the surroundings.
While degree metrics are essential for spec-sheet comparisons, angles alone don't intuitively tell you how many meters of stage space you will actually capture in a real venue.

That is where the calculator's Width and Height values come in—translating these optical angles into actionable, real-world physical measurements for your specific installation distance.

Width and Height: Practical Dimensions for Site Planning

While degree angles explain optics, Width and Height define the real-world physical area—in meters or feet—that your camera covers on the ground at your specified shooting distance:

• Wide Width & Wide Height: The maximum physical frame captured when the lens is fully zoomed out.
• Narrow Width & Narrow Height: The precise subject area framed when the lens is fully zoomed in.

These are often the most critical numbers for real-world deployment decisions.Imagine you are integrating a system for a 10-meter-wide stage. If the calculator shows a Wide Width of only 7 meters at your planned mounting position, you immediately know the camera cannot capture the full stage. Without installing a single bracket or running a single cable, the data clearly indicates you need to move the camera further back, select a model with a wider baseline lens, or adjust your mounting location.

By converting raw optical physics into actionable physical dimensions, the calculator eliminates guesswork and validates your deployment plan before on-site installation begins.

A Practical Example

Reading All Six Numbers Together

18-Meter House of Worship Deployment

To make these values concrete, consider a typical house of worship scenario: a PTZ camera mounted at the back of the room, 18 meters from the stage.

At that distance, a 20x zoom camera might return values like these:

METRIC	WIDE END	NARROW END	UNIT
HFoV	60	3.2	DEG
Width	20.78	1.01	METERS
Height	11.69	0.57	METERS

Reading these numbers together tells a complete planning story:

• At wide angle, the camera covers 20.78 meters horizontally and 11.69 meters vertically — enough to capture a large stage with room to spare, or a wide establishing shot of the entire space
• At full telephoto, the coverage narrows to just 1.01 meters wide and 0.57 meters tall — tight enough to frame a single presenter in a close-up head-and-shoulders shot
• The jump from 20.78 meters to 1.01 meters represents the full zoom range available from this camera position — every framing option between those two extremes is accessible without moving the camera

One Thing That Surprises Most People

Looking at the calculator data for 20x, 30x, and 35x cameras, something stands out: all three have the same Wide HFoV of 60°. At 18 meters, all three return exactly the same Wide Width of 20.78 meters.

18m Spatial Coverage Comparison Wide vs. Narrow Field Analysis

ZOOM	WIDE WIDTH (@ 18M)	NARROW WIDTH (@ 18M)
20x	20.78 m	1.01 m
30x	20.78 m	0.62 m
35x	20.78 m	0.63 m

* Identical 20.78m wide coverage confirms shared wide-angle baseline HFoV (60.0°).

Higher zoom doesn't make the wide end wider — it makes the telephoto end narrower. A 30x camera doesn't give you a broader establishing shot than a 20x camera. It gives you a tighter close-up at full zoom. This is one of the most common misunderstandings in PTZ camera selection, and the calculator makes it immediately visible.

How Distance Changes Everything

Of all the variables that affect what a PTZ camera can see in a room, distance is the most significant — and the most frequently overlooked. Zoom specification gets most of the attention during camera selection, but in practice, where you place the camera relative to the subject determines the outcome far more than which zoom model you choose.

The Relationship Is Linear

The mathematical relationship between distance and coverage is straightforward: double the distance, and the width and height coverage double as well. Move the camera twice as far from the subject, and every value in the calculator output scales up proportionally.

This means that camera placement is not a fixed decision that happens after the camera is chosen — it is a variable that fundamentally changes what any given camera can do in a space. A 20x camera that can't cover a wide enough stage from 10 meters away may cover it comfortably from 15 meters. A camera that produces a useful close-up from 20 meters may be too tight to use from 30 meters at the same zoom setting.

The Same Camera, Three Different Distances

To make this concrete, here are the actual calculator outputs for a 20x camera at three different distances:

DISTANCE	WIDE WIDTH	WIDE HEIGHT	NARROW WIDTH	NARROW HEIGHT
8.0m	8.96m	5.04m	0.45m	0.25m
18.0m	20.16m	11.34m	1.01m	0.57m
30.0m	33.60m	18.90m	1.68m	0.95m

At 8 meters

The wide end covers 9.24 meters — enough for a small meeting room or a tight stage setup. The narrow end covers just 0.45 meters — a very tight close-up, suitable for framing a face at short range.

At 18 meters

The wide end expands to 20.78 meters — broad enough for a large auditorium stage or a full worship space. The narrow end at 1.01 meters is now a comfortable head-and-shoulders framing.

At 30 meters

The wide end reaches 34.64 meters — a very broad field of view that would cover even large venue stages. But notice that the narrow end is now 1.68 meters wide — what was a tight close-up at shorter distances has become a wider framing at 30 meters, because the same zoom angle covers more physical space at greater distance.

What This Means for Camera Placement

The practical implication is that camera placement decisions and zoom specification decisions cannot be made independently. They interact directly, and changing one changes the effective output of the other.

If a room has fixed camera mounting positions — wall brackets, ceiling mounts, or structural constraints that limit where the camera can go — the distance is fixed, and the zoom specification needs to be chosen to produce the right coverage at that distance. If the camera position is flexible, the distance can be adjusted to make a specific zoom specification work for the space.

This is exactly what the Optical Zoom Calculator is designed to support. Rather than guessing whether a 20x or 30x camera is the right choice for a room, you enter the actual distance from the mounting position to the subject — and the calculator tells you what each zoom specification will actually see from that position. The decision becomes concrete rather than speculative.

Real-World Scenarios:
Choosing the Right Zoom for Your Space

The zoom specification you need is determined by the distance between your camera and your subject — and nothing else. The scenarios below use actual calculator outputs to show what different zoom levels deliver in real production environments, along with the Telycam cameras that fit each context.

Scenario 01

Small Meeting Rooms (5–8 meters)

At this distance range, high zoom is rarely necessary — and can actually work against you. A wide field of view is more useful than telephoto reach when the subject is close and the room is small.

At 8 meters, a 10x camera returns:

DISTANCE	OPTICAL ZOOM	HORIZONTAL FOV	MAX COVERAGE
8m	10x	6.3° – 62.5°	8.4m Wide

The wide end covers 11.55 meters — more than enough for a standard conference table. The narrow end at 1.13 meters allows for a tight individual framing when needed. In most small meeting room deployments, the camera spends the majority of its time at or near the wide end, occasionally zooming in for a closer participant view.

For this scenario, Telycam's Meet series is purpose-built — designed specifically for conference and huddle room environments where ease of setup and wide-angle coverage matter more than long-distance zoom reach.

Scenario 02

Houses of Worship (15–25 meters)

This is the most common PTZ deployment scenario, and the one where zoom selection has the most visible impact on production quality. The camera needs to cover the full stage at wide angle while being able to zoom in tightly enough to frame a presenter in a usable close-up.

At 18 meters, here is what a 20x and 30x camera each deliver:

COMPARATIVE DATA @ 18M

20X OPTICAL

1.2m — 19.8m

Operational Width

30X OPTICAL

0.8m — 19.8m

Operational Width

Both cameras produce identical wide-end coverage — 20.78 meters — because they share the same 60° Wide HFoV. The difference is at the narrow end: the 30x camera zooms in to 0.62 meters, producing a significantly tighter close-up than the 20x's 1.01 meters.

For most houses of worship at this distance, 20x provides a comfortable zoom range — wide enough for full-stage coverage, telephoto enough for a usable presenter close-up. If the camera is at the far end of a larger sanctuary, or if very tight facial close-ups are a production priority, 30x adds meaningful telephoto reach.

For 4K output at this distance, the Vision+ 4KN is available in both 20x and 30x configurations — choose based on how tight a close-up your production requires. For broadcast-grade requirements, the Explore (20x) covers this distance range with a 1-inch sensor, while the Explore SE (30x) adds additional telephoto reach for larger sanctuaries.

At this distance, the wide end of most PTZ cameras is broad enough to cover the full stage without difficulty. The critical question shifts to the narrow end: can the camera zoom in tightly enough to produce a usable close-up of a presenter at 30+ meters?

At 30 meters, a 20x vs 30x comparison:

CONFIG @ 30M	NARROW FOV	WIDTH
20x Zoom	3.4°	1.8m
30x Zoom	2.3°	1.2m

Scenario 03

Large Auditoriums and Lecture Halls
(25–40 meters)

At 30 meters, the 20x narrow end covers 1.68 meters — a mid-shot framing rather than a tight close-up. The 30x narrows to 1.04 meters, producing a much more usable presenter close-up at this distance. For large auditoriums where close-up presenter shots are part of the production, 30x is the more appropriate specification.

The Vision+ 4KN 30x covers this scenario well for 4K production. For broadcast-grade deployments at this scale, the Explore SE with its 30x zoom and 1/1.8-inch sensor is the purpose-built option.

Scenario 04

Large Venues and Sports Facilities
(50 meters and beyond)

At distances of 50 meters or more, the coverage numbers shift dramatically. Wide-end coverage becomes very broad — potentially too broad for practical use — while the narrow end determines whether the camera can deliver any usable close-up at all.

The wide end at 57.74 meters is too broad for most practical shots — at this distance, the camera will spend most of its time in the middle or upper range of its zoom, not at the wide end. The narrow end at 1.73 meters produces a reasonable presenter framing, though tighter than a traditional close-up.

For venues at this scale, 30x is the practical minimum for any usable telephoto reach. Camera placement strategy also matters significantly — a camera at 50 meters is often better served by being repositioned to 30–35 meters where the zoom range is more operationally useful across its full range.

The Explore SE (30x, broadcast-grade) is the appropriate specification for large venue deployments where both image quality and telephoto reach are non-negotiable requirements.

TECHNICAL CALCULATOR OUTPUT: 30X @ 50M

2.3°

NARROW H-FOV

2.0m

NARROW WIDTH

63.7°

WIDE H-FOV

60.1m

WIDE WIDTH

FAQ

Why does the actual footage look different from what the calculator predicted — with the top and bottom of the frame cut off?

What Is NDI High Bandwidth?

Alen — Fri, 24 Jul 2026 01:24:55 +0000

What Is NDI High Bandwidth?

The Standard for Broadcast-Quality IP Video

NDI made it possible to move video through standard IP networks instead of traditional SDI cables. But as production demands increased — higher resolutions, lower latency, and broadcast-quality workflows — another question emerged: how do you send the highest-quality video over IP without compromise?

That's where NDI High Bandwidth comes in.

Designed for professional live production, NDI High Bandwidth prioritizes image quality and real-time performance, delivering visually lossless video with extremely low latency over standard network infrastructure. In this guide, we'll explain what NDI High Bandwidth is, how it differs from other NDI formats, and where it fits in modern broadcast and AV workflows.

What Is NDI? A Quick Foundation

NDI — short for Network Device Interface — is a software protocol developed by NewTek that enables video, audio, and metadata to be transmitted and received over a standard local area network.

Before NDI, getting video between devices meant dedicated point-to-point connections: one SDI cable from camera to switcher, another from switcher to monitor, another from replay to graphics. Every signal required its own physical path. NDI replaces that model with a shared network approach — devices discover each other automatically, and any source on the network can be received by any compatible device on the same network, without additional cabling or routing hardware.

NDI is not a single standard but a family of versions, each making a different trade-off between image quality, latency, and bandwidth consumption. Understanding which version is which matters in practice, because the differences between them are significant enough to affect production decisions.

The three versions in current use are:

FULL SPEED

NDI High Bandwidth

The highest-quality version of the NDI protocol. Using intra-frame SpeedHQ compression, it delivers visually lossless video with sub-frame latency — typically less than 16ms at 1080p60. Bandwidth requirements scale with resolution: 100–150 Mbps for 1080p60, rising to 250 Mbps or more for 4K60.

Up to 150 Mbps

Sub-frame Latency

HX3 HYBRID

NDI|HX3

The practical sweet spot for most modern production environments. It uses short-GOP H.264 or H.265 compression to reduce bandwidth to around 8–40 Mbps at 1080p60 — a fraction of NDI High Bandwidth — while maintaining latency low enough for real-time live switching. For multi-camera deployments on standard gigabit networks, HX3 is typically the most efficient choice.

8–40 Mbps

Live Switching Ready

HX2 REMOTE

NDI|HX2

Optimized for bandwidth-constrained environments — remote production, campus distribution, and networks where video shares infrastructure with other traffic. Using long-GOP H.265, it achieves bitrates as low as 2–16 Mbps, low enough to run reliably over standard Wi-Fi. The tradeoff is latency: HX2 typically introduces 100–300ms of delay, which makes it unsuitable for live switching but practical for monitoring feeds, secondary distribution, and recording.

2–16 Mbps

Remote Distribution

This guide focuses on NDI High Bandwidth — the version designed for professional live production where image quality and switching performance are the priority.

What Is NDI High Bandwidth?

NDI High Bandwidth — also referred to as Full NDI — is the version of the NDI protocol that prioritizes image quality and low latency above all else, transmitting broadcast-grade video over a standard ethernet network without the quality compromises that higher compression introduces.

Think of it as the FLAC of video transmission. Just as FLAC preserves the full audio signal with minimal compression while MP3 discards detail to reduce file size, NDI High Bandwidth preserves virtually all of the original image data while using only the compression necessary to make network transmission practical. The result is video that is functionally indistinguishable from the uncompressed SDI signal coming out of the same camera.

The codec that makes this possible is SpeedHQ — an intra-frame compression format where every frame is compressed independently, with no reference to surrounding frames. Because each frame contains its complete image data, a receiver can decode and display it immediately without waiting for additional reference information. This is what enables NDI High Bandwidth's defining performance characteristic: latency of less than one frame — typically under 16ms at 1080p60 — fast enough to be effectively invisible in a live production context.

LATENCY

<16ms

Sub-frame end-to-end

TYPICAL BITRATE

150

Mbps

1080p60 Stream

COLOR DEPTH

bit

4:2:2 Color Support

Visually Lossless Image Quality

NDI High Bandwidth operates at 100–150 Mbps for 1080p60, scaling to 250 Mbps or more for 4K60. To put that in context, a standard streaming video might use 5–15 Mbps; NDI High Bandwidth carries ten to fifty times that data rate, preserving color accuracy, edge sharpness, and fine detail at a level that is indistinguishable from uncompressed SDI to the human eye. For productions where image quality is non-negotiable — broadcast output, large-venue IMAG screens, color-critical monitoring — this is the relevant standard.

Sub-Frame Latency

The latency of an NDI High Bandwidth stream at 1080p60 is typically under 16ms — less than a single frame at that frame rate. In practice, this means that what the camera sees and what appears on the production monitor or switcher output are effectively simultaneous. For live applications where timing precision matters — multi-camera switching, large-screen audience display synchronized with live audio, or fast-motion sports replay — this level of latency is what separates a system that feels immediate from one that feels slightly behind.

Why "Intra-Frame" Matters:
The Secret Behind Low Latency

NDI High Bandwidth's low latency isn't a marketing claim — it's a direct consequence of how the video is compressed. Understanding the difference between intra-frame and inter-frame compression makes it clear why some video formats can be switched live without hesitation, and others can't.

Two Ways to Compress Video

Every video compression system faces the same fundamental challenge: raw video contains an enormous amount of data, and transmitting or storing all of it is expensive. The solution is to find and remove redundancy — information that doesn't need to be stored explicitly because it can be inferred from something else.

There are two fundamentally different approaches to doing this:

Inter-frame compression looks for redundancy across multiple frames. If a background stays the same from one frame to the next, there's no need to store it again — only the parts that changed need to be recorded. This is how most consumer video formats work: H.264 and H.265, the codecs used in streaming services, YouTube, and most cameras, all use inter-frame compression. The efficiency gains are significant — bitrates drop dramatically — but there's a structural cost. To decode any given frame, the decoder may need information from frames that came before it, and sometimes frames that come after it. It has to wait until it has enough reference data before it can produce a complete image.

Inter-frame

Commonly used in H.264/H.265 (HEVC), this method looks for changes between multiple frames.

Requires Frame Buffer

01. Smaller file sizes for streaming.
02. High CPU load for encoding.
03. Significant Latency (100ms+).

Intra-frame

The NDI High Bandwidth / SpeedHQ standard. Every single frame is its own complete picture.

Independent Frames

01. Ultra-low CPU overhead.
02. Instant frame access.
03. Near-Zero Latency (<16ms).

Intra-frame compression takes the opposite approach. Each frame is compressed entirely on its own, with no reference to any other frame. SpeedHQ, the codec NDI High Bandwidth uses, works this way. Every frame is a self-contained unit — complete, decodable, and displayable the moment it arrives. There is no waiting for reference frames, no buffering, no dependency on what came before.

Why This Matters for Live Production

The practical consequence of intra-frame compression is immediate: a receiver can display each frame the instant it arrives, without needing to accumulate a buffer of surrounding frames first. This is what produces sub-frame latency.

Inter-frame compression introduces what engineers call decoder latency — the time the decoder spends waiting for enough reference frames to reconstruct the current one. In a consumer streaming context, this is invisible: a few hundred milliseconds of buffering doesn't affect the viewing experience. In a live production context, it's a different situation entirely.

Consider a technical director cutting between cameras on a live switcher. If the incoming signals have 200ms of decoder latency, the image on the monitor is already 200ms behind what the camera is actually seeing. That delay affects the timing of every cut, every graphic overlay, every piece of audio that needs to be synchronized with the image. It's the difference between a production that feels immediate and one that feels like it's running slightly behind itself.

NDI High Bandwidth eliminates this problem at the source. Because SpeedHQ compresses each frame independently, there is no decoder latency to accumulate. The signal arrives and displays in under 16ms — close enough to real time that it has no practical effect on production timing decisions.

A Simple Way to Think About It

Imagine two ways of writing a book. In the first version, every page is complete and self-contained — you can open it to any page and read it immediately. In the second version, some pages say "same as page 1, except change paragraph 3" — more efficient in terms of space, but you have to find page 1 before you can read any page that references it.Intra-frame compression is the first book. Inter-frame compression is the second. NDI High Bandwidth uses the first approach, which is why it can be decoded and displayed immediately, frame by frame, as each one arrives.

NDI High Bandwidth vs. NDI HX:
What's the Real Difference?

NDI High Bandwidth and the HX variants are not competing products — they are different tools designed around different priorities. Choosing between them is not a question of which one is better, but which one is the right fit for a specific production environment and network infrastructure.

The Core Design Philosophy

NDI High Bandwidth is built around a simple principle: deliver the highest possible image quality with the lowest possible latency, and let the network infrastructure handle the bandwidth requirement. It does not attempt to be efficient with bandwidth — it uses what the signal needs.

The HX variants invert that priority. They are designed to work within the constraints of networks that cannot support the bandwidth NDI High Bandwidth requires — whether that's a network shared with other traffic, a remote connection with limited capacity, or a deployment with too many concurrent streams for a gigabit network to carry. The compression they use reduces bandwidth significantly, but introduces latency as a structural consequence of how inter-frame codecs work.

This is not a flaw in the HX formats. It is the designed tradeoff. HX3 minimizes that latency penalty while still achieving meaningful bandwidth reduction. HX2 accepts higher latency in exchange for dramatically lower bitrates.

Side-by-Side Comparison

← Scroll to compare →

	NDI High Bandwidth	NDI HX3	NDI HX2
Codec	SpeedHQIntra-frame	H.264 / H.265Short-GOP	H.265Long-GOP
Bandwidth (1080p60)	100–150 Mbps	8–40 Mbps	2–16 Mbps
Bandwidth (4K60)	250+ Mbps	~50–80 Mbps	~20–40 Mbps
Latency	<16msSub-frame	~1 frameLive switching ready	100–300msNot suitable for live switching
Image Quality	Visually losslessYUV 4:2:2	High qualityHardware-friendly	GoodOptimized for low bitrate
Streams on 1 GbE	5–6 streamsat 1080p60	20–40 streamsat 1080p60	50–100 streamsat 1080p60
Best For	Live switching, IMAG, broadcast monitoring	Multi-camera IP deployment, 4K on GbE	Remote production, campus distribution, Wi-Fi
Network Requirement	Dedicated 1 GbE minimumIsolated AV network recommended	Standard 1 GbEShared network feasible	Low bandwidth networksWi-Fi compatible

The Decision in One Line

If your network can support the bandwidth and your production requires live switching — NDI High Bandwidth.
If bandwidth is constrained but latency still matters — HX3.
If bandwidth is the primary constraint and latency is acceptable — HX2.

What NDI High Bandwidth Actually Replaces in a Production Workflow

Understanding what NDI High Bandwidth is technically is one thing. Understanding what it changes in a real production setup is another. This section looks at what NDI High Bandwidth practically replaces — and what that means for how a production is built and operated.

1. SDI Cables and Dedicated Video Infrastructure

The most direct replacement NDI High Bandwidth offers is the SDI cable. In a traditional multi-camera setup, each camera requires its own dedicated coaxial SDI run from the camera position to the switcher — one cable per signal, routed through walls, floors, or cable trays, each terminating at a dedicated SDI input on the switcher or router.

NDI High Bandwidth replaces that model with a network connection. A camera with NDI High Bandwidth support sends its video signal over ethernet — the same infrastructure already running through most buildings for internet and data. The switcher, running compatible software or hardware, receives that signal over the network without a dedicated video cable. For venues with existing ethernet infrastructure, this means camera positions can be placed anywhere a network port exists, without the cost or disruption of running dedicated video cabling.

2. Hardware Capture Cards

In a software-based production workflow — using applications like vMix, OBS with NDI plugins, or Resolume — bringing a camera signal into the production computer traditionally requires a capture card: a hardware device that converts an SDI or HDMI signal into data the computer can process.

NDI High Bandwidth eliminates this requirement. A compatible camera on the same network appears as a source directly in NDI-compatible software, without any intermediate hardware. The signal is already in a format the software can receive and process natively. For productions built around software switchers, this removes a category of hardware from the signal chain entirely.

3. Single-Direction Signal Flow

Traditional SDI infrastructure is point-to-point and unidirectional — a cable carries one signal in one direction. Getting a return feed back to a camera position for talent monitoring requires a separate cable run in the opposite direction.

NDI operates on a network, where bidirectional communication is inherent. A camera sending NDI High Bandwidth to a switcher can simultaneously receive a program return feed, a prompter feed, or a confidence monitor signal over the same network connection. The infrastructure that carries the outgoing video signal also carries everything coming back — without additional cabling.

4. The Practical Limit

None of this eliminates the need for infrastructure planning. A gigabit network running five or six NDI High Bandwidth streams at 1080p60 is operating near its practical capacity. Mixing NDI High Bandwidth traffic with general office or venue network traffic on the same infrastructure creates congestion that affects video reliability. The standard recommendation — and the one that makes NDI High Bandwidth genuinely comparable to SDI in terms of operational reliability — is a dedicated AV network, isolated from general data traffic, with a managed switch that can prioritize video packets.

Within those parameters, NDI High Bandwidth delivers what SDI delivers, over infrastructure that most venues already have or can install at significantly lower cost than dedicated video cabling.

For productions using Telycam’s Explore and Explore SE cameras with native NDI High Bandwidth support, video sources can be discovered directly on the network after connection, enabling seamless integration with compatible switchers and production software without the need for external conversion devices.

Network Requirements: What You Actually Need

NDI High Bandwidth performs like broadcast infrastructure when the network supporting it is built like broadcast infrastructure. The most common source of NDI reliability problems — dropped frames, stuttering video, intermittent signal loss — is not the protocol itself. It's a network that wasn't designed to carry the load.

This section covers what a reliable NDI High Bandwidth network actually requires, and the mistakes that most commonly cause problems in practice.

The Baseline: Gigabit Ethernet

NDI High Bandwidth requires a minimum of gigabit ethernet (1 GbE) — a 1000 Mbps network connection — at every point in the signal chain. This means the camera, the switch, the cables between them, and the receiving device all need to support and operate at gigabit speeds. A single 100 Mbps link anywhere in the chain creates a bottleneck that limits the entire connection to that speed — which is not sufficient for even a single 1080p60 NDI High Bandwidth stream.

In practice, this means verifying that:

• The camera's ethernet port operates at gigabit speeds
• The network switch supports gigabit on every port being used
• The patch cables are Cat6 or higher. Cat5e technically supports gigabit speeds, but under the sustained high-bandwidth load of NDI High Bandwidth streams, it is more susceptible to electromagnetic interference and can introduce micro-packet loss that disrupts video reliability. For new installations, Cat6 is the practical minimum. For PTZ camera deployments using PoE power delivery, Cat6A is the stronger recommendation — its thicker conductors handle both the higher data rates and the heat generated by PoE power delivery more reliably than Cat6.
• The receiving computer or hardware switcher has a gigabit network interface

How Many Streams Can a Gigabit Network Handle?

A gigabit network has 1000 Mbps of theoretical capacity. In practice, the safe operating threshold is around 80% of that — approximately 800 Mbps — to leave headroom for network overhead and prevent congestion-related packet loss.

At 150 Mbps per 1080p60 stream, a gigabit network running at 80% capacity can reliably handle five to six concurrent NDI High Bandwidth streams. Beyond that, the network begins to saturate, and video quality becomes unreliable.

For productions that need more concurrent streams — or that need to run 4K at 250 Mbps per stream — a 10 gigabit ethernet (10 GbE) network is the practical upgrade path. 10 GbE provides ten times the capacity of a gigabit network, allowing significantly more concurrent streams or higher-resolution sources without congestion.

1GbE Network (800Mbps Safe Threshold) ~7 Full NDI Streams (1080p60)

10GbE Network (8Gbps Safe Threshold) ~70+ Full NDI Streams (1080p60)

Dedicated AV Network vs. Shared Infrastructure

This is the single most important infrastructure decision for NDI High Bandwidth reliability. Running NDI video traffic on the same network as general office or venue data traffic — internet browsing, file transfers, cloud backups, VoIP calls — creates competition for bandwidth that can cause video to stutter or drop frames unpredictably.

The standard practice for professional NDI deployments is a dedicated AV network: a separate network infrastructure, or at minimum a separate VLAN on a managed switch, that carries only video traffic. General data traffic stays on its own network. The two don't compete for the same bandwidth.

This doesn't necessarily mean running entirely separate physical cabling — a managed switch with proper VLAN configuration can provide logical separation on the same physical infrastructure. What it does mean is that the network carrying NDI High Bandwidth traffic should be treated as production-critical infrastructure, not as a general-purpose data connection.

Managed Switches vs. Unmanaged Switches

Not all network switches are appropriate for NDI High Bandwidth deployments. Consumer-grade and unmanaged switches — the kind commonly used in home networks and small offices — lack the configuration options needed to prioritize video traffic and handle the sustained high-bandwidth load that NDI High Bandwidth produces.

A managed switch provides several capabilities that matter for NDI:

QoS (Quality of Service): The ability to prioritize video packets over other traffic types, ensuring that NDI streams are not delayed by lower-priority data when the network is under loadI

GMP Snooping: A feature that manages multicast traffic efficiently, preventing NDI streams from being broadcast to every port on the switch regardless of whether that port has a receiver subscribed to the stream

Port-level monitoring: The ability to see traffic levels per port, which makes diagnosing bandwidth problems significantly easier

For any NDI High Bandwidth deployment beyond a single camera to a single receiver, a managed switch is the correct infrastructure choice.

What to Avoid

Wi-Fi for Full NDI

Wireless interference and packet retransmission create jitter that is incompatible with professional production standards. Use NDI|HX only if wireless is unavoidable.

Daisy-chaining Switches

Every hop between switches adds latency and creates a bandwidth bottleneck at the uplink port. Use a Star Topology with a central core switch.

Consumer Routers

Standard home routers lack the processing power (CPU/RAM) to handle hundreds of thousands of video packets per second, leading to device crashes.

Real-World Scenarios Where NDI High Bandwidth Makes Sense

NDI High Bandwidth is not a universal solution — it performs well within a specific set of conditions, and understanding those conditions is what determines whether it's the right choice for a given production. The following scenarios represent the environments where its combination of image quality and low latency delivers genuine operational value.

Multi-Camera Studio and Live Switching

This is the core use case NDI High Bandwidth was designed for. A studio with multiple cameras — whether three PTZ cameras in a house of worship, six cameras in a corporate broadcast facility, or a university lecture capture setup — can replace SDI infrastructure with a dedicated gigabit network, connecting each camera directly to a hardware or software switcher over ethernet.

The operational benefit goes beyond cabling simplicity. In a traditional SDI studio, adding a camera means running a new SDI cable. In an NDI High Bandwidth studio, adding a camera means connecting it to the network — the same infrastructure that's already in place. For permanent installations that expect to evolve over time, this flexibility has real long-term value.

Houses of Worship

Houses of worship represent one of the most common NDI High Bandwidth deployment environments, and for good reason. The typical production profile — multiple fixed camera positions, a weekly live stream, a small or volunteer production team — aligns closely with what NDI High Bandwidth offers: broadcast-quality video over existing ethernet infrastructure, with minimal operational complexity once the system is configured.

The ability to monitor and control cameras from a central location over the same network that carries the video signal simplifies the production workflow significantly. A single operator can manage multiple NDI-capable PTZ cameras, receive their feeds on a software switcher, and output the program stream — all from one network-connected workstation.

Corporate and Hybrid Events

Hybrid meeting environments — where part of the audience is in the room and part is remote — benefit specifically from NDI High Bandwidth's low latency and bidirectional network capability. Cameras send high-quality video to the production system over ethernet; return feeds, presentation slides, and remote participant windows travel back over the same infrastructure. The result is a production environment that can be assembled and reconfigured quickly without dedicated video cabling for each source.

For corporate events in venues with existing ethernet infrastructure, NDI High Bandwidth allows broadcast-grade production quality without the cost or logistics of deploying SDI equipment.

Software-Based Production Workflows

Productions built around software switchers — vMix, OBS with NDI plugins, TriCaster, Wirecast, or similar applications — benefit directly from NDI High Bandwidth's native software compatibility. Compatible cameras appear as sources in the software without capture cards or intermediate hardware, and the software can output NDI High Bandwidth streams to monitors, recorders, and other devices on the same network.

For content creators and small production teams working with software-based tools, this removes a layer of hardware that would otherwise be required to get camera signals into the production computer.

FAQ

1. How much bandwidth does NDI High Bandwidth require?

What Is an SFP+ Port?

Alen — Thu, 16 Jul 2026 09:58:28 +0000

What Is an SFP+ Port?

How Fiber Optic Transmission Works for Live Production

Every video cable has a distance limit. Copper-based connections like SDI and ethernet work well within a controlled environment — but push them beyond their rated range and signal quality drops, reliability suffers, and the footage you're counting on may not arrive cleanly at the other end.

For productions where the camera and the control room aren't in the same room — or even the same building — that limit becomes a real operational constraint. SFP+ ports exist to solve it. By accepting interchangeable fiber optic modules directly in the camera or switcher, they extend video transmission from meters to kilometers without signal degradation or additional conversion hardware.

This guide explains what SFP+ ports are, how fiber optic transmission works, and how to choose the right setup for your production environment.

The Distance Problem:
Why Copper Has a Ceiling

Before understanding what SFP+ does, it helps to understand the problem it solves.

Copper cables carry video signals as electrical current. As that current travels along the cable, it naturally loses strength over distance — a phenomenon called signal attenuation. The higher the data rate being transmitted, the faster that attenuation occurs. This is not a manufacturing defect or a quality issue. It is a physical property of electrical transmission that applies to every copper cable regardless of brand or specification.In practical terms, this means every copper-based video connection has a reliable distance limit:

Standard ethernet (Cat6) — approximately 100 meters before signal degradation becomes a problem

3G-SDI coaxial cable — approximately 100 meters on standard broadcast coax

12G-SDI coaxial cable — approximately 45–50 meters on standard cable, because the higher frequency attenuates faster over the same distance

These limits are workable in a studio or conference room. They become a real constraint the moment a production scales up — a camera on the far end of a stadium, a PTZ unit mounted at the back of a large auditorium, or a signal that needs to travel between buildings on a campus. At those distances, copper runs out of range before the signal reaches its destination.

The conventional workaround is a signal repeater — a device placed mid-run that receives the degraded signal, amplifies it, and sends it on. This works, but it adds hardware, introduces another potential failure point, and in the case of 12G-SDI, requires a repeater rated for that specific data rate. For long or complex runs, the repeater chain becomes its own infrastructure problem.

Fiber optic cable solves this differently — not by amplifying the signal mid-run, but by using a transmission medium where attenuation is so low that the signal arrives intact over distances that copper cannot approach.

What Is an SFP+ Port?

An SFP+ port — short for Small Form-factor Pluggable Plus — is a standardized, hot-swappable interface slot found on professional cameras, switches, and video equipment that accepts interchangeable transceiver modules for video or data transmission.

If that definition sounds technical, here's a simpler way to think about it. An SFP+ port is like an empty socket on your camera — a standardized slot that doesn't do anything on its own. What you plug into it determines how the signal travels. Insert a copper module and you get a short-range electrical connection. Insert a multimode fiber module and you get reliable transmission up to several hundred meters. Insert a single-mode fiber module and you can send video several kilometers without signal loss. Same port, completely different capability depending on the module.

This is the fundamental difference between SFP+ and a fixed video output like a BNC or HDMI connector. A BNC port is always a BNC port — it carries an electrical signal over copper, and that's the only thing it does. An SFP+ port is a platform. The module you choose determines the transmission medium, the distance, and the signal type.

In the context of a professional PTZ camera, this modularity has a direct practical benefit: the camera can be deployed in a standard studio setup using a copper SFP+ module for short runs, then redeployed in a large venue using a fiber module for long-distance transmission — without any external conversion hardware, without additional boxes in the signal chain, and without changing the camera's physical connection to the switcher or router it feeds into.

How Fiber Optic Transmission Works

Understanding why fiber optic cables can carry video signals so much further than copper comes down to one basic difference: copper cables carry electricity, and fiber optic cables carry light.

Electricity vs. Light: Why It Matters

When a video signal travels through a copper cable, it moves as electrical current. Electrical current naturally loses strength as it travels — the longer the cable, the weaker the signal gets. This is the attenuation problem described in the previous section, and it's the reason every copper connection has a practical distance limit.

Fiber optic cables work differently. Instead of carrying electrical current, they carry pulses of light through a thin strand of glass or plastic — roughly the diameter of a human hair. The video signal is converted into light at one end, travels through the fiber, and is converted back into an electrical signal at the other end. Because light in a glass fiber loses far less energy over distance than electrical current loses in copper, the signal arrives much further down the line with far less degradation.

Two Additional Advantages

No electromagnetic interference
Electrical signals in copper cables can be disrupted by nearby electrical equipment, power lines, motors, and other sources of electromagnetic interference. Light signals are immune to this entirely. In environments like sports stadiums, concert venues, hospitals, or industrial facilities — where large amounts of electrical equipment operate simultaneously — fiber optic cables maintain signal integrity where copper would struggle.

Electrical isolation
Because fiber carries light rather than electricity, there is no electrical connection between the two ends of a fiber cable. This eliminates ground loop problems — a common source of image noise in copper-based video systems where equipment at different points in a building runs at slightly different electrical potentials.

Single-Mode vs. Multimode Fiber

Not all fiber optic cable is the same. There are two main types, and the difference between them affects how far the signal can travel:

Multimode fiber has a wider core — typically 50 or 62.5 microns in diameter — which allows light to travel through it along multiple paths simultaneously. This makes it less expensive to manufacture and easier to work with, but it also means the light pulses spread out slightly over distance, which limits reliable transmission to around 300–550 meters depending on the cable and module specifications.

Single-mode fiber has a much narrower core — typically 9 microns — which forces light to travel in a single straight path. This dramatically reduces signal degradation over distance, allowing reliable transmission of 2km, 10km, 20km, or even further depending on the module used. Single-mode fiber is the standard for any installation where the camera and the control room are in different buildings, or where cable runs extend across a large outdoor venue.

Multimode fiber

Core Size:50-62.5 microns
Max Distance:300m - 400m
Light Source:LED / VCSEL

Single-mode Fiber

Core Size:9 microns
Max Distance:10km - 40km+
Light Source:Laser

For most permanent installations in large venues, single-mode fiber is the practical choice — the cable itself is inexpensive, and the distance flexibility it provides is worth the slightly higher cost of single-mode SFP+ modules.

SFP+ Modules: Choosing the Right Fiber Solution for Live Production

An SFP+ port provides production systems with great flexibility, but the port itself is only the starting point. The actual transmission performance depends entirely on the SFP+ module installed.

Different SFP+ modules support different transmission media, distances, and use cases. The key is not to choose the “most powerful” option, but to select the module that best matches your physical layout, distance requirements, and budget.

The Main Types of SFP+ Modules

Copper SFP+ modules (DAC cables)
These modules use a short copper cable rather than fiber, and are designed for connections within a rack or between devices sitting very close together — typically 1 to 10 meters. In video production, they work well for connecting equipment inside a control room or broadcast rack, such as linking a switcher to a router or network storage. One important limitation: DAC cables do not support PoE (Power over Ethernet), so they cannot be used to power a camera at the other end. For camera connections specifically, even over short distances, most engineers use standard network cable instead — which supports PoE and is more flexible in the field.

Multimode fiber modules
These modules use multimode fiber cable and operate at an 850nm wavelength, supporting transmission distances of around 300 to 550 meters. They are a practical choice for large indoor venues — a university auditorium, a conference center, or a mid-sized sports arena — where the camera and control room are in the same building but beyond the range of copper. Multimode modules are generally less expensive than single-mode equivalents, making them cost-effective for shorter long-distance runs.

Single-mode fiber modules
These modules use single-mode fiber cable and operate at 1310nm or 1550nm wavelengths, supporting much longer distances — available in 2km, 10km, 20km, and 40km variants. Single-mode is the right choice when cameras and the control room are in different buildings, when cable runs cross outdoor spaces, or when future flexibility in camera placement matters. While single-mode modules cost slightly more than multimode equivalents, the fiber cable itself is actually less expensive than multimode cable — making single-mode the more cost-effective option for longer permanent installations.

DAC (Direct Attach Copper)

Medium: Twinax Copper
Distance: 1m - 7m
Latency: Ultra-Low

Best Use Case: Local Control Room & Rack-to-Rack Patching

Multimode (MMF)

Wavelength: 850nm
Core: 50/125µm (OM3/4)
Distance: Up to 400m – 550m

Best Use Case: Intra-Building & Medium-Scale Venues

Single-Mode (SMF)

Wavelength: 1310nm / 1550nm
Core: 9/125µm (OS2)
Distance: Up to 10km / 40km

Best Use Case: Long-Distance, Cross-Campus & Virtual Production

Three Common Mistakes

Mismatching modules at each end
Both ends of a fiber connection must use compatible modules — the same fiber type, the same operating wavelength, and compatible distance ratings. Pairing a single-mode module (1310nm) at the camera with a multimode module (850nm) at the switch will result in no signal, even if both modules physically fit their respective ports.

Choosing the wrong distance rating
SFP+ modules are rated for specific maximum distances. A 2km-rated module used on a 5km run will produce a failed or unreliable connection — the signal degrades before reaching the other end. When specifying modules for a permanent installation, always choose a distance rating that comfortably exceeds the actual cable run to account for any additional losses from connectors and patch panels.

Using the wrong fiber cable type
Single-mode modules require single-mode cable, and multimode modules require multimode cable. The two look similar from the outside, but their internal glass cores are not compatible. The industry uses color coding to help distinguish them: multimode fiber is typically orange or aqua, and single-mode fiber is yellow. Mixing them will result in no signal even over a short distance.

SFP+ in Video Production: Real-World Applications

With the technical foundation in place, it's worth looking at where SFP+ fiber transmission actually shows up in professional video production — and why it's become a standard part of broadcast infrastructure rather than a specialist solution.

The 12G-SDI and SFP+ Combination

In professional live production, 12G-SDI is widely used for transmitting uncompressed 4K60 video over coaxial cable. However, copper-based 12G-SDI connections are typically limited to around 45–50 meters, which can become a challenge in large venues, studios, and outdoor productions.

An SFP+ interface provides a flexible way to extend these workflows over fiber. By using a compatible transmission module, cameras with SFP+ connectivity can send professional video signals through fiber links over much longer distances — from hundreds of meters to several kilometers — while maintaining stable signal quality and low latency.

The exact signal format carried through SFP+ depends on the camera’s internal design and supported modules. Some systems use SDI-over-Fiber transmission, while others rely on IP-based video workflows, so module compatibility should always be confirmed before deployment.

For production environments where long-distance signal transport is required, a built-in SFP+ interface can simplify system design by reducing the need for external conversion equipment. Telycam’s Explore SE features a native SFP+ interface, giving production teams a flexible fiber connectivity option for demanding broadcast and live event applications.

Where SFP+ Fiber Makes a Practical Difference

Large sports venues and stadiums

Camera positions in a stadium can be hundreds of meters from the broadcast control room — press boxes, field-level positions, and overhead rigs regularly exceed copper's reliable range. Fiber runs to these positions are standard practice in broadcast venues, and SFP+ modules allow modern PTZ cameras to connect directly into that fiber infrastructure without external conversion boxes.

Outdoor events and festivals

Large outdoor productions involve significant amounts of electrical equipment — stage power, lighting rigs, generator sets — that generate electromagnetic interference capable of disrupting copper cables. Fiber carries light rather than electrical current, making it completely immune to EMI. This physical property makes fiber the reliable choice for outdoor multi-camera setups where cable runs cross areas of high electrical activity.

Healthcare and secure facilities

Hospitals and government facilities present two specific challenges that fiber handles uniquely well. In medical environments, equipment like MRI machines generates powerful electromagnetic fields that can interfere with copper-based video signals — fiber's immunity to EMI makes it the only practical choice in these spaces. In secure government or defense facilities, fiber offers an additional advantage: because it carries no electrical current and emits no electromagnetic radiation, it is significantly more resistant to signal interception than copper, making it the preferred transmission medium where signal security matters.

Multi-building campus and permanent installations

Universities, corporate campuses, and houses of worship with multiple buildings need to share video across distances that copper cannot span without repeaters. Single-mode fiber can cover an entire campus on a single cable run. For permanent installations specifically, fiber infrastructure is a long-term investment — the cable doesn't degrade the way copper can in high-flex or high-humidity environments, and single-mode fiber's distance headroom means the infrastructure remains useful as equipment is upgraded over time.

SFP+ vs. Other Long-Distance Solutions

↔ Scroll horizontally to view full table

Solution / Interface	Native SFP+ Fiber	Standard RJ45 Copper	SDI Coax + Repeaters	HDMI Extenders
Physical Medium	Optical Fiber (Single-Mode / Multimode)	Twisted Pair Copper (Cat6 / Cat6A)	75Ω Coaxial Copper Cable	Cat6 Copper / Active Optical Cable
Max Reliable Distance	Kilometers to Tens of Kilometers (10km - 40km)	Strictly limited to 100 Meters (328 ft)	~200m (Requires inline repeaters every 50-100m)	50m - 100m (Dependent on extender chipsets)
Signal & Quality	100% Lossless (Supports high-bandwidth Full NDI)	Protocol dependent (Full NDI lossless / HX compressed)	100% Lossless (Baseband uncompressed SDI)	Lossy (Usually undergoes lightweight compression)
Transmission Latency	Microsecond-Level (Near-Zero)	Ultra-low (Limited only by network encoding delay)	Absolute Zero Latency	Low to Medium (Dependent on processing chipsets)
EMI Immunity	100% Immune (Complete electrical isolation)	Weak (Prone to stage power & lighting interference)	Weak (Prone to ground loops & RF noise)	Very Weak (HDMI handshake is highly sensitive to EMI)
Deployment Complexity	Medium (Requires selecting SFP+ modules & fiber)	Extremely Low (Plug-and-play, supports PoE power)	Medium (Requires separate power runs for repeaters)	High (Requires dedicated TX/RX hardware units & power)
Best Use Cases	Professional broadcast, massive stadiums, cross-building campuses, XR virtual production	Small-to-mid studios, localized IP workflows, distributed networks	Traditional studios, OB vans, local uncompressed legacy patching	Live streaming events, basic conference rooms, light-duty extensions

FAQ

Q1. Why Not Just Use an External Fiber Converter Instead of an SFP+ Port?

Telycam + Bitfocus Companion

Alen — Fri, 10 Jul 2026 07:28:02 +0000

Telycam + Bitfocus Companion

Flexible PTZ Camera Control for Modern Production

Telycam’s official Bitfocus Companion module brings professional PTZ camera control directly into the Companion ecosystem, allowing operators to manage Telycam cameras through a flexible and customizable production workflow.

Supporting Telycam’s Explore, Vision, and Drive series, the module provides seamless integration with Companion, enabling users to control essential camera functions from the same interface used to manage other production devices.

Bitfocus Companion goes beyond traditional hardware controllers. Whether you are using a Stream Deck, a web browser, a laptop interface, a touchscreen device, or other Companion-compatible controllers, Telycam cameras can be integrated into a unified control environment that adapts to your workflow.

From individual operators building a custom control setup to professional teams managing complex production environments, Telycam + Bitfocus Companion provides a scalable and flexible approach to PTZ camera operation.

Full Camera Control, All from One Surface

The v1.2.0 module brings all essential Telycam camera functions into Companion, giving operators a unified control interface across every stage of live production.

PTZ & Focus Control

Pan, tilt, zoom, and focus in real time with full 8-direction diagonal movement. Store and recall up to 50 camera presets instantly.

Image Parameters

Adjust white balance, exposure, WDR, backlight compensation, and noise reduction on the fly. Mirror and flip controls included.

Auto-Tracking

Enable/disable tracking on demand, switch between head and body framing, and manage target switching. Supports blackboard area detection.

System Control

Wake, sleep, switch day/night mode, and set tally light status (off, red, or green) all from the same surface.

Quick Setup Guide

Connect Telycam PTZ Cameras with Bitfocus Companion

Getting started with Telycam and Bitfocus Companion is simple. In just a few steps, operators can install the official Telycam module, connect their PTZ cameras, and create a customized control workflow for their production environment.

Watch the step-by-step guide below to see how to configure the module, assign camera controls, and build your own Companion interface.

How to Set Up Telycam PTZ Cameras in Bitfocus Companion

Install Bitfocus Companion
Download and install the latest version of Bitfocus Companion, then launch the Companion interface to begin configuration.

Add the Telycam Companion Module
Navigate to Connections and search for “Telycam PTZ IP Camera” in the Companion module registry. Add the module to your workspace.

Connect Your Telycam Camera
Enter your camera’s IP address to establish the connection. Once connected, Telycam PTZ cameras can be controlled directly from the Companion interface.

Customize Your Control Layout
Create personalized control pages for different workflows, such as camera operation, preset management, or production scenes. Simply drag and drop Telycam actions to build your preferred interface.

Connect Your Preferred Control Surface
Use Companion with a variety of control options, including Stream Deck, Xkeys, web interfaces, or other supported devices, and keep your workflow consistent across different production environments.

Flexible Applications

Versatile control solutions designed for various professional production environments.

Live Events & Staging

Build customized operator panels for dynamic productions, giving teams quick access to essential camera controls.

Broadcast & Live Streaming

Support multi-camera production with fast camera switching, preset recall, and centralized PTZ control for live workflows.

Corporate AV & Enterprise

Simplify control across meeting rooms, presentation spaces, and multi-room environments with a unified interface.

House of Worship

Create simple, reliable camera workflows that allow teams and volunteers to operate confidently with minimal training.

Education & Hybrid Learning

Enable smarter classroom production with easy camera control, auto-tracking support, and streamlined lecture capture workflows.

Home Studio & Creation

Build a streamlined studio workflow with PTZ control, OBS integration, and customizable production actions.

Total Control. One Surface.

The official Telycam Bitfocus Companion module gives operators the flexibility to create customized PTZ control workflows that match their production needs. By bringing Telycam cameras into the Companion ecosystem, users can combine camera operation with a wide range of control interfaces and production tools in one unified workflow.

Designed for scalable and flexible deployments, Telycam + Bitfocus Companion supports everything from individual operator setups to professional broadcast, live event, and Pro AV environments.

The module is free and available now. To get started, open Bitfocus Companion and search for “Telycam PTZ IP Camera” in the global registry.

Contact Telycam

Sales Inquiries

sales@telycam.com

Call Us

+86-755-33275155

Name

Phone Number

Email Address*

country

Message

Genlock Explained: How Multi-Camera Synchronization Works in Traditional and IP-Based Live Production

Alen — Wed, 08 Jul 2026 06:57:29 +0000

Genlock Explained

How Multi-Camera Synchronization Works in Traditional and IP-Based Live Production

Multiple cameras are expected to behave like a single system — whether you're producing a live broadcast, a sports event, or a virtual production. But every camera has its own internal clock, and without a way to keep those clocks in sync, even perfectly functioning equipment can fall out of step. That's the problem Genlock was designed to solve.

In this guide, we'll explain what Genlock is, how it synchronizes multiple cameras to a shared timing reference, and why it remains relevant in both traditional SDI workflows and modern IP-based production environments. We'll also cover when Genlock is essential, when it isn't, and how it relates to technologies like NDI and PTP.

Why Cameras Fall Out of Sync: The Root Cause

Before getting into how Genlock works, it helps to understand why the problem exists in the first place.

Every camera — regardless of manufacturer or model — has an internal crystal oscillator that drives its video timing. This oscillator determines when each frame starts and ends, and it runs continuously from the moment the camera is powered on. The problem is that no two oscillators are perfectly identical. Even cameras of the same model, produced in the same factory, will have oscillators that run at slightly different rates — differences measured in parts per million, but differences nonetheless.

In a single-camera setup, this doesn't matter. There's only one clock, and everything downstream follows it. In a multi-camera setup, it creates a structural problem. Each camera is running on its own independent clock, and those clocks are not coordinated with each other. Over the course of a broadcast, they drift — slowly but inevitably moving out of phase with one another.

The consequence becomes visible at the moment of a camera cut. A video switcher transitions between sources by selecting a new input at a specific point in time. If Camera 1 and Camera 2 are not synchronized to the same frame boundary — meaning they don't start and end their frames at the same moment — the switcher may capture part of one frame from Camera 1 and part of the next frame from Camera 2 at the moment of transition. The result is a torn image, a flash of visual noise, or a brief color artifact at the cut point.

This is not a malfunction. It is the expected behavior of unsynchronized video sources. Genlock addresses it by giving every device in the system a single shared timing reference to lock onto — eliminating the independent clocks problem at its source.

What Is Genlock?

Genlock — short for Generator Locking — is a broadcast synchronization technology that locks all video devices in a production system to a single shared timing reference signal, ensuring every camera and device starts and ends each frame at exactly the same moment.

In practice, this means that instead of each camera running on its own independent internal clock, every device in the system receives a master reference signal and adjusts its timing to match. The result is a production where any camera can be cut to at any moment without the timing mismatches that cause visual artifacts at the transition point.

Think of it like an orchestra. If every musician plays to their own internal sense of rhythm, the notes may be individually correct but collectively out of time. A conductor gives everyone a shared beat to follow. In a video production system, the sync generator — or a designated master camera — plays the role of that conductor, and every other device locks its timing to that beat.

The master timing signal can come from a dedicated sync generator, a piece of hardware whose sole job is to produce a stable reference, or from a designated master camera that distributes its own timing to the rest of the system.

The Two Reference Signal Types

Not all Genlock signals are the same. Two formats are in common use, and which one applies depends on the resolution of your production:

Black Burst is the older of the two standards, originating in the analog broadcast era. It carries a composite sync signal used to align standard-definition video devices. Despite its age, Black Burst remains in widespread use in facilities that still operate legacy SD equipment or hybrid SD/HD environments where backward compatibility matters.

Tri-Level Sync is the standard for high-definition and ultra-high-definition production. It operates at a higher frequency than Black Burst, which translates to greater timing precision and lower jitter — both important factors when synchronizing cameras at 1080p, 4K, or higher frame rates. Most modern professional cameras, including PTZ cameras designed for broadcast use, accept Tri-Level Sync as their Genlock reference input.

Genlock vs. Frame Sync vs. Timecode:
What's the Difference?

These three terms appear regularly in multi-camera production discussions, and they are frequently confused with one another — sometimes used interchangeably when they shouldn't be. Each one addresses a different aspect of the synchronization problem, and understanding the distinction between them changes how you approach a production setup.

Genlock: Preventive Synchronization

Genlock operates at the source. It locks every device's internal clock to a shared reference before any video is captured, ensuring that all cameras start each frame at exactly the same moment. The synchronization is continuous and real-time — as long as every device remains locked to the reference signal, the system stays in sync frame by frame throughout the entire production.

Core Mode: Hardware-Level

The Proactive Approach

"It prevents timing mismatches from occurring in the first place, rather than correcting them after the fact."

The key characteristic of Genlock is that it is proactive. It prevents timing mismatches from occurring in the first place, rather than correcting them after the fact. This is why it is the preferred method when physical infrastructure allows — it eliminates the problem at its source.

Frame Sync: Corrective Synchronization

A frame synchronizer — often called a frame sync — takes a different approach. Rather than locking the source device to a reference, it accepts an incoming signal that is already out of sync and corrects it at the receiving end by buffering the signal and re-timing it to match the local reference.

Core Mode: Buffer-Based

Handling Remote Feeds

Introduces 1-2 frames of latency to correct timing mismatches reactively. Essential for remote production where physical reference cables aren't feasible.

Frame sync is reactive. It doesn't prevent the timing mismatch — it receives a misaligned signal and fixes it before it reaches the switcher. The tradeoff is latency: buffering and re-timing a signal introduces a delay of one to two frames, which may be acceptable for some production scenarios but problematic for others, particularly where real-time monitoring or talent IFB feeds are involved.

Frame sync is the standard solution when Genlock isn't possible — most commonly in remote production, where cameras are in different physical locations and running a Genlock reference cable between them is not an option.

Timecode: Not Sync, But Reference

Timecode is frequently mentioned alongside Genlock and frame sync, but it serves a fundamentally different purpose. Timecode doesn't synchronize devices in real time — it labels each frame with a timestamp, typically in hours, minutes, seconds, and frames (HH:MM:SS:FF).

Core Mode: Metadata Identification

The Post-Production Solution

Solves alignment problems on the timeline. Ensures multi-camera edits can be perfectly matched after the shoot.

In live production, timecode is used to correlate what happened at a specific moment across multiple recording devices — useful for post-production editing, replay systems, and logging. In a multi-camera setup, timecode ensures that the editor can align footage from different cameras to the correct point in the timeline, even if those cameras were never physically synchronized during the shoot.

The practical distinction is this: Genlock and frame sync solve the real-time switching problem. Timecode solves the post-production alignment problem. They address different stages of the workflow, and in a well-configured production, all three are typically used together.

How the Three Work Together

In an ideal production setup, the relationship between the three looks like this:

Genlock keeps all local devices locked to the same frame boundary in real time

Frame Sync brings any remote or asynchronous sources into alignment at the point of entry into the local system

Timecode is recorded on every source, providing a frame-accurate reference for any post-production work that follows

None of the three replaces the others. Genlock without timecode leaves you with clean live switching but no post-production reference. Timecode without Genlock gives you a post-production tool but no real-time sync. Frame sync without timecode handles the incoming signal but doesn't label it for later use. Together, they form a complete synchronization architecture.

Genlock in Traditional SDI Production

In a traditional SDI production environment, Genlock is not an optional refinement — it is a foundational part of how the system is designed. Every professional SDI facility, from a television broadcast studio to a live event truck, is built around a central timing reference that all devices lock to.

How the Signal Chain Works

The standard configuration starts with a sync generator — a dedicated hardware device whose sole function is to produce a stable, continuous reference signal and distribute it throughout the facility. From the sync generator, the reference signal runs via 75-ohm coaxial cable to every device in the system: cameras, switchers, graphics systems, media servers, monitors, and recording devices. Each device has a Genlock input — typically a BNC connector labeled "Genlock," "Ref In," or "Sync In" — where it receives the reference and locks its internal pixel clock and frame timing to it.

Once every device is locked, the entire system operates on a single shared clock. Frame boundaries are aligned across all sources, and the switcher can transition between any two of them at any moment without producing a timing artifact.

In larger facilities, the reference signal is routed through a distribution amplifier (DA) — a device that takes one reference output and splits it into multiple identical, isolated copies. This ensures that every device receives the same signal at the same voltage and waveform level, regardless of cable run distance.

PTZ Cameras and Genlock in Multi-Camera Deployments

PTZ cameras present a specific advantage in Genlock deployments compared to shoulder-mounted or handheld cameras: they are fixed installations. Because a PTZ camera stays in one place, running a Genlock reference cable to it is a one-time infrastructure decision rather than an ongoing operational challenge. Once the cable is run and the camera is locked, it stays locked for every subsequent production in that space.

This makes PTZ-based multi-camera setups particularly well suited to permanent Genlock configurations — houses of worship, conference centers, broadcast studios, and university lecture theaters where the same camera positions are used repeatedly.

Telycam's Explore and Explore SE both include native Genlock input support, allowing them to lock directly to a facility's master reference signal without external conversion or additional hardware.

Genlock in IP and NDI-Based Production

Traditional Genlock solves the synchronization problem in SDI environments cleanly and reliably — but it relies on physical reference cables running to every device in the system. As production workflows move toward IP-based video transport, maintaining that dedicated physical infrastructure becomes harder, and in some scenarios, impossible. A camera at a remote location, a graphics system running on a software platform, or a virtual production environment built around real-time rendering can't always accept a coaxial Genlock signal. This is where IP-based synchronization approaches come in — and where the relationship between Genlock and newer protocols becomes important to understand.

The Core Challenge: IP Networks Don't Carry Native Sync

In an SDI system, the Genlock reference signal travels on a dedicated coaxial cable, completely separate from the video signal itself. Every device gets a direct, physical connection to the timing reference.

IP networks don't work this way. Video, audio, control data, and timing information all share the same network infrastructure. Standard ethernet networks are inherently asynchronous — packets arrive with variable delays depending on network load, switch processing time, and routing decisions. There is no equivalent of a Black Burst or Tri-Level Sync signal that can simply be distributed over a standard IP network.

This means traditional hardware Genlock cannot be directly applied in a pure IP environment. A different approach is required.

PTP: The IP World's Answer to Genlock

The broadcast industry's solution is PTP — Precision Time Protocol, standardized as IEEE 1588 and adopted into broadcast workflows through SMPTE ST 2059. PTP distributes a highly accurate time reference across an IP network, allowing all connected devices to synchronize their internal clocks to a shared time base — functionally achieving what Genlock achieves in SDI environments, but over standard network infrastructure.

In a PTP system, a grandmaster clock — a hardware device with a highly stable oscillator, often GPS-referenced — distributes timing packets across the network. Connected devices receive these packets and adjust their internal clocks accordingly, achieving synchronization accuracy in the sub-microsecond range. SMPTE ST 2110, the professional IP video transport standard used in high-end broadcast facilities, uses PTP as its timing backbone — meaning that in a full ST 2110 environment, traditional Genlock is effectively replaced by PTP entirely.

NDI Workflows and the Hardware Synchronization Reality

NDI — widely used in corporate, educational, and mid-tier live production — takes a different approach. NDI does not use PTP for timing. Instead, it includes a software-based Genlock API that allows NDI-capable software applications to use an incoming NDI stream as their timing reference.

This works well for purely software-defined sources. Graphics engines, virtual sets, title generators, and replay software can all lock their output to an incoming NDI signal — keeping overlays and digital assets aligned with the main program feed without requiring a physical sync cable.

However, there is a critical limitation: NDI software Genlock only applies to software-defined sources.

Hardware cameras — including PTZ cameras — process video through onboard hardware with fixed clock timing. A PTZ camera outputting NDI High Bandwidth or NDI|HX3 generates its video based on its own internal hardware oscillator, and that clock cannot be adjusted by a software API. Even in a fully NDI-based production environment, hardware cameras still require a physical reference signal for frame-accurate synchronization across multiple devices.

This is precisely why Telycam's Explore and Explore SE retain dedicated BNC Genlock inputs alongside their NDI High Bandwidth and NDI|HX3 outputs. By feeding a physical Tri-Level Sync reference to the camera while transmitting video over the network, technical directors get the best of both worlds: the streamlined cabling of an IP workflow combined with the frame-accurate synchronization of traditional broadcast Genlock.

Virtual Production: Where Genlock Becomes Critical Again

Virtual production environments — where live cameras are composited against real-time rendered backgrounds on LED volumes or in mixed reality setups — represent one of the most demanding synchronization scenarios in modern production. Here, Genlock is not just about clean switching. It is about maintaining the precise temporal relationship between the physical camera and the virtual world it is capturing.

When a camera moves in front of an LED volume, the rendered background must update in real time to match the camera's new perspective, driven by tracking data delivered via the FreeD protocol. For the composite to look correct, the background frame the camera captures must correspond exactly to the camera's position at that precise moment. If the camera's frame timing is not synchronized to the render engine's output, the result is a virtual background that lags or drifts relative to the camera's actual movement — subtle but immediately noticeable to any attentive viewer.

Genlock eliminates this by locking the camera's frame timing to the same reference as the LED processor and render engine. For cameras like the Telycam Explore — with its 1-inch sensor capturing at broadcast-grade resolution — that frame-level alignment ensures every captured frame corresponds precisely to the rendered output, producing a composite that holds up under the scrutiny of large-screen display.

FAQ

What happens when a device loses the Genlock signal?

4K vs. 1080p: Which Is Right for Your Production Workflow?

Alen — Thu, 02 Jul 2026 08:02:52 +0000

4K vs. 1080p

Which Is Right for Your Production Workflow?

Most decisions about 4K start with a simple assumption: higher resolution means better quality. But in live production, that assumption often breaks down quickly.

Resolution is only one part of the system. Bandwidth, signal infrastructure, processing load, and even how the audience consumes the content all play a bigger role in whether 4K actually improves the final output.

This guide breaks down what actually changes between 4K and 1080p in real live production environments — and when higher resolution is worth the trade-off.

The Math Behind the Pixels

Before comparing how 4K and 1080p perform in production, it helps to be precise about what the numbers actually mean — and where the gap between them is bigger than most people assume.

1080p, also called Full HD, measures 1920×1080 pixels — that's 1920 × 1080 = 2,073,600 pixels per frame, roughly 2.07 million.

4K, or Ultra HD, measures 3840×2160 pixels — 3840 × 2160 = 8,294,400 pixels per frame, approximately 8.29 million.

Since both the width and height double from 1080p to 4K, it's tempting to call 4K "twice the resolution." In terms of actual pixel data, that's misleading: doubling both dimensions doesn't double the pixel count — it quadruples it. 4K isn't twice the image data of 1080p. It's four times.

That distinction matters beyond storage and bandwidth. Every additional pixel has to be captured, processed, compressed, transmitted, and decoded somewhere downstream — by the camera sensor, the switcher, the network, and the viewer's device.

Resolution vs. Bitrate:
The Distinction Most People Miss

Here's something that surprises a lot of people: two videos can have the exact same resolution and look completely different in quality. The reason comes down to bitrate — and understanding this one distinction will change how you think about the whole 4K vs. 1080p debate.

Think of it like this. Imagine you're describing a painting to someone over the phone. If you have an hour to describe it, you can capture every brushstroke, every shade of color, every fine detail. If you only have five minutes, you'll hit the broad strokes but lose a lot of nuance. The painting hasn't changed — but how accurately it gets communicated has.

High Bitrate

Low Bitrate

Bitrate works the same way. It's the amount of data used to encode each second of video. A higher bitrate means more data is allocated to preserve detail, handle motion cleanly, and maintain color accuracy. A lower bitrate compresses the image more aggressively — and that compression shows up as blurring, color smearing, or a "blocky" look in fast-moving scenes.

This is why a well-encoded 1080p stream can look noticeably sharper and cleaner than a poorly encoded 4K one. The 4K image has more pixels on paper, but if the encoder doesn't have enough data to represent them properly, those extra pixels end up carrying compressed, degraded information — not genuine additional detail.

In live production, this comes up more often than people expect. A team upgrades to 4K but their upload bandwidth or streaming platform settings can't support the higher bitrate 4K actually needs. The resolution goes up. The visible quality doesn't.

Resolution matters — but it's only half the equation. Bitrate is the other half, and it's the one that gets overlooked most often.

The Bandwidth Reality:
What 4K Actually Costs

Choosing 4K isn't just a camera decision — it affects everything your signal passes through before it reaches the viewer. And the biggest practical constraint most teams run into isn't the camera. It's bandwidth.

Here's a rough sense of what each resolution actually demands:

• A typical 1080p live stream runs at around 5–8 Mbps for a watchable, professional-looking output
• A 4K live stream needs roughly 20–35 Mbps to look genuinely better than 1080p — not just have more pixels

That's four to five times the upload speed, sustained, for the entire duration of the broadcast. On a stable office or studio connection, that's manageable. On a venue Wi-Fi, a 4G hotspot, or a location shoot where you don't control the network, it's a real risk.

The same gap applies inside your production infrastructure. Transmitting 1080p video over a network using NDI — a common standard for sending video between devices over ethernet — typically uses around 100–150 Mbps per stream. The 4K equivalent jumps to roughly 250–300 Mbps. A standard gigabit network connection can handle that for one or two cameras, but add more sources, monitors, and return feeds, and you'll start running into bottlenecks quickly.

The point isn't that 4K is impractical — it's that 4K has infrastructure requirements that 1080p doesn't. Before committing to a 4K workflow, the honest question to ask is: does every part of my signal chain — cameras, cables, switcher, network, and upload connection — actually support this? If any link in that chain doesn't, the extra resolution doesn't make it to the viewer anyway.

Where 4K Actually Makes a Visible Difference

After all the caveats around bandwidth and infrastructure, it's worth being clear: 4K does make a genuine difference in the right conditions. The key word is "conditions." Here's where the upgrade actually shows up on screen.

Large screens and close viewing distances

The most straightforward case for 4K is also the most obvious one: big displays, viewed up close. On a 65-inch screen across the room, most people can't reliably tell 4K from 1080p. On a large LED wall at the front of a conference room, or a monitor that presenters stand directly in front of, the difference becomes visible. If your content regularly ends up on screens larger than 55 inches and your audience sits within a few meters of them, 4K earns its keep.

Post-production flexibility

This is one of the most practical arguments for shooting 4K even when your final output is 1080p. A 4K frame is wide enough that you can crop into it significantly and still have full 1080p resolution left over. That means you can reframe a shot in post, punch in on a detail, or turn a wide horizontal shot into a vertical one for social media — all without losing quality. Shoot in 1080p and the same crop leaves you with noticeably softer footage.

Platform encoding advantages

Uploading 4K to platforms like YouTube gives you a less obvious but real benefit: the platform allocates a higher bitrate to 4K source files, even when viewers watch at 1080p. That means a video uploaded as 4K and viewed at 1080p often looks better than the same video uploaded natively at 1080p — sharper, with fewer compression artifacts. For teams producing content for YouTube, this alone can be a reason to shoot 4K even without a 4K delivery requirement.

Long-term archiving

If you're recording content that has a long shelf life — training videos, event recordings, documentary material — shooting in 4K means the footage stays usable as display technology improves. Content shot in 1080p five years ago is already starting to look dated on modern screens. The same content shot in 4K has more room to age gracefully.

Where 1080p Is Still the Smarter Choice

4K gets most of the attention, but for a significant portion of live production work, 1080p isn't a compromise — it's the more sensible decision. Here's when sticking with it makes more sense than upgrading.

01 / AUDIENCE FOCUS

Most of your audience watches on a phone

This is the single most underrated argument for 1080p in live production. The majority of live stream viewers are watching on a smartphone screen that's five or six inches across. At that size, and at typical phone-to-face distances, 4K is physically invisible — the display simply can't render the difference. Delivering 4K to a mobile audience costs you significantly more in bandwidth and infrastructure for a quality improvement that doesn't exist on their end.

02 / INFRASTRUCTURE

Your network isn't guaranteed

Live production doesn't always happen in a controlled environment with a dedicated fiber connection. Churches, corporate events, and location shoots often rely on venue Wi-Fi or mobile data — connections that can fluctuate mid-broadcast. A stable 1080p stream that never drops is a better viewer experience than a 4K stream that buffers every few minutes. Reliability matters more than resolution when you're live and can't call a retake.

03 / LOGISTICS

Storage and editing add up fast

4K files are roughly four times the size of 1080p files at the same frame rate. For a team doing regular recordings — weekly services, ongoing training sessions, frequent events — that difference accumulates quickly in storage costs and backup requirements. Editing 4K also demands significantly more from your computer: faster processors, more RAM, and often a dedicated GPU just to play back footage smoothly. For smaller teams without dedicated editing hardware, 1080p keeps the post-production workflow manageable.

04 / STRATEGY

Budget is better spent elsewhere

If the choice is between a 4K camera with a basic lens and lighting setup, or a 1080p camera with money left over for better audio, proper lighting, and a more experienced operator — the 1080p setup will almost always produce content that looks and feels more professional. Resolution is visible. Bad audio, flat lighting, and shaky framing are more visible. For teams working within real budget constraints, the 4K premium often delivers less value than investing that money in the fundamentals.

Real-World Scenarios:
When to Stay 1080p vs. When to Go 4K

The right resolution for your production isn't a universal answer — it depends on what you're producing, who's watching, and how the content gets delivered. Here's how the decision plays out across the most common live production contexts.

1. Esports and Sports Broadcasting

For fast-moving content, smoothness matters more than sharpness. A 1080p stream at 60 or even 120 frames per second will look dramatically better for live sports or competitive gaming than 4K at 30 frames per second — fast-moving subjects blur and smear at lower frame rates, and that's what the audience actually notices. On the technical side, a stable 1080p60 stream is manageable at around 6–9 Mbps. Pushing to 4K60 can spike that requirement to 25 Mbps or more, and also increases the delay between what happens on the field and what appears on screen. Unless you're feeding a large stadium display that genuinely needs every pixel, that bandwidth is better spent keeping the stream smooth and fast.

2. Large-Scale Live Events and Broadcast Production

This is where 4K earns its place without much debate. When content is going onto large venue screens — the kind where front-row audience members are sitting close enough to see individual pixels if the resolution isn't high enough — 4K becomes a practical necessity, not just a preference. There's also a post-production advantage: a 4K master recording gives editors the ability to crop, reframe, or create the effect of multiple camera angles from a single wide shot, all without losing full HD quality in the final output. Implementing 4K at this scale requires solid infrastructure — single-cable 12G-SDI connections and proper signal synchronization across all cameras. Cameras like Telycam's Explore series support native 12G-SDI output, which simplifies the cabling side of that infrastructure significantly. For productions at this level, that kind of built-in capability is usually already part of the budget conversation.

3. Remote Education and Healthcare

The smartest approach here is a split workflow: capture locally in 4K where detail is critical, but distribute over the network in 1080p. In a surgical suite or a precision lab, 4K sensors allow operators to digitally zoom into fine details — suture work, small components, delicate procedures — without physically moving the camera or losing image quality. At the same time, pushing 4K over a hospital intranet or university network creates congestion that can affect everyone on the connection. The practical solution is to record the full 4K feed locally for archiving and detailed review, while streaming a compressed 1080p version for remote participants. Both audiences get what they actually need.

4. Houses of Worship and Corporate Meetings

For weekly services, town halls, and standard corporate events, 1080p remains the most practical choice — and not just because of cost. The platforms most commonly used for this content, including YouTube Live, Zoom, and Microsoft Teams, cap or heavily compress streams well below 4K quality anyway, which means the extra resolution largely disappears before it reaches the viewer. On top of that, 4K footage generates roughly four times the storage of 1080p — around 40–50 GB per hour of raw recording — which adds up quickly for organizations producing content on a regular schedule. For small teams or volunteer-run productions, staying at 1080p keeps the workflow predictable, the storage manageable, and the technical demands within reach.

Should You Upgrade to 4K?
A Quick Decision Checklist

Before committing to a 4K workflow, it's important to understand that resolution alone does not determine system quality. A successful upgrade depends on how your content is viewed, how your system is built, and how much operational flexibility your team has.

Use the checklist below as a practical decision guide.

Your content and audience

4K only delivers visible value when the viewing environment can actually display that level of detail.

□ Will your content regularly appear on large screens — 65 inches or bigger — viewed at close range?
□ Does your audience watch on dedicated displays rather than phones or laptops?
□ Do you need to produce both horizontal and vertical versions of the same content?
□ Will the footage be archived for long-term use or repurposed years down the line?

If most answers are yes

The market demand and creative utility of 4K align with your current production goals.

Your infrastructure

Even if your cameras support 4K, your system must be able to transport, process, and store that data reliably.

□ Does your signal chain support single-cable 12G-SDI or high-bandwidth NDI for 4K60?
□ Are you still relying on quad-link 3G-SDI or already near the limit of your current network?
□ Can your editing system play back 4K smoothly without proxy workflows?
□ Are your switchers, capture devices, and monitors fully 4K-ready?

If any critical part is not ready

Infrastructure bottlenecks will cause production delays and increased operational costs.

Your budget and team

A 4K upgrade affects far more than just cameras — it impacts storage, processing, and operational complexity.

□ Do you have storage capacity for files roughly four times larger than 1080p?
□ After infrastructure upgrades, is there still budget for lighting, audio, and production quality improvements?
□ Can your team comfortably manage a more demanding workflow without increasing failure risk?

If the upgrade compromises other production areas

A resolution increase is never worth a decrease in lighting quality, sound production, or storytelling depth.

The Bottom Line

← Scroll to compare →

	1080p	4K
Bandwidth Required	5–8 Mbpsfor live streaming	20–35 Mbpsfor live streaming
NDI Stream per Camera	~100–150 MbpsNDI High Bandwidth	~250–300 MbpsNDI High Bandwidth
Storage per Hour	~10–15 GB	~40–50 GB
Ideal Hardware Interface	3G-SDI / HDMI 1.4	12G-SDI / HDMI 2.0single-cable 4K60 transmission
Workflow Friction	LowPlug and play in most environments	HighRequires full infrastructure validation
Best For	Mobile audiences, live streaming, budget-conscious teams	Large LED screens, post-production cropping, broadcast delivery

Telycam's camera lineup is built around this same distinction. The Drive series is a 1080p-focused entry-level line, well suited to budget-conscious deployments where HD output and reliable distribution matter more than maximum resolution — churches, classrooms, and small conference rooms fall squarely into this category.

For productions that need 4K, the Explore series and the Vision+ 4KN / Vision+ 4KZ models provide native 4K output, suited to the large-screen delivery, post-production crop flexibility, and broadcast-grade requirements covered earlier in this guide.

Whichever resolution your workflow calls for, the deciding factor should be the production requirement — not the spec sheet.

FAQ

Do I need 12G-SDI or will standard HDMI work for 4K60 video workflows?

Explore 100/300/500 Feedback

Alen — Tue, 30 Jun 2026 03:34:23 +0000

Mix One Testing Feedback

Alen — Tue, 30 Jun 2026 03:15:38 +0000

Steady on Target: PTZ Coverage at the National Pistol Championship

Alen — Thu, 25 Jun 2026 07:43:13 +0000

Steady on Target: Telycam PTZ Coverage at the National Pistol Championship

From June 13 to 20, 2026, the National Shooting Championship (Pistol Category) was held at the Qingzhen Sports Training Base in Guizhou. The tournament brought together 396 athletes from 30 provincial delegations, competing across men's and women's 10m air pistol, the 10m air pistol mixed team event, men's 25m rapid fire pistol, women's 25m pistol, and men's 50m pistol — all scored on the ISSF-certified SIUS electronic laser system, with draws, scoring, and results processed through the official SiusRank software. In this sport, precision is the standard, not the exception.

The Challenge

Unlike field or track events, shooting unfolds in fractions of a second and within a tightly controlled environment — a combination that places unusual demands on both equipment and on-site coordination. The production team identified four core challenges going into the event:

01. Instantaneous Action

A shooter's aim, trigger pull, and point of impact happen almost instantaneously. At range, traditional manual focus and framing struggle to keep pace, risking missed footage of the exact moments that matter most.

02. Multi-Angle Complexity

A single shooting event calls for simultaneous coverage of shooter close-ups, profile stance, spectator reaction, and full-range context — coverage that traditionally requires a large camera crew to achieve.

03. Restricted Access

Shooting ranges are high-security environments by design, and personnel cannot freely enter the core competition area to adjust or reposition cameras — making remote, hands-off operation a hard requirement rather than a convenience.

04. Broadcast Standards

National-level coverage and archival footage must meet broadcast standards for resolution, long-range optical clarity, operational stability, and color accuracy.

The Blueprint: Halving the Hardware, Doubling the Range

To shatter these constraints, the technical team threw out the traditional broadcast playbook. Instead of deploying the dozens of fixed cameras typical for an event of this scale, they engineered a highly automated, six-camera remote grid using Telycam PTZ systems.

By leveraging the extreme optical reach of just two Explore cameras and four Vision+ 4KN cameras, the team slashed the required hardware count by 50%. Every single angle was managed entirely over IP from the safety of the exterior control room, proving that leaner infrastructure can deliver richer coverage.

The Camera Layout

The same six-camera configuration was used for both the 10m and 25m pistol events, with only minor adjustments in camera orientation to suit the differences between the two disciplines, starting with the layout for the Men's 10m Air Pistol Final.

Camera 1

Explore

Positioned in front of Target Stations C/D, angled to capture shooters at Stations E through H.

Camera 2

Vision+ 4KN

Positioned alongside Camera 1 on the C/D line, providing a second angle on the same group of shooters.

Camera 3

Explore

Mounted on a tripod near the left side of the R1 reference line, framing shooters at Stations A through D.

Camera 4

Vision+ 4KN

Also mounted on a tripod near R1, positioned for a broader vantage over the full range.

Camera 5

Vision+ 4KN

Positioned along the R1 side, capturing profile shots of shooters during their stance and shot execution.

Camera 6

Vision+ 4KN

Positioned behind and to the side of the firing line, alternating between wide range coverage and shots of the spectator stands.

The 25m Adjustment

The transition from the 10m air pistol events to the 25m rapid-fire discipline introduced a longer shooting distance and a change in range geometry, requiring only a minimal adjustment to the existing setup.

The six-camera system remained fully unchanged, with the only modification taking place on Camera 2 (Vision+ 4KN), which was manually reoriented on the C/D line from the shooters toward the downrange target boards.

From there, its 30× optical zoom bridged the extended 25-meter distance, delivering stable, high-clarity target imagery that complemented the SIUS scoring system without any additional hardware or signal infrastructure changes.

System Connectivity and Control Workflow

The production relied on a hybrid signal architecture designed to maximize broadcast stability while minimizing on-site cabling.

• Video Feeds: Explore cameras utilized SFP fiber links for long-distance reliability, while Vision+ 4KN ran uncompressed SDI directly into the switcher for ultra-low latency.

• Unified Power: The Explore units ran on PoE++, while the Vision+ 4KN units operated on PoE+. Both consolidated power and data onto a single cable per unit, eliminating separate power runs.

• Remote Control: PTZ commands and WebUI management ran entirely over the IP network, allowing operators to tune all camera parameters from the control room.

In the control room, production ran on a hybrid hardware-and-software workflow:

Blackmagic Design ATEM 1 M/E Advanced Panel 20 — handled real-time signal switching and live production control

AVMATRIX PKC4000 IP controller — dedicated to remote PTZ control and preset recall

vMix — served as a complementary production platform, managing multi-camera signals and handling the graphics overlay layer — athlete name bars, live scoring, and match information — composited and synced directly with the live feed

Final Results: A Week of Competition, Zero Compromises

Across both the 10m and 25m pistol events, the six-camera PTZ system delivered complete broadcast coverage — including shooter close-ups, target results, full-range context, and audience reactions — without requiring any operator access to the firing line.

The same system carried over seamlessly between disciplines with no equipment rebuild, and only a single camera required reorientation to accommodate the 25m configuration. Overall, the deployment remained compact and efficient, achieving full coverage with significantly fewer cameras than a traditional fixed setup.

With fiber-based video transmission, SDI output, and PoE-powered connectivity, the workflow remained stable and streamlined throughout the event. This allowed the production team to focus on monitoring and live coordination, while the SIUS scoring system ensured synchronized and reliable competition data for both judging and broadcast output.

"In shooting, you don't get to walk over and adjust a camera mid-match. Every position has to be right before the first shot, and it has to stay right for the rest of the competition. What surprised me most was how little hardware we actually needed — about half the cameras we'd normally bring to an event this size. Six cameras, fully remote, and we never had to put anyone where the rules said no one could stand."

— Song Jie, Broadcast Technical Lead, 2026 National Shooting Championship (Pistol)

Beyond the Range

Most live sports broadcasts come down to camera count and operator skill. Shooting takes the operator out of the equation entirely. The answer isn't more people on the floor — it's a camera network precise enough, and remote control reliable enough, that no one needs to be there at all.

As sports production continues to evolve, the traditional model of large crews and full-time manual operation is giving way to something leaner: remote-first, PTZ-driven, and built around small, highly efficient teams.

The 2026 National Shooting Championship put that shift to the test — and showed what Telycam's PTZ systems can deliver in environments defined by precision, restricted access, and zero tolerance for error. Looking ahead, Telycam will continue investing in sports broadcasting, live production, and professional imaging, building smarter, more reliable visual solutions for the events that demand them most.

Download

Contact Telycam

Sales Inquiries

sales@telycam.com

Call Us

+86-755-33275155

Name

Phone Number

Email Address*

country

Message

Telycam

Meet Telycam at Upcoming Events in 2026

Meet Telycam at Upcoming Events in 2026

IBC 2026: Amsterdam

BIRTV 2026: Beijing

Contact Telycam

Sales Inquiries

Call Us

PTZ Camera Optical Zoom Explained

PTZ Camera Optical Zoom Explained

What Is Optical Zoom, Really?

The 20x Magnification Logic

Optical Zoom vs. Digital Zoom: Why the Distinction Matters

Optical Zoom

Digital Zoom

Understanding Your Optical Zoom Calculator Results

Wide vs. Narrow: Understanding the Optical Range

Understanding HFoV (Horizontal Field of View)

Width and Height: Practical Dimensions for Site Planning

Reading All Six Numbers Together

One Thing That Surprises Most People

How Distance Changes Everything

The Relationship Is Linear

The Same Camera, Three Different Distances

What This Means for Camera Placement

Real-World Scenarios: Choosing the Right Zoom for Your Space

Small Meeting Rooms (5–8 meters)

Houses of Worship (15–25 meters)

Large Auditoriums and Lecture Halls (25–40 meters)

Large Venues and Sports Facilities (50 meters and beyond)

FAQ

What Is NDI High Bandwidth?

What Is NDI High Bandwidth?

What Is NDI? A Quick Foundation

NDI High Bandwidth

NDI|HX3

NDI|HX2

What Is NDI High Bandwidth?

Visually Lossless Image Quality

Sub-Frame Latency

Why "Intra-Frame" Matters: The Secret Behind Low Latency

Two Ways to Compress Video

Inter-frame

Intra-frame

Why This Matters for Live Production

A Simple Way to Think About It

NDI High Bandwidth vs. NDI HX: What's the Real Difference?

The Core Design Philosophy

Side-by-Side Comparison

What NDI High Bandwidth Actually Replaces in a Production Workflow

1. SDI Cables and Dedicated Video Infrastructure

2. Hardware Capture Cards

3. Single-Direction Signal Flow

4. The Practical Limit

Network Requirements: What You Actually Need

The Baseline: Gigabit Ethernet

How Many Streams Can a Gigabit Network Handle?

Dedicated AV Network vs. Shared Infrastructure

Managed Switches vs. Unmanaged Switches

What to Avoid

Wi-Fi for Full NDI

Daisy-chaining Switches

Consumer Routers

Real-World Scenarios Where NDI High Bandwidth Makes Sense

Multi-Camera Studio and Live Switching

Houses of Worship

Corporate and Hybrid Events

Software-Based Production Workflows

FAQ

What Is an SFP+ Port?

What Is an SFP+ Port?

The Distance Problem: Why Copper Has a Ceiling

What Is an SFP+ Port?

How Fiber Optic Transmission Works

Electricity vs. Light: Why It Matters

Two Additional Advantages

Single-Mode vs. Multimode Fiber

Multimode fiber

Single-mode Fiber

SFP+ Modules: Choosing the Right Fiber Solution for Live Production

Understanding Your
Optical Zoom Calculator Results

Real-World Scenarios:
Choosing the Right Zoom for Your Space

Large Auditoriums and Lecture Halls
(25–40 meters)

Large Venues and Sports Facilities
(50 meters and beyond)

Why "Intra-Frame" Matters:
The Secret Behind Low Latency

NDI High Bandwidth vs. NDI HX:
What's the Real Difference?

The Distance Problem:
Why Copper Has a Ceiling

Genlock vs. Frame Sync vs. Timecode:
What's the Difference?

Resolution vs. Bitrate:
The Distinction Most People Miss

The Bandwidth Reality:
What 4K Actually Costs

Real-World Scenarios:
When to Stay 1080p vs. When to Go 4K