A VOS.io live event is the process of ingesting live video feeds through an RTMP protocol or SRT protocol, then direct pass-through or transcoding it, and finally streaming the live video content to end users or consumers. We support 24/7 live streaming and along with recorded content that will be available after live as VOD content.

 

VOS.io enables you to create Live Events. It is important to understand the life cycle of a Live Event to master the operation.

Live Event States: 

Live Event Operations: 

 

 

VOS.io delivers video, audio, and text in various protocols. When you publish your live stream by using MPEG-DASH or HLS/CMAF, then along with video and audio, the service delivers the transcribed text in IMSC1.1-compatible TTML.

In VOS.io, a streaming endpoint represents a dynamic (just-in-time) packaging and origin service that can deliver your live and on-demand content directly to a client player app by using one of the common streaming media protocols (HLS or DASH). In addition, the streaming endpoint provides dynamic (just-in-time) encryption to industry-leading DRM systems.

Yes, by leveraging VOS.io’s built-in origin server and dynamic packaging and encryption capabilities, we support the delivery from your existing assets in your Azure Blob storage accounts in HLS, Smooth Streaming and MPEG DASH streaming protocol formats. That means no more extra processing and quicker turnaround.

The egress limit of one streaming unit is 200 Mbps.

Then the total streaming units needed = Average bandwidth x Number of viewers x Percentage of traffic not handled by the CDN / 200 Mbps. You can set the streaming units per your view of your traffic demand.

In case of some unpredictable traffic peak/burst which causes exceeding the max capacity of the preset streaming units, VOS.io supports auto-scaling the streaming units for you.

The following file formats are supported:

• MXFop1a: AVCI, AVC LGop, Mpeg2 LGOP, XDCAM50 (MPEG2 Long-GOP + PCM), DVCPro100.
• MXF file playback supports DolbyE audio tracks. The DolbyE will be decoded.
• MP4: H.264, audio supports AAC.
• MTS: Mpeg2, H.264, audio can be Mpeg2L1 or AAC or AC3.
• MOV: XDCAMHD, DV25, DVCPRO50/100, with PCM & DolbyE audio tracks.

We don't recommend it. Very short content that's less than a minute or two in duration is not ideal for adaptive bitrate streaming. If you intend to stream very short-form files, we recommend that you pre-encode the content into a format that's easily streamed using a single bitrate. Because most adaptive bitrate players need time to buffer multiple segments of video, as well as time to analyze the network bandwidth before "shifting" up or down the adaptive bitrate ladder, it's often useless to provide a lot of bitrates for content that's under 30 seconds long. By the time the player locks its heuristic algorithm on the right bitrate to play based on network conditions, the file will be done streaming. In addition, some players default to buffering up to three segments of video. Each segment can be two to six seconds long. For very short-format videos, the player is likely to buffer and begin playback of the first selected bitrate of the adaptive bitrate set. For this reason, we recommend using a single-bitrate MP4 file, and uploading it to an asset if you need HLS or DASH manifest generation. For details on how to achieve this, see the answer to the question "Can I stream existing MP4 files that are pre-encoded or encoded in another solution?" in the section about packaging and delivery.

Dynamic encryption is securing your media from the time it leaves your computer all the way through storage, processing, and delivery. With VOS.io, you can deliver your live and on-demand content encrypted dynamically with Advanced Encryption Standard (AES-128) or any of the three major DRM systems: Microsoft PlayReady, Google Widevine, and Apple FairPlay. More information is coming soon...

Customers often wonder whether they should use AES encryption or a DRM system. The main difference between the two systems is that with AES encryption, the content key is transmitted to the client over TLS. The key is encrypted in transit without any additional encryption ("in the clear"). As a result, the key that's used to decrypt the content is accessible to the client player and can be viewed in a network trace on the client in plain text. AES-128 clear key encryption is suitable for use cases where the viewer is a trusted party (for example, encrypting corporate videos distributed within a company to be viewed by employees).

DRM systems like PlayReady, Widevine, and FairPlay provide an additional level of encryption on the key that's used to decrypt the content, compared to an AES-128 clear key. The content key is encrypted to a key protected by the DRM runtime in addition to any transport-level encryption that TLS provides. Decryption is handled in a secure environment at the operating system level, where it's more difficult for a malicious user to attack. We recommend DRM for use cases where the viewer might not be a trusted party and you need the highest level of security.

Yes, we support using Azure AD as a Secure Token Service provider to issue tokens as part of our content protection working chain. If you don’t have any specific token provider, no worries, VOS.io also provides embedded STS service that can help to ease your work.