StreamValidator usage Q & A

This document presents some common problems and solutions using StreamValidator.

StreamValidator can't work

Check your internet, if it still not work, maybe the StreamValidator is being updated, wait some minutes and clean the cache of your browser, and then you can use it.

StreamValidator crash and the web page reports “Run out of the memory”

The Web based StreamValidator has memory limitation, based on WebAssembly filesystem, we use JS heap to store all files, the limitation of browser JS heap is window.performance.memory.jsHeapSizeLimit (over 21 GB in my tester computer)

• 1. We use it to store the segment you want to download and the demuxed ES we want to save.
• 2. Besides we use it to store one segment of each thread. (EXP. 5 Representations * 5MB (one media segment in the Representation))

So we should focus on the limitation and don't use SV to parse too complex stream.

StreamValidator use the cache of your browser to do the validation, if your stream is really complex or contain too much data, you can use the select stream button to validate your stream.

StreamValidator reports fail to fetch the manifest

Firstly, check whether your input URL is wrong.

Secondly, if you access to StreamValidator via HTTPS and the content you input is a HTTP content, then you can find a secure invalid button in the URL line in your browser, click it and choose "Load unsafe scripts".

Thirdly, click "F12" and check the console line in your browser, if it reports "CORS" policy issue that it cross the domain, then, we suggest you install an extension app "Cross Domain - CORS" in your chrome browser.

Or add a CORS policy to the server bucket that the content is being pulled from, such as:

[

    {

        "AllowedHeaders": [

            "*"

        ],

        "AllowedMethods": [

            "GET",

            "HEAD",

        ],

        "AllowedOrigins": [

            "*"

        ],

        "ExposeHeaders": [

            "x-amz-server-side-encryption",

            "x-amz-request-id",

            "x-amz-id-2"

        ],

        "MaxAgeSeconds": 3000

    }

]

If it reports "CORS" policy issue that "The request client is not a secure context and the resource is in more-private address space `private`", you can set your chrome accept the private request:

DASH-IF validation doesn't work or reports fail to access to the content

Currently, our DASH-IF server only can access to public content, if the content is on your private server, try to use upload button to validate your content. When you use upload button, the DASH-IF server won't support to do the additional "segment validation".

If you access to StreamValidator via HTTPS, then, you should set your browser "allow insecure content" and then use the DASH-IF validation, such as in chrome: