Skip to main content

Changelog

XUI 2.0 Changelog – Build 2603128C37

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


Overview

This build focuses on stability, performance optimization and critical system fixes. Core components were reworked to improve reliability and reduce resource usage.


New Features

Custom FFmpeg Command

  • Added support for custom FFmpeg command override
  • Replaces the auto-generated FFmpeg command between binary and output
  • Supports dynamic placeholders:
    • {STREAM_SOURCE} input stream
    • {LOGO} overlay logo
  • Applies only on servers pulling directly from source

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
XUI 2.0 Custom FFmpeg Command

Improvements

  • 🟢 Responsive UI fixed for mobile and desktop
  • 🟡 CSS visual inconsistencies resolved
  • 🟢 Build version added in footer
  • 🟢 Reduced RAM usage across processes

Bug Fixes

  • 🔴 Fixed high CPU usage in Catchup Timeshift (infinite loop)
  • 🔴 Fixed public API issues
  • 🟡 Fixed source scan and MAP detection
  • 🟡 Fixed playlist import limitations (.m3u8 supported)

System Changes

  • 🟢 Load Balancer ↔ Main Server communication reworked
  • 🟢 Stable under high latency, no ping loss
  • 🟢 Licensing system rebuilt, persistent HWID
  • 🟢 Network binary rewritten in Go for speed and accuracy

Streaming & Data Handling

Catchup / Timeshift

  • Fixed infinite loop in TVArchive
  • Reduced CPU usage significantly

API

  • Fixed public API endpoints
  • Improved response stability

Source Scanning

  • Fixed silent failures on slow sources
  • Improved MAP detection logic

Playlist Import

  • Supports .m3u and .m3u8
  • Requires valid M3U structure

Components

yt-dlp

  • 🟢 Updated to latest 2026 version
  • 🟡 Improved compatibility
  • 🟢 Better stability for live streams

Installation

InnoDB Auto Configuration

Automatically calculates innodb_buffer_pool_size based on RAM.

Logic:

  • ≤ 4 GB RAM → 40% (min 256M)
  • Rounded to nearest 128 MB
  • Fallback: 512M
4 GB RAM → 25% (max 4G)

Examples:

RAMResult
1 GB384M
2 GB768M
4 GB1G
8 GB2G
16 GB4G
32 GB4G

Notes

  • Recommended for production
  • Restart services after update
  • Monitor system after upgrade