DIVA Platform frequently asked questions.*
FAQs - General
Q: What is DIVA 5?
A: The new DIVA 5 solution decouples the DIVA Player from our DIVA Back Office video workflow. Now provided as a pure client-side SDK, DIVA 5 Player enables developers to integrate the video player with their chosen Online Video Platform (OVP) for video and stream management. Whilst moving to this more modern approach, we’ve also been delivering new SDKs for big screen devices, meaning users can enjoy DIVA’s great user engagement features on all major device types including TV’s going forward.
Read: Help center article - DIVA 5 Player
Q: What does DIVA 5 offer my business?
A: DIVA 5 means that clients can now adopt the DIVA player and its brilliant user engagement features across all devices without having to change their existing video workflow which is generally complex and time-consuming.
Q: Specifically, what features are supported on which devices?
A: We support an extensive range of features, covering the basics of video playback through to some of the most engaging user features available on the market today. Explore DIVA 5 features and the devices they’re available on.
Q: Can my in-house development team do all of the integration work?
A: They can certainly do most of the work. However, our development teams will still need to help you set up some of the more engaging features to ensure you can run your events smoothly with the best user experience.
Q: What benefits does DIVA 5 have against DIVA in the past?
A: We’ve listened to the market and our customers. DIVA 5 is now much more flexible to integrate with existing video workflows whilst also allowing you to have consistent experiences across all devices. It offers more flexibility in terms of integration efforts. If you have a large in-house development team, they can complete the majority of the integration work themselves, reducing the total cost of ownership.
Q: I’m an existing DIVA customer; what does DIVA 5 mean for me?
A: DIVA 5 enables you to launch DIVA on large screen devices and take advantage of future roadmap deliveries. Please talk to your project team about what’s involved with moving to DIVA 5 and adopting our new big-screen SDKs.
Q: Is there feature parity between DIVA 4 and DIVA 5?
A: Not yet. Initially, we’re focussing on our most used and key features and are developing additional features throughout 2022. If you are an existing DIVA customer, we're happy to talk you through this and our roadmap in detail so you can understand what this might mean for the features you are currently using. All supported features are detailed here in our help centre.
Q: Can I take big screen SDKs without upgrading my existing small screen players?
A: Yes, you can! We recommend doing an upgrade to your existing small screen players soon to take advantage of new product developments in the roadmap, but you can take big screen on DIVA 5 with your existing DIVA 4 small screen players.
Q: I’m not ready to migrate to DIVA 5 yet. Is this a problem?
A: Not immediately, we are continuing to provide critical support for our DIVA 4 player but all new feature releases going forward will be on DIVA 5 architecture.
Q: Where can I find out more information on DIVA?
A: You're in the right place! Our help center has lots of information to help you understand DIVA and DIVA 5 specifically; if you have further questions and are an existing client, please reach out to your project team. If you are not yet a client, we welcome you to our nearest office.
FAQs - DIVA Player
Q: How do I integrate DIVA with my entitlement logic?
A: As part of the DIVA Player integration, you will implement a VideoMetadataProvider component that connects the player to your video solution. This component oversees the return of a VideoMetadata structure, a description of the video that the DIVA Player should play, including valid video URLs, advertisements, etc.
In the event the VideoMetadataProvider returns an error, a customizable message displays for the end user. Your Entitlement logic can leverage this mechanism to ensure DIVA is either playing the video or displaying an error message. For technical documentation see our Video Meta Data article.
Depending on the use case, you can configure your Entitlement logic, removing the player and handling the Entitlement error in a completely custom way.
Visit: DIVA developer hub for technical documentation
Q: How can I geo-block content?
A: Geo-blocking content can only be done via entitlements and a CDN. Clients must adopt geo-block rules in their CDN or user entitlement integration. A player cannot provide an end-to-end out-of-the-box (OOTB) solution, this relates to production/distribution, and it comes down to how you tokenize streaming URLs before they reach the player (Entitlement + CDN (content distribution) Tokenization).
Q: How do I enable Alternate audio tracks?
A: To enable alternate audio tracks your video production needs to produce a video with multiple audio tracks in it. Those audio tracks are identifiable either by language or by name (the former in case you have multiple audio tracks for the same language).
For DIVA to be able to pick up and display multiple audio tracks, you must tell DIVA Player what the selection method is via the Settings audioSelectionMethod attribute. See our technical documentation on Settings and Video Meta Data article with specific reference to Audio tracks.
Next, the VideoMetadataProvider component needs to return a description of the tracks that should be made available to the user.
Read: Help centre article - Alternate audio tracks
Q: How do I enable Captioning?
A: Similarly to Alternate audio tracks, your video production needs to produce a video with multiple Closed Caption tracks. DIVA primarily supports VTTs that are embedded in the manifest. Those audio tracks can be identified either by language or name, and this is set up in the closedCaptionSelectionMethod attribute. For technical documentation, read our Settings article. For feature documentation, read our Subtitles and Captioning article.
Unlike Audio tracks, there is no need to feed additional information to DIVA through the VideoMetadataProvider. DIVA localizes the Closed Caption tracks on the UI (User Interface) based on the mechanism of the DIVA dictionary.
Q: How do I integrate my own Conviva account?
A: We provide a DIVA Conviva plugin that is pre-implemented on each platform. You can easily integrate it into your app together with DIVA.
Read: Developer documentation - Conviva plugin
Q: How can I integrate different video analyses like NPAW or MUX?
A: The DIVA Conviva plugin we distribute is based on a generic set of Media Analytic events which the integrator can use to develop its own plugin, similarly to how they are used by the Conviva plugin.
Read: Developer documentation - Media Analytics and Conviva
Q: How can I integrate client-side advertising?
A: DIVA supports Google IMA-based CSAI (Client-side Advertisement) out-of-the-box. The VideoMetadataProvider can pass in an ad URL through the VideoMetadataProvider. Such URL can point to a VAST or VMAP AD definition which is played automatically by DIVA Player using Google IMA.
Read: Developer documentation - Advertising
Q: How can I integrate server-side ad insertion?
A: DIVA supports Google SAI (SSAI) out-of-the-box for live streams. The integration is like CSAI, although different parameters are used.
Read: Developer documentation - Advertising
FAQs - DIVA Back Office
Q: How do I schedule a session?
A: manually schedule live sessions (events) from within DIVA Back Office’s Scheduler functionality, or via APIs. Channels in DIVA Back Office are linked with a video acquisition point via a configuration file (there is no Back Office UI layer for this). It's important to note that the DIVA Back Office Scheduler functionality is only relevant for clients using the DIVA end-to-end solution. Clients using their own OVP ingest video via APIs into the Video catalog.
Read: Help centre articles:
Q: How do I copy and paste sessions?
A: To save time duplicating sessions, to move a session from one channel to another, or in the event of an error, use DIVA’s Back Office Scheduler to easily copy and paste sessions. To follow detailed steps on copy and pasting sessions, check out our video catalog article.
Q: How do I ingest videos?
A: Live and video-on-demand (VOD) assets can be ingested into DIVA Back Office in a number of ways; as APIs, using Forge, or manually via the Video catalog. Read our video catalog article for further information.
Q: How do I add editorial data?
A: Editorial data is used to enhance the video stream, e.g., commentary, chapters, advertisements, subclips. For steps on how to add editorial data to video assets within DIVA Back Office, see our video catalog article.
Q: How do I synchronize a video with sports data?
A: Syncing a video with sports data is typically an automatic process using the Back Office time code, which links the video time code with the data provider events feed. Operators can manually override synchronized data time codes. For more information, check out our video catalog help centre article.
Q: How do I transition content from live to VOD?
A: there are two ways to transition live events into VOD.
Manually stopping the event or waiting until the event ends (transitions automatically relating to project workflows). Find out more in our video scheduler help centre article.
Q: How do I enable/disable data overlays?
A: DIVA Player configuration supports the ability to enable/disable data overlays. If DIVA Back Office has the information that populates the data overlays, this is sent to DIVA Player via APIs. Speak to the Deltatre Project team for more information.
Q: How do I add an OPTA ID to an event?
A: You can add an OPTA ID to an event when you create a timeline through DIVA Back Office’s Timeline catalog. The OPTA ID is inserted as Timeline ID. The Timeline ID is then linked to a data provider.
Q: How do I create a subclip?
A: subclips, live, and VOD are all video assets in DIVA Back Office. Find out more about creating subclips in our video catalog help centre article.
Q: How do ingested videos and event data reach end users’ screens?
A: DIVA Back Office contains an XML file with information on how DIVA Player should stream a video. DIVA Back Office sends data synchronization information to the Player via the Push Engine while the video is playing. DIVA Player presents an interactive, enriched, and synchronized video and data experience for end users.