🚀 Release Notes — XUI 2.0 Build 260512FF48

Release Date: 13.05.2026
Version: v2.0.0
Type: Stable Release

This release introduces major improvements focused on low-latency streaming, backend optimization, infrastructure stability and safer deployment workflows. XUI 2.0 continues evolving into a faster, more scalable and production-ready IPTV platform.

⚡ New Feature: LL-HLS (Low-Latency HTTP Live Streaming)

Overview

XUI 2.0 now includes full support for LL-HLS, Apple's low-latency extension for HTTP Live Streaming.

Traditional HLS streams usually operate with 15 to 30 seconds of delay because of long MPEG-TS segments. The new LL-HLS implementation reduces latency down to approximately 1–3 seconds while remaining fully compatible with existing HLS players and streaming infrastructure.

The implementation uses:

• Fragmented MP4 (fMP4) segments
• Ultra-short segment durations
• Partial segment delivery
• Playlist preloading
• Native FFmpeg low-latency HLS generation

✨ Key Benefits

🔧 How It Works

When enabled, the system generates an additional LL-HLS output alongside the standard HLS stream.

Generated files include:

The playlist includes Apple's LL-HLS extensions:

• EXT-X-PART-INF
• EXT-X-PART
• EXT-X-SERVER-CONTROL
• EXT-X-PRELOAD-HINT

These extensions allow players to preload segments before finalization and significantly reduce playback delay.

⚙️ Configuration Options

LL-HLS can be configured directly from the Admin Panel.

📡 Player Access

Clients can access LL-HLS streams using:

GET /playlist/USERNAME/PASSWORD/m3u?output=llhls

Or directly:

GET /live/USERNAME/PASSWORD/STREAM_ID.m3u8?output=llhls

The built-in Shaka Player fully supports LL-HLS playback out of the box.

🚄 Performance Notes

• Uses FFmpeg native fmp4 HLS muxing
• No additional transcoding overhead
• Lower bandwidth usage
• Reduced disk I/O
• Automatic stale connection cleanup

🛠️ New Feature: Custom FFmpeg Command Override

XUI 2.0 now supports fully custom FFmpeg command injection directly inside the transcoding pipeline.

Administrators can override the default auto-generated FFmpeg command and create advanced transcoding workflows for overlays, branding, hardware acceleration and low-latency delivery.

🔧 Supported Placeholders

💡 Example

-re -fflags +genpts -async 1 -i {STREAM_SOURCE} -i /assets/images/logo.png -filter_complex "overlay=W-w-20:20" -c:v libx264 -preset ultrafast -tune zerolatency -b:v 4000k -c:a copy

🔧 Fix: RTMP Output Stabilization

RTMP output handling has been redesigned and stabilized for better compatibility with external ingest servers.

The output now correctly uses the FLV container together with the no_duration_filesize flag to improve long-running RTMP stability.

Improvements

• Fixed FLV stream packaging
• Improved RTMP connection stability
• Better compatibility with ingest providers
• Fixed authentication encoding issues

RTMP output can be enabled per-stream from the stream settings panel.

⚡ Improvement: LLOD V3 (PHP-based Low-Latency On Demand)

LLOD V3 received major internal optimizations focused on speed, lower resource usage and stream stability.

Unlike previous FFmpeg-based implementations, LLOD V3 performs direct MPEG-TS parsing inside PHP without relying on FFmpeg segmentation.

📈 What Improved

This significantly improves playback startup speed and lowers CPU usage under heavy workloads.

🌎 Improvement: TMDB Regional Spanish Locales

TMDB integration now supports multiple regional Spanish locales instead of generic es metadata only.

Supported locales include:

This improves metadata quality and region-specific naming across movies, series and automated imports.

🗄️ New Feature: Secure Database Migration Tool

The database migration system for upgrading from XUI 1.5.13 to XUI 2.0 has been completely rewritten from scratch.

The new migration workflow was designed to provide a safer and more reliable upgrade process while preserving the native XUI 2.0 schema and core configuration structure.

Unlike older migration methods, the new system intelligently applies all legacy migrations step-by-step while maintaining compatibility with the new XUI 2.0 architecture.

✅ Migration Improvements

🔄 How It Works

The migration process now performs:

1. Automatic database backup
2. SQL validation checks
3. XUI 2.0 schema preservation
4. Legacy data conversion
5. Step-by-step migration handling
6. Final integrity verification

At the end of the process, the server is fully migrated, optimized and ready for production usage.

💻 Migration Command

The migration command remains unchanged for compatibility with existing workflows.

Example:

/home/xui/tools restore /root/backup_2026-05-12_13:19:02.sql

Replace the SQL path with the correct location of your backup file.

📌 Summary