Neurocast

Content-agnostic, modular and customizable method of preparation, delivery and playback of multiple types of data on a single interface using several, interchangeable transport technologies working simultaneously, enabled via a sequence of fully modifiable components, integratable during any phase of content delivery.

There is a proliferation of standards and lack of interoperability in video streaming. For example, preparing and carrying out a live stream available on mobiles and desktops means multiple video and audio tracks which are designed as separate workflows with their own manifests, CDN requirements, supported DRMs and so on.

PolygonCast is a workflow focused on data streaming, inspired by database synchronization. Its core is ANY data projected on a temporal dimension and requested based on time by user interfaces. The transport layer is fully separate and modular, allowing for simultaneous independent content delivery and ad hoc customization.

PolygonCast is built with modularity in mind, meaning each component can be modified without affecting the others. The workflow can be dynamically modified, allows for use of multiple technologies simultaneously and is content-agnostic, allowing the delivery of any type of data to the viewer.

The PolygonCast Data Streaming Workflow can be deployed during any phase of content delivery, easily combined with your existing stack and used to deliver any type of content to a single interface using multiple transport technologies while being open to modification and adjustment according to your needs.

We provide the ability to stream and play back any type of content or contents simultaneously on a single player interface. This can be multiple videos playing side by side, an overlay of the latest Facebook updates over a live event stream or anything else or everything together. Said content can be delivered using HTTP, WebRTC, UDP, QUIC, Multi-CDNs and even P2P. All of these technologies can be used together, simultaneously and interchangeably to deliver the same data, whatever it may be.

With PolygonCast viewers get a truly interactive experience - they can view content-targeted news during playback, access additional monetized materials to supplement the core stream (e.g. backstage feed), select from multiple camera feeds to individualize their streams an so on. By combining multiple streams into a single player, PolygonCast allows you to easily support 360 segmented ABR video via e.g. streaming 9 separate video feeds with only the one in front of the viewer being in HD. Adding additional data streams to that gives you VR-readiness.

PolygonCast Platform aims to compartmentalize video delivery. It can integrate with your infrastructure at the very beginning and is capable of receiving raw video data, processing it via external encoders (like Elementals) and outputting it in a number of formats, available both for viewer consumption and/or further processing. Everything we do is packed in a neat dashboard which provides an intuitive GUI. You can select content to be streamed, customize quality and break down single multimedia items into multiple streams. We also provide a comprehensive statistical overview of each ongoing data stream.

The PolygonCast Platform is agnostic when it comes to ingestion formats. We support various input scenarios for both the metadata and the video itself. After the ingestion we may proceed to processing, transformation, propagation and delivery.

We use raw media files as baseline input and support both mp4 and webm containers. We handle both chunked and non-chunked muxed content. The next step would be using non-muxed content (when the industry is ready to provide it).

A machine friendly way to push video data via an HTTP REST API or any other low-level TCP/UDP scenario. This would probably be the default interface if you were to to interact with the platform through program code rather than user interface.

Both DASH and e.g. HLS manifests can act as an input source. We ingest the metainformation from the manifest and combine it with what we can extract from raw data. Many industry products use DASH or HLS manifests as supported forms of output.

We have optimized and prepared everything to additionally support the most notable live streaming workflows currently on the market. This means both IP based ones such as RTMP, UDP, RTSP, as well as transport stream based ones.

We use raw media files as baseline input and support both mp4 and webm containers. We handle both chunked and non-chunked muxed content. The next step would be using non-muxed content (when the industry is ready to provide it).

A machine friendly way to push video data via an HTTP REST API or any other low-level TCP/UDP scenario. This would probably be the default interface if you were to to interact with the platform through program code rather than user interface.

Both DASH and e.g. HLS manifests can act as an input source. We ingest the metainformation from the manifest and combine it with what we can extract from raw data. Many industry products use DASH or HLS manifests as supported forms of output.

We have optimized and prepared everything to additionally support the most notable live streaming workflows currently on the market. This means both IP based ones such as RTMP, UDP, RTSP, as well as transport stream based ones.

Within the platform, you can process, edit and remix your data to achieve the desired result. Every transformation step is an optional "filter" that you apply to your content to get the best "picture". And in the end you schedule everything for distribution.

Propagation to edge servers is important for every workflow. You can opt-in to distribute content with multiple CDNs simultaneously. We've successfully tested automatic propagation with CloudFront, AWS S3 and CDN77.com. Custom workflows are also supported.

Since we support multiple transport technologies, we also support propagation to a streaming server that may go beyond HTTP. E.g., in the demo above, a UDP (WebRTC based) streaming server receives content via an API and makes it ready for streaming.

One of the key features of the PolygonCast Streaming Platform is the ability to encode both live and VOD video content as needed by integrating with and using one of the industry standard encoders like Wowza, Elemental or Elastic Encoder.

In addition to usual video encoding, we have prepared everything to support custom encoding workflows. Like using cloud based encoders (such as bitcoding.com) or a custom built distributed encoder that utilizes ffmpeg.

Propagation to edge servers is important for every workflow. You can opt-in to distribute content with multiple CDNs simultaneously. We've successfully tested automatic propagation with CloudFront, AWS S3 and CDN77.com. Custom workflows are also supported.

Since we support multiple transport technologies, we also support propagation to a streaming server that may go beyond HTTP. E.g., in the demo above, a UDP (WebRTC based) streaming server receives content via an API and makes it ready for streaming.

One of the key features of the PolygonCast Streaming Platform is the ability to encode both live and VOD video content as needed by integrating with and using one of the industry standard encoders like Wowza, Elemental or Elastic Encoder.

In addition to usual video encoding, we have prepared everything to support custom encoding workflows. Like using cloud based encoders (such as bitcoding.com) or a custom built distributed encoder that utilizes ffmpeg.

Our FlexManifest allows you to combine various contents into a single stream. This allows you to combine multiple cameras from a live concert, merge it with a UGC like Periscope stream, add a 360º video and the viewer would be able to seamlessly switch between them or view them side-by-side.

FlexManifest is a data streaming manifest, which is a very important distinction to make. With FlexManifest there is an option to effortlessly add data buckets to video buckets. And without any additional effort clients will be able to access that data the same way they get the video data with live playback.

Sometimes external processing (like adding DRM) is required. Adding 3rd party services like a DRM-vendor, automatic content quality control systems, p2p etc., is our core approach. Our data streams can be customized to both ingest and output specified times of data anywhere, anytime.

Any custom transformation can be configured or applied on request. Even if your requests go beyond the above given frame of reference, with data streaming we will be able to easily accommodate most requests. Segmented 360 selective ABR video, to give an example. Everything’s possible.

Our FlexManifest allows you to combine various contents into a single stream. This allows you to combine multiple cameras from a live concert, merge it with a UGC like Periscope stream, add a 360º video and the viewer would be able to seamlessly switch between them or view them side-by-side.

FlexManifest is a data streaming manifest, which is a very important distinction to make. With FlexManifest there is an option to effortlessly add data buckets to video buckets. And without any additional effort clients will be able to access that data the same way they get the video data with live playback.

Sometimes external processing (like adding DRM) is required. Adding 3rd party services like a DRM-vendor, automatic content quality control systems, p2p etc., is our core approach. Our data streams can be customized to both ingest and output specified times of data anywhere, anytime.

Any custom transformation can be configured or applied on request. Even if your requests go beyond the above given frame of reference, with data streaming we will be able to easily accommodate most requests. Segmented 360 selective ABR video, to give an example. Everything’s possible.

Apart from CDN propagation there is also a manifest output format. Right now, MPEG-DASH and HLS are the default output standards. We propose our own Flex Manifest format. It is a machine-api-player-friendly format for universal data streaming. It maps data on a temporal dimension a bit like MPEG-DASH or HLS. And we've designed it in way that would e.g., enable adding other dimensions (like altitude and longitude) for VR experience data streaming connected to real and virtual locations.

