Verify your Wowza Streaming Engine version and license support LL-HLS output; LL-HLS delivery was added in a specific Wowza version — check the Wowza release notes for the minimum supported version.
In the application's streaming configuration, enable the Apple Low-Latency HLS playback type; this configures the packager to produce CMAF fMP4 partial segments and emit EXT-X-PART and EXT-X-SERVER-CONTROL tags.
Set the target part duration (chunk size) to approximately 200–500 ms and ensure the segment duration is a multiple of the part duration.
Configure the Wowza HTTP origin to support blocking playlist reload requests (requests with _HLS_msn and _HLS_part query parameters); Wowza handles this server-side when LL-HLS mode is enabled.
If using a CDN in front of Wowza, verify the CDN supports LL-HLS cache behavior (partial segment caching, blocking reload pass-through); not all CDN configurations support this without custom rules.
Test playback with Safari (native HLS) and hls.js (lowLatencyMode: true) to confirm the LL-HLS latency target is met.
Known gotchas
CDN compatibility is the most common LL-HLS deployment problem; many CDN edge configurations cache the full playlist and do not pass blocking reload query parameters to the origin.
Wowza's LL-HLS implementation details and configuration property names vary between Wowza Streaming Engine and Wowza Video (cloud); use the correct documentation for your deployment type.
CMAF fMP4 partial segments require the encoder to produce keyframes aligned to part boundaries; misaligned keyframes cause the INDEPENDENT attribute to be absent on most parts, degrading seek behavior.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp