Category Archives: Documentation

  • -

nanoStream and Google Chrome

Note: this Information covers the Transition Phase for Chrome 44 to 45. With the availability of nanoStream 4, all newer Chrome Browsers are supported by nanoStream.


In Chrome version 42 introduced in April, 2015, Google changed the default setting for NPAPI plugins like nanoStream from “enabled” to “disabled”. You can re-enable NPAPI support by changing the Chrome Flag for up to Chrome 44.
This setting will be has been removed from Chrome 45 in September 2015, when all NPAPI plugin support from Chrome will be discontinued.

nanoStream Product Options for Web Browsers

All nanocosmos customers will be able to proceed using our nanoStream technology in desktop browser environments. We will
keep providing solutions and updates to our web based live video encoder software along with new browser technologies.

See our separate page for further information about browser plugin, NPAPI, Chrome Extension and WebRTC based live encoding.

Background info about NPAPI Plugins

The NPAPI technology is based on native C/C++ code which enables system-level functions in custom plugins within browser environments. Google considers this a security risk, as it is not “sandboxed” as other technologies. Until now, NPAPI is the only plugin technology available on all browsers and desktop platforms (except Internet Explorer, which is using Active-X).

  • -

New Meta Data Add-on for nanoStream

nanoStream Live Encoding Software Platforms now supporting meta data transport injection

Our nanoStream SDKs, Apps and browser plugins now can be extended for sending any kind of meta data information to streaming server backends and players.
Based on a simple JSON API, any kind of object can be embedded into live streams.
Examples are: sending cue points, custom events, ad inserts, any kind of meta data.
Available in nanoStream Version 3.6 on Windows, MacOS, Desktop and Browsers and Mobile Devices (iOS/Android).

Contact us to find out more and get a quote.

Example usage to inject RTMP meta data

  • Sending a RTMP Cue Point

    // { name: cuepoint, time: 0.5 }
    data = ' "name": "name1", "time": "0.5", "type": "type1", "parameters": { "p1": "v1", "p2": "v2" }';
    nanoStream.SendMetadata("onCuePoint", data, "", 0);

    • -

    nanoStream Web Encoder Samples

    Check out the latest nanoStream Web Encoder samples, running on your Windows or MacOS browsers.

    Watch out for more samples soon!



    • -

    New nanocosmos / nanoStream Documentation Area

    Please checkout our new documentation and FAQ area on our website!

    Please click here to proceed.

    • -

    How To Use Tunneling for Firewall Protected Streaming Setups

    nanoStream3 supports RTMPT, the tunneling protocol of RTMP,
    including automatic Proxy detection.

    The URL should then be similar to this:


    The port should probably be 80, dependent on the corporate firewall and streaming server setup.

    Please note that RTMPT Tunneling is a workaround
    using the firewall-accepted HTTP protocol.
    This requires a protocol overhead, so plain RTMP is preferred.

    For using Firewalls, it might work to stream plain RTMP over port 80, like this:


    If this fails, use RTMPT.