Ventuz: How was the decision-making process at Outernet to decide to use Ventuz?
Jad: We wanted predictability and reliability, and the kind of responsiveness that is usual on mission critical scenarios like broadcast. The decision to use Ventuz came after extensive research of the solutions available in the market. Some vendors even declined to create this kind of project due to the technical challenges while Ventuz did come forward, they were very open and keen on solving the technical challenges of this outstanding project.
Ventuz: What were the most important features in Ventuz that made you decide for our solution?
Jad: Outernet is a one-of-a-kind project. We had a vision and the [Ventuz] flexibility made it an easy choice, because it could adapt to all the different bits and content types that we needed for such a groundbreaking installation.
Ventuz: You are working with Ventuz 7 for quite a while now, how is the experience?
Jad: Mapping and handling all the different displays while keeping a limited number of systems was the main thing for us, the Cluster in a Box technology in Ventuz 7 allowed us to run the whole installation with a manageable amount of workstations, almost three times less than other solutions. We were excited about how easy it was to automate Ventuz playout and integrate it with our CMS/Scheduler, this allowed us to control the whole Outernet district, 5 ultra large screens, 26k and over 230 million pixels, and all controlled by just one operator.