Yes, VIPE is software only and runs on COTS hardware either in the public or private cloud.

Yes, VIPE supports HLS streams and manifest files containing metadata for downstream processing.

Yes you can. There is no 1:1 relation between number of channels and number of servers or instances.

No, VIPE is fully cloud native. It was architected from the ground up to operate in a virtual environment but this can just as easily be in your private cloud on premises.

Yes, you can, VIPE solo is perfect for this. It doesn’t scale but is an efficient Channel In A Box (CIAB) solution. Please contact our sales team for advice.

Multiple channels can run on a single server/instance, the balance between channel definition of and compute power the determine how many channels can be virtualised.

Yes, simulcast is just another stream that can be published from the same playlist in parallel.

Yes, VIPE scales tremendously well. From the start, it has been architected to behave exactly like this.

Yes, BCNexxt does not supply any hardware. Of course, we can help to select the hardware that fits your requirements the best.

Yes, VIPE is using floating licenses which can be moved at any time.

Yes, source content is not copied from its original location and the rendered content is encrypted.

VIPE accepts the usual professional codecs. A full list is available via our datasheet, please contact our sales team for assistance.

Yes, by nature VIPE is very suitable for this. VIPE’s playout engines operate independently from all other engines (except for VIPE solo) and they pull content from a central storage location, also when the playout is operated in a remote headend.

Virtually unlimited. Since VIPE is a pre-render solution, the render speed may vary depending on the amount of graphics that need to be rendered at a specific time.

No, rendered content is encrypted for security reasons but commercial solutions always include decryption software.

Yes, as soon as a few frames have been rendered, playout can already start. Since the render engine is faster than real-time, the system will gain on the schedule.

Yes, there are different ways to achieve this. Our projects team will advise what is the best approach for your requirement.

Before rendering, trusted content is checked on availability, compatibility and corruption.

After rendering, the enriched files are checked on black/freeze/audio.

An embedded rich media player allows for visual control of the content, including all audio and subtitle tracks. This visual control is not mandatory.

The outcome of all QC processes are presented in the central rundown and monitor view through icons and colours so a single person can overview multiple channels with a breeze.

VIPE accepts schedules from all major traffic vendors.

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. Our projects team will advise and assist where needed.

Yes, by applying business rules in combination with HTML5 scaling effects any scaling requirement can be met. Our projects team will advise and assist where needed.

Yes, VIPE allow a single workflow to produce multiple streams in parallel. Streams can vary in bitrate, resolution, audio/subtitle mapping or PID configuration.

Yes, before rendering, trusted content is checked on availability, compatibility and corruption.

Note that “Quality control” explains more content checking processes.

Yes, user management allows for controlled access to parts of the system and selections of the channels and/or destinations.

Yes, you can. Our professional support team is always available.
OPEX offerings have 24/7 support included.
APEX offerings come with a separate line item and are therefore optional.

Updates can be installed remotely by the VIPE professional support team.

Since VIPE is accessed through a web browsers, the users only have to refresh their browser session to gain new functionality.

For more complex updates there is a traditional main/backup scenario for controlled deployment.

Different storage types of the trusted content are supported.

In AWS, S3 is typically used. In the private cloud a NAS is common.

Our projects team will advise on the possibilities based on your requirements and existing infrastructure.

VIPE will typically store the rendered files, that are ready to be published, on to a NFS server.

Yes, contact our sales team for details.

Our professional projects team will advise how much compute power is needed for your requirements. Also, when expanding an existing installation.

Besides the normal asrun export files, VIPE offers comprehensive monitoring of the complete system health status as well as error messaging of all individual publishing streams.

Integration with 3^rd party tools is supported through our API.

No, a VIPE main playout channel always comes with a backup channel at no additional cost.