SupportLiveEdit AppGetting Started

LiveEdit Network : the foundation of a seamless workflow

LiveEdit is a collaborative platform designed to share all critical show data in real time, from pre-production through rehearsals to live performance. The dedicated LiveEdit network (LAN) forms the backbone of this workflow, providing flawless and synchronised communication between all system components.


Pre-production phase

To ensure optimal sharing of project data (cues, media, reviews, etc.), a stable and fast internet connection is strongly recommended. This enables near-instant synchronisation with the LiveEdit Cloud, making updates instantly available to all users and fostering seamless collaboration.


Production phase

A typical on-site LiveEdit workflow operates on a dedicated and isolated network (LAN) ensuring high-performance communication for all LiveEdit components, including:

  • LiveEdit Client: A Mac mini or Mac Studio running the LiveEdit application, managing the project.
  • LiveEdit Pro Server: The Show Controller handling all I/O operations, triggers, and automation, with up to three Pro Servers for redundancy.
  • iPads/Tablets: Used by the crew to follow cues and track show progression in real time.

iPad Power and Connectivity:

  • Preferred method: iPads Power iPads via the network using PoE+ adapters to guarantee stable operation.
  • Alternative method: If PoE+ is not feasible, ensure each iPad is powered individually at its operational location.
Warning: Always prefer wired Ethernet over Wi-Fi for critical operations.
Warning: Insufficient or unstable power supply to tablets can cause disruptions and must be carefully planned.

Internet Connectivity During Production: A stable internet connection must be available on site to maintain real-time collaborative workflows. If a temporary disconnection occurs, synchronisation will automatically resume once connectivity is restored.


The vital importance of a dedicated LiveEdit Network

Recommended network configuration:

  • Dedicated VLAN for all LiveEdit devices.
  • No inter-VLAN routing except for controlled internet access.
  • Subnet /24 assigned.
  • QoS rules prioritizing LiveEdit traffic.
  • mDNS multicast discovery enabled.


Static IP address configuration

Assign static IP addresses to critical devices:

  • Main Client : xxx.xxx.xxx.100
  • LiveEdit Pro Server Main : xxx.xxx.xxx.101
  • LiveEdit Pro Server Backup : xxx.xxx.xxx.102

Non-critical nodes can use DHCP reservations.


Additional recommendations for optimal performance

  • Use Cat6a or better Ethernet cables.
  • Deploy broadcast-grade switches and routers.
  • Ensure minimum LAN speed of 1 Gbps.
  • Monitor latency, packet loss, and bandwidth usage.


Enhanced security measures

  • Restrict device access via MAC address filtering.
  • Enable port authentication (802.1X).
  • Apply VLAN-based firewall rules.
  • Schedule regular penetration and vulnerability tests.


Internet connectivity

Internet access is required for:

  • Project synchronisation with the LiveEdit Cloud.
  • Real-time backup of project files.
  • Remote team access to project updates.

Recommended Practices:

  • Allocate separate bandwidth for cloud activities.
  • Protect internet access with strong firewall policies.
  • Ensure minimum 20 Mbps symmetrical internet speed.


Network ports requirements

The following ports must be open and unrestricted internally:

  • Port 21 - TCP - Server FTP (file transfers)
  • Port 80 - TCP - WebUI Access (Pro Server management)
  • Port 4012 - UDP - LTC Pipe (timecode transmission)
  • Port 5353 - UDP - mDNS (multicast service discovery)
  • Port 8001 - TCP - Control API (LiveEdit Pro Server control)
  • Port 8002 - TCP - Showtime API (Show timeline synchronization)
  • Port 8109 - TCP - File Server (media and data distribution)
  • Port 8111 - TCP - Orbit API (Orchestration and triggers)
  • No proxying or port filtering should be applied inside the LiveEdit VLAN.
  • HTTPS port 443 should also be open outbound for cloud services.


Common pitfalls to avoid

  • Using public Wi-Fi for critical operations.
  • Mixing LiveEdit traffic with general office traffic.
  • Neglecting static IPs for core devices.
  • Overlooking redundant power supplies for servers and network gear.


Check-list

Pre-Deployment

  1. Confirm stable internet connection availability.
  2. Verify LiveEdit Cloud synchronisation works.

Network Setup

  1. Create dedicated VLAN for LiveEdit devices.
  2. Disable inter-VLAN routing (except internet).
  3. Assign /24 subnet addressing.
  4. Prioritise LiveEdit traffic via QoS settings.
  5. Enable mDNS multicast discovery.

Hardware Setup

  1. Use Cat6a (or better) Ethernet cables for critical devices.
  2. Install broadcast-grade switches and routers.
  3. Guarantee minimum 1 Gbps LAN speed.

Device Configuration

  1. Assign static IPs to Main Client and Pro Servers.
  2. Configure DHCP reservations for non-critical devices.

Power and Connectivity

  1. Provide PoE+ power to iPads where possible.
  2. Prepare stable alternative power sources for tablets.
  3. Connect critical devices via wired Ethernet.

Internet Access

  1. Validate internet availability during production.
  2. Allocate separate bandwidth for cloud sync.
  3. Allow outbound HTTPS (port 443) in firewall.

Ports and Security

  1. Open required ports (21, 80, 4012, 5353, 8001, 8002, 8109, 8111).
  2. Apply MAC filtering and 802.1X authentication.
  3. Implement VLAN-based firewall rules.
  4. Plan penetration tests and security audits.

Final Verification

  1. Perform full system end-to-end test.
  2. Validate redundancy of Pro Servers.
  3. Confirm backup and recovery procedures.