Low Latency Content Streaming

nw exp was intentionally created to accommodate streaming from external providers as well as through the nw content service docid 2vvmvdu4mn886 w0xyk6l streaming through the content service offers complete flexibility to support end to end content flow in various scenarios, whether conventionally via sdi on site in an ob truck, optionally utilizing a nw avcoder docid 4dst 3sqiz724cyyzbghq , remotely in a production setting, or directly in the cloud in general all common industry formats for audio and video are supported, ranging from srt, rtmp, whip/whep, etc for point to point connections over to hls, dash, mp4, etc for end user delivery including all common video and audio codecs the content ingest and transcoding for end user distribution can occur either in a single step or across different facilities for instance, streaming might progress from sdi to srt to the cloud, where transcoding and packaging take place for distribution through a content distribution network (cdn) the content service seamlessly integrates with the origin service docid\ ronb6ttsm4ymnkjue6u6c , enabling integration with a custom cdn to channel the entire content flow through it nw streaming overview content synchronization multiple methods are available to synchronize content across diverse audio, video, and data feeds, encompassing automated procedures through embedded timecodes within the video/audio content or the content itself, along with manual adjustments accessible within the console the fundamental objective is to maintain the real world timestamp when a frame was captured and use this data to synchronize all video, audio, and data feeds precisely as each setup varies, this task can be intricate; hence, nativewaves streamlines this process by accommodating different methods of extracting time information from diverse content streams in different formats automatically in instances where time information is absent, the system assumes certain values the ultimate aim is to automate this process extensively therefore, it's advisable for producers to incorporate timecodes in the video feeds whenever feasible having timing information that correlates the pts timestamp of the video feed with real world event time (e g , frame 85 captured at event time 12 00 01 500) is ideal this synchronization can be achieved by embedding metadata within the video feed or utilizing timing information like program date time in a hls manifest low latency at nativewaves, we believe that low latency is crucial for streaming live events, whether it's at the venue, on the go, or at home conventional streaming methods that introduce delays of over 30 seconds have proven inadequate, particularly when compared to the much faster delivery of traditional tv signals furthermore, we want to prevent scenarios where users receive event notifications on their mobile devices before witnessing the actual moment in the live stream, causing unwanted spoilers with a significant delay several low latency streaming technologies have emerged in the last few years that can reduce latency to a minimum as part of the nativewaves cloud platform docid\ nvstigq7vuyrvila15qpw , we offer a content service docid 2vvmvdu4mn886 w0xyk6l which is a low latency http based streaming service that leverages all the developments of the last 5 years in this field (cmaf, ll hls, hesp, …) and achieves a sub three second latency lens to screen that is scalable with conventional cdns for a broadcast audience of millions of viewers this system can also be tuned to achieve sub second latency at the venue including drm protection nativewaves exp leverages existing implementations of video/audio players such as exoplayer (android), avplayer (ios), and hls js (web) rather than developing its own playback core, nativewaves exp closely manages playback and seeking within the content by utilizing these well established player frameworks since nativewaves exp relies on the underlying player implementations, the low latency streaming capabilities are dependent on the features and performance offered by each platform's player currently, nativewaves exp achieves sub three second latency from lens to screen with ll hls across all platforms furthermore, we are continuously exploring opportunities to expand the streaming protocol support this involves collaborating with both commercially available player integrations and exploring custom player integrations the ability to origin service docid\ ronb6ttsm4ymnkjue6u6c is also a key aspect from a business standpoint broadcasters and streaming platform providers often have contracts in place that optimize the cost of data transfer per gigabyte, making it cost effective for accommodating large audiences specifically for in venue streaming, webrtc based systems have emerged that are generally more challenging to scale cost effectively but can reduce latency even further (< 100 milliseconds end to end) which makes it an interesting choice for various use cases our guiding principle is to prioritize the best possible watching experience, which is why we adopt a partnership driven strategy we actively engage in close collaboration with leading streaming tech providers to collectively push boundaries and allow for effortless integration within established broadcast and streaming systems nw exp also facilitates the combination of webrtc and http based streaming for individual audio/video feeds, offering the advantages of both technologies ultra low latency and scalability combined with instant replay functionailty