Solutions for eSports

Solutions for esports, high quality and robustness

  • Dedicated hardware for highest possible robustness and quality
  • Multiple destinations from one encoder
  • Multiple encoders per unit
  • Redundant streaming
  • Adaptive bitrate
  • BIFROST™, network bonding, ARQ and error correction
  • Intinor performance level 6 = x264 preset “SLOW”
  • RTMP-input on Direkt Router for “Broadcast takers”
  • Distribution delay

A key feature of the Intinor product ranges for esports is the ability to have multiple software encoders, an encoder doing High (!) quality low bitrate (6mbps) multiple RTMP-streaming to Twitch, Facebook and/or Youtube, while other encoders are simultaneously sending broadcast quality streams to takers. With a cellular bonding backpack encoders for interviews and remote production, we offer a solution for every event. Read more in product catalogue

ESL’s Global head of streaming, Steven “Claw” Jalicy, said“We wanted a solution that could dynamically scale and deliver high quality and high reliability without generating out of control service costs and technology bottlenecks. Furthermore, we wanted the future capacity and potential to merge our online and linear workflows into a single ecosystem” “The Intinor equipment is cheaper then any of its competitors but it’s also the highest quality I have seen.” Don’t miss this blog post where Steven talks more about the “Basics of esports broadcast”. 

Michael Valentine, Global Head of Broadcast Technology at GFINITY,

“Using Intinor has allowed us to deliver shows to all of our online platforms, as well as traditional linear television channels with no stress at all. The all IP signal flow means we don’t have to worry about converting or standards, and the Direkt link encoder gives us full confidence in picture quality.

Having the ability to simply place a Direkt Link or Direkt Receiver in any location and send a high quality IP video feed means we no longer have to worry about point-to-point streaming in any capacity. This allows us to utilise our own infrastructure if producing an event on a remote location and we know it’s going to work.”

Twitch – “Best practice recommended”

  • 2 – 36 IP inputs
  • Netvideo inputs (HLS-pull & RTMP-in, NDI inputs )
  • Up to 16x SDI outputs / NDI-outputs
  • Multiple RTMP destinations
  • Destination delay 
  • TCP & SRT-pull
  • Transcoding
  • Logo & GFX overlays
  • IP stream forwarding with SRT, RIST, Bifrost and more
  • Scheduling and automation via API
Scroll to Top