Santacarl wrote:
I just don't know enough about networks to know if mixing E1.31 and DPP on the same network is more efficient than running multiple E1.31's. 🤷♂️
You’d probably be surprised at how little network “space” show data actually uses. Even the most extreme setups would struggle to max out a wired connection — you’d need to push around 400 universes before Ethernet bandwidth itself became a real issue. (Wireless is a different story — much easier to overwhelm there.) Here's ChatGPT response.
Rule of thumb for E1.31 (sACN) over UDP:
- 1 DMX universe (510–512 channels) @ 44 fps = ~0.24–0.25 Mbps
- That’s ~170 RGB pixels per universe
- Bandwidth scales linearly with universes × frame rate
Quick reference:
- 10 universes @ 44 fps ≈ 2.5 Mbps
- 25 universes @ 44 fps ≈ 6.2 Mbps
- 100 universes @ 44 fps ≈ 25 Mbps
Pixel counts (RGB, 3 channels/pixel @ 40–44 fps):
- 1,000 pixels (~6 universes) → ~1.3–1.5 Mbps
- 5,000 pixels (~30 universes) → ~6.5–7.5 Mbps
- 10,000 pixels (~59 universes) → ~13–15 Mbps
Notes:
- Multicast vs unicast doesn’t change payload much (just who gets it).
- 100BASE-T is plenty for most shows; the controller usually bottlenecks first.
- Dropping frame rate (e.g., 20–25 fps) roughly halves the bandwidth.
- Wi-Fi controllers (ESP-based) handle far fewer universes reliably than wired.
DDP vs. E1.31:
DDP is more efficient — about 15–30% less traffic for the same pixel count and FPS, because it avoids the per-universe overhead.
- 1,000 pixels → ~1.0–1.2 Mbps with DDP (vs 1.3–1.5 Mbps E1.31)
- 5,000 pixels → ~5–6 Mbps (vs 6.5–7.5 Mbps)
- 10,000 pixels → ~10–12 Mbps (vs 13–15 Mbps)
👉 Bottom line: for wired, you’ll run out of controller horsepower or pixel power distribution long before you run out of network bandwidth.
ChiefWarrant wrote:
You’d probably be surprised at how little network “space” show data actually uses. Even the most extreme setups would struggle to max out a wired connection — you’d need to push around 400 universes before Ethernet bandwidth itself became a real issue. (Wireless is a different story — much easier to overwhelm there.) Here's ChatGPT response.Rule of thumb for E1.31 (sACN) over UDP:
- 1 DMX universe (510–512 channels) @ 44 fps = ~0.24–0.25 Mbps
- That’s ~170 RGB pixels per universe
- Bandwidth scales linearly with universes × frame rate
Quick reference:
- 10 universes @ 44 fps ≈ 2.5 Mbps
- 25 universes @ 44 fps ≈ 6.2 Mbps
- 100 universes @ 44 fps ≈ 25 Mbps
Pixel counts (RGB, 3 channels/pixel @ 40–44 fps):
- 1,000 pixels (~6 universes) → ~1.3–1.5 Mbps
- 5,000 pixels (~30 universes) → ~6.5–7.5 Mbps
- 10,000 pixels (~59 universes) → ~13–15 Mbps
Notes:
- Multicast vs unicast doesn’t change payload much (just who gets it).
- 100BASE-T is plenty for most shows; the controller usually bottlenecks first.
- Dropping frame rate (e.g., 20–25 fps) roughly halves the bandwidth.
- Wi-Fi controllers (ESP-based) handle far fewer universes reliably than wired.
DDP vs. E1.31:
DDP is more efficient — about 15–30% less traffic for the same pixel count and FPS, because it avoids the per-universe overhead.
- 1,000 pixels → ~1.0–1.2 Mbps with DDP (vs 1.3–1.5 Mbps E1.31)
- 5,000 pixels → ~5–6 Mbps (vs 6.5–7.5 Mbps)
- 10,000 pixels → ~10–12 Mbps (vs 13–15 Mbps)
👉 Bottom line: for wired, you’ll run out of controller horsepower or pixel power distribution long before you run out of network bandwidth.
Thanks "CWO"....I'm just making a logical guess! 😉
Wow....that's great information. That post should be pinned some place because I looked high and low for something to help understand bandwidth on these shows. Now I just need to look at the controllers to make sure they can handle the data dump to them.
SC
MartinMueller2003 wrote:
Personal opinion: Then choose DDP. It is FAR lighter on your network for the same amount of show data transferred. It is way easier to use. If there is a choice, I recommend DDP. (what a great setup for the line: 9 out of 10 lighting geeks choose DDP). :p
Same here — I run everything on DDP now. It really simplifies setup and keeps things much cleaner.
Santacarl wrote:
The only reason I can think of to run both on the same controller MIGHT be if you want to run Renards and pixels on the same controller? But I'm just guessing....probably showing my lack of knowledge...Haha. 🙊:sneaky:
The choice of E1.31 vs DDP is not related to the use of pixels vs AC or DC lighting channels. As a matter of fact, both DDP and E1.31 were developed for individual channel devices (like renards) and have no intrinsic support for pixels. Using E1.31 for pixel transfer is possible by accepting some deficiencies in the E1.31 protocol, such as 510 channels used instead of 512, odd universe mapping to completely fill a pixel port etc.
Santacarl wrote:
Now I just need to look at the controllers to make sure they can handle the data dump to them.
Controller | Max Pixels | Channels | Bandwidth @ 44 FPS | Bandwidth @ 20 FPS
------------------- | ---------- | -------- | ----------------- | -----------------
Falcon F16v3 | 16,384 | 49,152 | ~17.3 Mbps | ~7.9 Mbps
SandDevice E682 | 6,400 | 19,200 | ~6.8 Mbps | ~3.1 Mbps
Combined | 22,784 | 68,352 | ~24.1 Mbps | ~11 Mbps
Takeaways:
- Well under Cat5e (100 Mbps) capacity.
- DDP efficiently handles pixel data.
- PC/FPP combo mainly manages rendering and timing; network bandwidth isn’t the bottleneck.
