Overview
MPEG-DASH (Dynamic Adaptive Streaming over HTTP) is an HTTP-based adaptive streaming protocol for live and VOD delivery. A DASH stream uses an.mpd manifest and media segments, so it can be cached and delivered through Gcore CDN like other HTTP video formats.
Low-Latency MPEG-DASH (LL-DASH) is the low-latency mode for DASH live streaming. It enables 2-4 second glass-to-glass latency with CMAF (Common Media Application Format) segments and Gcore’s Chunked-Proxy technology, which streams content immediately as it’s received instead of waiting for complete file downloads.
When to use DASH via CDN
Use Video CDN for DASH if:- You already have DASH streams (
.mpdmanifests and media segments) - You handle transcoding and packaging on your side
- You need broad device compatibility for Android, Smart TVs, web browsers, or custom players
- You want CDN features like geo-blocking, secure tokens, origin shielding, or custom domains
When to use LL-DASH
Use LL-DASH if:- You need 2-4 second latency for live events (sports, auctions, gaming)
- Your transcoder produces MPEG-DASH with CMAF segments
- You need broad device compatibility (Android, Smart TVs, web browsers)
- You want an industry-standard alternative to LL-HLS
- You need transcoding from RTMP/SRT → Use Video Streaming instead
- You want automatic ABR ladder generation → Use Video Streaming instead
How LL-DASH works on Gcore CDN
Traditional CDN delivery (high latency)
Standard CDNs use “Store and Forward” delivery:- The CDN edge waits for the complete segment to download from the origin (2-6 seconds).
- Only then starts sending to viewers.
- Result: minimum latency of 10–15 seconds.
Gcore Chunked-Proxy delivery (low latency)
Gcore’s Chunked-Proxy module uses immediate streaming:- The CDN then begins delivering the segment to viewers.
- Immediately starts streaming to viewers while still downloading.
- Uses HTTP Chunked Transfer Encoding (HTTP/1.1) or Framing (HTTP/2/3).
- Result: 2-4 second glass-to-glass latency.
Requirements
To use DASH via Gcore CDN:Quick setup
Step-by-step guide: Create a CDN Resource for Video Streaming Select the “For Live MPEG-DASH CMAF Streaming” tab for complete instructions on:- Requesting Chunked-Proxy activation from support
- Configuring cache rules for manifests and segments
- Enabling “Always online” for reliability
- Testing your low-latency stream
Supported file formats
How Chunked-Proxy works
Without Chunked-Proxy (standard CDN)
With Chunked-Proxy (Gcore CDN)
- Byte-level streaming: Data flows from origin → CDN → viewer simultaneously
- Protocol optimization: HTTP/1.1 Chunked Transfer Encoding, HTTP/2 Framing
- RAM-based caching: LIVE STREAMING preset uses RAM instead of disk
- Origin shielding compatible: Reduces origin load while maintaining low latency
Activation process
Step 1: Request Chunked-Proxy activation
Contact Gcore Support with:- Your CDN resource ID or domain
- Confirmation you’re using LL-DASH with CMAF segments
- Your origin transcoder details (Wowza, Nginx-RTMP, FFmpeg, etc.)
Using Gcore Video Streaming? If you’re using our Video Streaming Platform with transcoding, Chunked-Proxy is already enabled by default. No activation needed.
Step 2: Configure CDN resource
After activation, follow the cache configuration steps in the Getting Started Guide. Key settings:- Manifests (
.mpd): 2 second cache - Segments (
.m4s): 60 second cache - Always online: Enabled (error + timeout, not updating)
- LIVE STREAMING preset: Enabled for RAM caching
Best practices
Origin configuration
- Segment duration: 2-6 seconds (shorter = lower latency, higher overhead)
- Chunked encoding: Enable chunked transfer encoding on your origin
- Availability window: Keep 30-60 seconds of segments available
CDN optimization
- Origin shielding: Recommended for 100+ concurrent viewers
- Edge locations: Content cached at 210+ global edge servers
- Monitoring: Use CDN Statistics to track performance
Player compatibility
Ensure your video player supports:- MPEG-DASH playback
- CMAF segment format
- Low-latency mode (if available)
- dash.js (with low-latency mode)
- Shaka Player
- ExoPlayer (Android)
- AVPlayer (iOS/tvOS with DASH support)
Latency comparison
Technical deep dive
For video engineers and CTOs interested in the technical implementation: Engineering blog post: Optimizing HLS and DASH for 3-second latency This article covers:- HTTP Chunked Transfer Encoding implementation
- HTTP/2 and HTTP/3 framing optimizations
- Origin-to-edge-to-viewer data flow
- Benchmarks and performance analysis
- Comparison with other low-latency approaches
Troubleshooting
High latency (>10 seconds)
Cause: Chunked-Proxy not activated or not working correctly Solution:- Verify Chunked-Proxy is activated by support
- Check origin supports chunked encoding
- Verify CMAF segments are used (not MPEG-TS)
- Contact Gcore Support for diagnostics
Buffering or playback issues
Cause: Cache settings too aggressive or manifest updates too slow Solution:- Reduce manifest cache to 1-2 seconds
- Ensure segment cache is 60 seconds
- Enable “Always online” (error + timeout only)
- Check origin availability and response times
Need help?
Contact Gcore Support or use the chat in the bottom-right corner.Scope: CDN with its own video origin
The settings on this page apply to a custom CDN resource with its own video origin. When the CDN resource is linked to Gcore Streaming, Gcore Streaming controls almost all of its settings, and the streaming CDN guide applies instead.
Next steps
Getting Started Guide
Complete setup instructions to create a CDN resource for video streaming
HLS and LL-HLS
Alternative HLS formats for standard and low-latency streaming
Video CDN Overview
All Video CDN features and capabilities
Engineering Blog
Technical deep dive: 3-second latency optimization