A schemaless, flexible and interactive way of describing media content. It is a technological foundation for building innovative streaming applications.

Both DASH and HLS outputs are supported. They can be propagated to various CDNs alongside the content.

Some workflows may require other custom output formats and we are ready to provide them as needed.

A schemaless, flexible and interactive way of describing media content. It is a technological foundation for building innovative streaming applications.

Both DASH and HLS outputs are supported. They can be propagated to various CDNs alongside the content.

Some workflows may require other custom output formats and we are ready to provide them as needed.

The client consists of several sub-entities called Projectors within a DataPlayer, which can be dynamically created to display a given bucket (type, format, element) of data. This means that in one window several contents can be displayed hand-in-hand, not being limited by type (e.g. text on video or video in video). The data for each bucket is provided by a Universal Download Manager that utilizes/mixes available transport technologies, handles network ABR and is generally responsible for delivering data to every projector before the deadline.

In addition to our own protocl protocol, we have developed a reference data streaming client that utilizes Multi Transport and Multi CDN technology that works automatically with anything. It works great with video, but it will work just same with any media content or arbitrary data. Hence, any type of streaming data can utilize that power. Including adaptive quality change for scenarios from various thumbnail resolution to advanced features like adaptive viewports.

The PolygonCast Client allows for simultaneous delivery of content via multiple transport technologies. The include HTTP, WebRTC, UDP, QUIC and even P2P. We also support streaming from multiple CDNs, as pioneered by MPEG-DASH. Methods of content delivery can be dynamically adjusted mid-stream.

The DataPlayer (playback interface of the PolygonCast Client) takes a modular approach to streaming. Each video stream is displayed via a projector, which can then be either displayed exclusively within the DataPlayer or coupled with additional video feeds. This can easily support e.g. multiple cameras during a live event.

The projectors are not only capable of playing back video, but also any other type of media. Each type of content being streamed can get its own projector and can then be freely coupled with other projectors within the DataPlayer. This shines for multiple audio tracks with e.g. multilingual events or additional stream with sign language.

PolygonCast does not stop at delivering media content. With data streaming you are free to mix and match content as you please and deliver it easily to your viewers. It’s possible to provide live playback of e.g. twitter feeds or mid-stream targeted, fully interactive advertising. Any type of data can be deliver and played back to your viewers.

The PolygonCast Client allows for simultaneous delivery of content via multiple transport technologies. The include HTTP, WebRTC, UDP, QUIC and even P2P. We also support streaming from multiple CDNs, as pioneered by MPEG-DASH. Methods of content delivery can be dynamically adjusted mid-stream.

The DataPlayer (playback interface of the PolygonCast Client) takes a modular approach to streaming. Each video stream is displayed via a projector, which can then be either displayed exclusively within the DataPlayer or coupled with additional video feeds. This can easily support e.g. multiple cameras during a live event.

The projectors are not only capable of playing back video, but also any other type of media. Each type of content being streamed can get its own projector and can then be freely coupled with other projectors within the DataPlayer. This shines for multiple audio tracks with e.g. multilingual events or additional stream with sign language.

PolygonCast does not stop at delivering media content. With data streaming you are free to mix and match content as you please and deliver it easily to your viewers. It’s possible to provide live playback of e.g. twitter feeds or mid-stream targeted, fully interactive advertising. Any type of data can be deliver and played back to your viewers.

By revamping the traditional playback approach, we allow for easy streaming of multiple video (or any other content) streams to a single playback interface. This means not only easy 360 video, but also augmenting said video with additional feeds, like geo-located newsfeed, photos or even interfaces for interaction with the outside world. Should a proper type of interface be involved, we can even deliver sensory data like haptic feedback alongside multimedia content.

PolygonCast can send and play back any type of content to the end-user. This means text data like a newsfeed enriching streams from live events, video content like periscope videos dynamically inserted into said stream alongside the original feed and so on. Everything that up until now had to be done via editing tricks, can now be combined together into a single, coherent data feed that can be displayed to the end-user live and dynamically adjusted.

Learn more

Contact us