An online video platform (OVP), provided by a video hosting service, makes it possible for users to publish, convert, store and play back video content on the Internet, frequently through a structured, massive system that might create revenue. Users typically will submit video material through the hosting service's site, mobile or desktop application, or other user interface (API). The kind of video material published might be anything from shorts to full-length TV shows and motion pictures. The video host stores the video on its server and uses users the ability to allow different kinds of embed codes or links that allow others to view the video material. The site, generally utilized as the video hosting site, is generally called the video sharing site.
Online video platforms can utilize a software application as a service (SaaS) business model, a do it yourself (Do It Yourself) model or user-generated content (UGC) model. The OVP comes with an end-to-end tool set to upload, encode, manage, playback, style, deliver, distribute, download, publish and measure quality of service or audience engagement quality of experience of online video content for both video as needed and live delivery. This is typically manifested as a User Interface with log-in qualifications. OVPs also consist of supplying a customized video gamer or a third-party video gamer that can be embedded in a website. Modern online video platforms are typically paired up with ingrained online video analytics supplying video publishers with in-depth insights into video efficiency: the overall number of video views, impressions, and distinct views; video watch time, statistics on user location, gos to, and behavior on the website. Video heat maps reveal how user engagement rate changes through the viewing procedure in order to determine audience interaction and to create compelling video content. OVPs relate to the over-the-top material video market, although there are numerous OVP suppliers that are also present in broadcast markets, serving video as needed set-top boxes.
OVP item models differ in scale and feature-set, varying from ready-made web websites that individuals can use, to white label models that can be personalized video promotion by enterprise clients or media/content aggregators and incorporated with their standard broadcast workflows. The former example is YouTube. The latter example is predominantly found in FTA (Free-To-Air) or pay-TV broadcasters who look for to provide an OTT service that extends the availability of their content on desktops or several movement devices.
In general, the visual user interface accessed by users of the OVP is offered as a service. Profits is obtained from regular monthly subscriptions based on the number of users it is certified to and the intricacy of the workflow. Some workflows need file encryption of material with DRM and this increases the cost of using the service. Videos might be transcoded from their initial source format or resolution to a mezzanine format (suitable for management and mass-delivery), either on-site or using cloud computing. The latter would be where platform as a service, is offered as an additional expense.
It is possible, however uncommon, for big broadcasters to establish their own proprietary OVP. However, this can require complex development and maintenance costs and diverts attention to 'structure' rather than distributing/curating material.
OVPs typically cooperate with specialized third-party company, utilizing what they call an application shows user interface (API). These consist of cloud transcoders, suggestion engines, online search engine, metadata libraries and analytics suppliers.
Video and content delivery protocols
The vast bulk of OVPs utilize industry-standard HTTP streaming or HTTP progressive download protocols. With HTTP streaming, the de facto standard is to use adaptive streaming where multiple files of a video are created at different bit rates, however just one of these is sent to the end-user during playback, depending upon readily available bandwidth or gadget CPU restraints. This can be switched dynamically and near-seamlessly at any time during the video watching. The primary protocols for adaptive HTTP streaming include Smooth Streaming (by Microsoft), HTTP Live Streaming (HLS) (by Apple) and Flash Video (by Adobe). Flash is still in usage however is declining due to the appeal of HLS and Smooth Stream in mobile phones and desktops, respectively. [citation needed] Each is a proprietary procedure in its own right and due to this fragmentation, there have actually been efforts to create one standardized procedure understood as MPEG-DASH.
There are numerous OVPs available on the Web.