Integration Into Your App & Platform
NW EXP integration can be structured across multiple domains (see image below) and utilized for various event types.
NW EXP offers a standardized functionality package, encompassing playback of multiple video and audio feeds, instant replays, and more, readily available.
Additionally, for different event types, pre-built experiences are accessible. These experiences integrate with data providers to enrich the event with additional information, such as match statistics, athlete details, and more. Once a data provider is fully integrated, this experience is available across all events supported by that provider.
Hence, the bulk of the integration occurs only once and can be applied to multiple experiences, including various sporting events. Merely connecting the content input feeds and setting up the event within the NW system prepares everything for smooth execution.
Imagine you're aiming to employ NW EXP for a particular event like football "soccer". Your goal is to offer the viewers a multiview experience with integrated event data for a hundred events being broadcasted.
NW organize the setup process into two core areas: defining the content flow and setting up the desired user experience.
[Part of Content Distribution]
For the content flow, different options can be chosen depending on the event production.
Events are sometimes traditionally produced on-site using an OB truck, while at other times, production occurs remotely, with individual camera feeds sent to a central production center or cloud environment.
NativeWaves can facilitate the complete end-to-end content flow in all these use case through the Content Service. In addition, it can also seamlessly work with existing streaming partners.
For example, an OB truck setup can easily be supported by using a NW AVCoder which is a hardware encoder/decoder device, that is used at the event site and connected to the input feeds via SDI. The AVCoder only needs an internet connection, can be remotely managed via the NativeWaves Console, transcodes the feeds and pushes them to the cloud. One or multiple AVCoders can be used and there is no limit in number of feeds as long as enough upload bandwidth is available (see section below).
In remote production setups where all audio/video feeds from the event are available as digital feeds (SRT, RTMP, etc.), they can be directly sent to the NW Content Service. Subsequently, these feeds will be transcoded in the cloud to a distribution format like HLS.
If all necessary feeds are already available in a final distribution format, e.g. as HLS stream, they can also be integrated into the NW EXP system.
This content flow setup is usually defined once for one or multiple event series, and once it's setup it can be easily reused across many events.
For more details on content streaming, especially low-latency content streaming, please explore our dedicated section on Low Latency Content Streaming.
[Part of App, UX, Platform]
NW EXP offers a default experience along with pre-built user experiences wich integrate various data providers tailored for diverse event types. These experiences are adaptable and can be customized to align with the theme of the application they are integrated in.
If an experience is unavailable for a specific event type or data provider, it can be newly designed and created by NativeWaves. We structure this process in the following steps:
- The data provider(s) for the specific event types that should be supported, need to be identified.
- NativeWaves receives the data provider's API documentation and/or direct access to the data for the relevant event types (direct access to the data speeds up the overall process)
- NativeWaves creates a first UX mockup with basic features that can be shared and discussed (takes usually 1-2 weeks)
- After the first UX draft is defined, the implementation takes 2-4 weeks and is then ready to be used.
In summary, creating a new experience with a fresh data provider typically takes around one month. For more intricate designs involving nested menus and advanced features like specialized graphs (e.g., heatmap for new sports), the estimate generally spans between 2 to 3 months.
The integration and development phases can progress in parallel and gradually. For instance, a multi-view experience with instant replays is readily accessible for a new sport type at the start. Within a month, a basic data integration is deployed, followed by an advanced data integration within an additional 1 to 2 months.
After the event series is set up, the same setup can be used for multiple events. All that needs to be done is to connect the video, audio, and data feeds to the defined endpoints and set up the events in the NW system.
[Part of Production & Operations]
Once the content flow is defined and set up, the next step is simply connecting the feeds with the specified inputs. The NW EXP system can seamlessly handle alterations from one event to another, such as camera unavailability or shifts in content flow.
Here some guiding questions as a thought reference when configuring events, allowing preparation before the event goes live:
- How many video feeds are available and where are the cameras positioned? - NW EXP aims to enhance the viewing experience by contextualizing it. It allows for the individual organization and labeling of video feeds or their grouping into "entities." This grouping facilitates various use cases, such as linking front, back, and cockpit cameras into a single driver "entity" that users can select during their viewing experience.
- Depending on the content flow, is enough internet upload bandwith available to push all relevant feeds into the cloud (if using the NW Content Service)? - For example, if a 1080p feed and multiple bitrates (720p, 540p, ..) are directly encoded on site, we estimate around min. 20 Mbit/s per output stream without saftey overhead, see Low Latency Content Streaming for more information.
- How many audio feeds are available and how are they structured? - NW EXP can handle global and local audio tracks and can handle various multi audio use cases e.g. commentary in different languages, team radio, stadium sounds. The full concept is explained in later sections.
- Are all content feeds equipped with accurate time information and timecodes for precise and automated synchronization? - Different options are available, and this will be already defined in the project setup phase, see Low Latency Content Streaming for more information.
When the NW content service is used to stream the content, then there is no difference between live and VOD content. Any content is immediately available as VOD, thus also supporting instant replays of any moment in the past from all perspectives. The storage duration can be specified and is set to indefinite by default "subject to content rights".
If working with external stream URLs that switch between live and VOD, they can simply be replaced after the event is ended.
The NW content service provides redundancy for multiple content objects and supports several AVCoders pushing identical feeds for failover. NW EXP tracks all content objects, aligning them on a unified timeline, and dynamically selects them. Therefore, if one content object stops, it seamlessly switches to an available one without any user interaction.
[Part of Production & Operations]
NW Events can be manually set up within the NativeWaves Console, or automated via REST APIs. The event configurations have the flexibility to be reused across a series of events or set up individually based on changing requirements. For instance, during certain games in the season, coverage might vary, resulting in fewer available video feeds.
The full process is described in the Getting Started section.
[Part of Content Distribution]
NW EXP was designed with scalability at its core. As a result, all content streams can be directed through a Content Distribution Network (CDN).
NativeWaves offers a seamless integration method for your own CDN within the content flow, leveraging the Origin Service. This approach allows your CDN to manage the final stage of content distribution, granting you complete control over scalability and costs.
Scalability largely relies on the CDN, responsible for caching content and delivering it to end-users. Hence, if the CDN provider can manage the user base's load, NativeWaves will scale accordingly.
Given NW EXP utilizes conventional HTTP streaming, there's no adverse impact on streaming. Your existing CDN, capable of handling the load, will suffice for NW EXP.
[Part of App, UX, Platform]
NW EXP is available for multiple platforms, and can be integrated into existing applications.