Home > Live Streaming > Miscellaneous > Troubleshooting - Publisher Side

Troubleshooting - Publisher Side



There are 4 major areas which have plenty of failure potential:

Capture Devices
Most publishers have a fantastic setup of production equipment – the “Capture Devices”. This is the area with the least amount of failure potential among experienced production houses and broadcasters.


Encoder
There are typically 3 types of encoders: Lightcast Encoders, Third-Party Hardware Encoders, Self-Built Encoders.

  • Lightcast Encoders: Publishers who use a Lightcast Encoder have 0 liability in this area and an extremely low risk of failure in this area.

  • Third-Party Hardware Encoders: Publishers who invested into a professionally built and configured third-party hardware encoder have a very low risk of failure in this area, once the encoder has been configured correctly.

  • Self-Built Encoders (often the cheapest entry-level solution): Publishers using a software encoder on a PC or Mac (a self-built encoder setup) are affected the strongest in this area and bound to trouble-shoot their encoders on a regular basis. Even small, unnoticed software changes (in the operating system, drivers, software updates, software for other use of the computer, etc…), can have an immediate effect on the performance of the software encoder, or the input and output hardware connection. If you look at using your own self-built encoder, please have the needed know-how employed on staff, available at all times and hired to build, maintain and trouble-shoot your self-built encoder setup.


Local Network
This area often bears underestimated risks with plenty of failure potential. It starts with the connection: how is your encoder connected? Via cable or via WiFi? What is the setup of your LAN (computer) network? Your network may include: switches, hubs, routers, cables, plugs, wall-sockets. Have a professional system administrator setup, maintain and check on your local computer network.


Internet Service Provider
Often a very frustrating area of failure potential, as it is beyond anyone’s control and ISPs are often unreachable, or customer support unable to help, or unknowledgeable in regards to live-streaming requirements. In most cases anyone reachable at an ISP is entire unaware of possible connection problems within their network. As the signal of your live-stream leaves your building, it can travel to the CDN’s access point (the CDN’s POP location where you decided to ingest your live-stream into the CDN) through different routes. Along the route of the signal there are different hubs and proxy servers with potential bottle-necks and connection problems. Your ISP most likely does not own the cable networks along the entire way, but usually has to pass the signal along to third-party cable networks. There are usually several hubs along the way which can hold up the flow of the signal. Pulling a trace-route shows you all hubs along the way and the delay times of each hub. It will allow you to detect the bottle-necks where the signal is being slowed down too much in order to ensure good streaming performance. You should send the trace-route data to the highest possible level of tech-support you can get a hold of at your Internet Service Provider and put enough pressure on them, to be willing to work on eliminating the delays of the signal flow.


Check out Troubleshooting - CDN Side or Troubleshooting - User Side.