System Requirements
OmniBridge runs as a single program on a small PC or mini-PC. How much computer you need depends on one thing: whether your destinations are set to transcode.
- Passthrough (transcode off, the default). Video is passed through as-is, with no re-encoding. This is light work: a small mini-PC handles it easily, and your network connection matters more than the processor.
- Transcode on. Every slot of a transcoding destination is re-encoded to a fixed picture size and frame rate (1080p30 by default). A destination has 3 slots, so this is the heavy mode, and the choice that matters most is whether the machine can encode video on its graphics hardware.
OmniBridge picks the best encoder it finds on its own: Intel graphics (VAAPI or QuickSync), then NVIDIA, and only then the main processor. You don't set this.
Passthrough (no transcode)
| Minimum | Suggested | |
|---|---|---|
| Computer | 4-core mini-PC, Intel N100 class or better | Intel N100 class or better |
| Memory | 4 GB | 8 GB |
| Storage | 200 MB free | SSD, 1 GB or more free |
| Network | Wired, 1 Gbps | Wired, 1 Gbps, its own network port |
| Handles | Up to 4 sources and 2 destinations | Up to 8 sources and 3 destinations |
On a real N100 mini-PC running 8 sources and 3 destinations, passthrough used about three-quarters of one processor core out of four.
Transcode with graphics-hardware encoding (recommended)
Needs a machine with Intel integrated graphics (most Intel Core and N-series chips from the last several years) or an NVIDIA graphics card.
| Minimum | Suggested | |
|---|---|---|
| Computer | Intel N100 mini-PC with its built-in graphics | Intel Core i3 or i5, 12th generation or newer (QuickSync) |
| Memory | 8 GB | 8 to 16 GB |
| Storage | 200 MB free | SSD, 1 GB or more free |
| Network | Wired, 1 Gbps | Wired, 1 Gbps |
| Handles | 1 transcoding destination at 1080p30 | About 3 transcoding destinations at 1080p30 |
Each additional transcoding destination adds roughly one processor core and half a gigabyte of memory. A second destination on an N100 is possible but sits right at the edge of comfortable (about two-thirds of the processor), so plan on one destination per N100 and step up to a Core i3 or i5 for more.
Transcode in software only (not recommended)
If the machine has no usable graphics hardware, the main processor does all the encoding. Each transcoding destination then needs about three full processor cores, so even one destination calls for a modern 8-core processor (for example a Ryzen 5 or a 12th-generation Core i5). This works for testing and one-off jobs, but for real shows we recommend a machine with Intel graphics or an NVIDIA card instead.
Things to know before you buy
- Measured, not guessed, on one machine. These numbers come from testing on an Intel N100 mini-PC running Debian 13 (Linux), with sources of 8 Mbps or less in H.264. Larger setups are scaled up from those measurements.
- 60 fps costs double. The figures above assume 1080p30 output. 1080p60 needs roughly twice the processing per slot, and 4K was not tested.
- Windows was not measured. Expect it to behave similarly, but we haven't put numbers on it.
- Keep it cool. A fanless mini-PC can slow itself down when it runs hot for hours, which shows up as dropped frames mid-show. For transcoding, use a machine with active cooling or good airflow.
- When a feed drops, the load goes up. Each source or destination showing the "no signal" slate costs a little processor time (about a fifth of a core each), and that happens right when something has gone wrong. Leave headroom for it.
- NVIDIA cards can limit simultaneous encodes. Some consumer NVIDIA drivers cap how many video encodes run at once, and each transcoding destination uses three. Check NVIDIA's current limit for your card before relying on it.
- Network. A single 1 Gbps port is plenty for typical shows. See the sizing table in Ports and Troubleshooting for how much traffic your source and destination counts add up to.