Vipe is a cloud native, software-only solution that can be deployed in public and private clouds. It can be applied on site, through COTS hardware, or with a hybrid model across all three deployment options.
Your installation, tailored around your required workflow. No matter which type of deployment, Vipe is highly scalable, with multiple processing engines that act as one entity to scale up or down according to the actual workload.
With source files provided by a central location, Vipe uses intermediate storage that sits between the render and playout engines. This intermediate storage is shared across all the playout channels—separate networks for control, data and broadcast should be applied accordingly.
Vipe maintains a secure, RESTful web service which uses API-KEY for authorization. For your system health status, functional data, and available API calls, this means you can always contact us for the latest status.
Yes, Vipe can replace almost every playout application. Start by talking to our experienced professional services team who will help design the system architecture required to meet your needs.
Yes, from a single to an unlimited number, the quantity on a single server is dependent upon the complexity of the channel.
Vipe supports up to multiple live feeds per channel including graphics. Switching between them and other file-based events is seamless.
Yes, from a single to an unlimited number, the quantity on a single server is dependent upon the complexity of the channel.
Vipe is extremely scalable in both volume of content and types of publishing. Your only consideration is how you choose to host.
Yes, contact our sales team for details
No, a Vipe main playout channel always comes with a backup channel included
Yes, Vipe supports HLS streams and manifest files containing metadata for downstream processing
Vipe uses floating licenses that can be moved between installs without penalty, our PS team can determine the resources you require.
There is no fixed relationship between number of Linear, OTT or VOD channels and the servers needed, the application automatically scales to meet demand
Although Vipe is fully cloud native and architected to operate in a virtual environment, it can be just as easily hosted in your private cloud or on premises.
Yes, Vipe runs on COTS hardware either on-premises or in the public or private clouds.
Numerous storage types are supported - in AWS, S3 is typically used. In the private cloud a NAS is common. Our PS team will advise you based on your requirements and any existing infrastructure.
Yes, simulcast is just another stream that can be published from the same playlist in parallel
Vipe supports DVB, Teletext (OP47), SCTE27, CEA 608/708 and Invision subtitles
Yes, as soon as a few frames have been cached, playout can start and will gain on the schedule
Yes. There are different ways to do this, so our PS team will advise the best way for your workflows.
Yes, a single workflow can produce multiple streams of varying bitrate, resolution, audio/subtitle mapping or PID configuration in parallel.
Content is automatically checked for availability, compatibility and corruption and after assembly the files are checked for black / freeze / audio.
Issues are presented on an exception basis, so a single person can easily overview multiple channels, then an embedded rich media player allows for visual checking of the content, including all audio and subtitle tracks.
Vipe accepts schedules from all major traffic vendors.
Yes, events can be changed up to a few minutes before they are published.
Yes, user management allows for controlled access to parts of the system and selections of the channels and/or destinations.
Updates are managed centrally and there is a traditional backup scenario for controlled deployment.
Our PS team will advise how much compute power is required for your workflow.
Yes, the output stream is compressed and can be specified from the web GUI
Yes, Vipe is HTML5 based and supports all HTML5 effects.
Yes, by applying business rules in combination with HTML5 scaling effects any ARC requirement can be met.
Yes, by applying business rules with HTML5 scaling effects any requirement can be met.
Yes, source content is not copied from its original location and the rendered content is encrypted.
Vipe accepts most codecs. Please contact our sales team for a full list.
Yes, Vipes playout engines operate independently from all other engines and pull content from a central storage location.
It is virtually unlimited, the render speed may vary depending on the amount of graphics that need to be rendered at a specific time
Vipe offers comprehensive monitoring of the health of the complete system as well as individual publishing streams
Yes, the GUI enables changes, re-rendering and publishing of the on air event without a glitch.
Yes, Vipe has a unique way of linking parent/child playout channels in an efficient way.
Yes, any Vipe output can be delayed.
