Contact support

Channels: detailed analysis errors

Overview

This document describes the detailed error messages included in 500 Server Errors returned by the analyzer. It covers general errors, stream format errors, and HLS or DASH-specific errors.

Analysis error formats

General errors

General errors appear as strings inside the data array field.

{
    "type": "ERR_INVALID_MANIFEST",
    "code": 500,
    "message": "Manifest Invalid",
    "data": [
        "Request failed with status code 404"
    ],
    "name": "MoleculerError"
}

Stream format errors

Stream errors appear as objects in the data array.

The type field can be streamError for HLS or dashStreamError for DASH.

{
  "type": "ERR_INVALID_MANIFEST",
  "code": 500,
  "message": "Manifest Invalid",
  "data": [
    {
      "type": "streamError",
      "index": 0,
      "uri": "320x180/ch5223id88.m3u8",
      "errors": ["No bandwidth found", "No codecs found", "No resolution found"]
    }
  ],
  "name": "MoleculerError"
}
{
  "type": "ERR_INVALID_MANIFEST",
  "code": 500,
  "message": "Manifest Invalid",
  "data": [
    {
      "type": "streamError",
      "index": "",
      "uri": "",
      "errors": ["Submanifest uri missing"]
    }
  ],
  "name": "MoleculerError"
}

General errors

General errors are found directly as strings in the data array field. Examples include:

  • "Manifest file not found"
  • "Unknown manifest type. Must be one of HLS, DASH, MRSS"
  • "getaddrinfo ENOTFOUND": URL not found
  • "connect ECONNREFUSED 127.0.0.1:80": invalid value passed as the URL

HLS-specific errors

Examples of HLS-specific errors include:

  • "No bandwidth found"
  • "No codecs found"
  • "No segment duration found"
  • "Submanifest uri missing"
  • "HLS substreams can only be analyzed via the master stream. Please provide the master manifest url": the provided URL points to a substream instead of the master manifest
  • "Invalid Playlist: The EXTM3U tag MUST be the first line.": malformed substream
  • "expected 1 audio stream, found 2": multiple audio streams aren't supported for HLS

DASH-specific errors

Examples of DASH-specific errors include:

  • "Only DASH Live streams can be analyzed" 
  • "Can't find any dash stream information in manifest"
  • "Can't find stream information in manifest"
  • "No audioSamplingRate found"
  • "No bandwidth found in video stream <number>"
  • "No codecs found in video stream <number>"
  • "No resolution found in video stream <number>"
  • "No valid segment duration found in video stream <number>"