AnInsomniacy/aria2-next v2.8.0

v2.8.0 - Native HLS/DASH Downloads and Browser Capture Support

on GitHub

Before upgrading

• Linux binaries require glibc 2.35 or newer and a compatible system C++ runtime, matching Ubuntu 22.04. Older Linux installations must upgrade before using these binaries.
• HLS/DASH manifests are now recognized automatically by URL or HTTP content type. Use --media=file when a script needs to save the original playlist or manifest unchanged.
• If you used an unreleased media build, incompatible media checkpoints and task caches are discarded. Existing downloaded output is kept.

Native media downloads

• HLS and MPEG-DASH: download finite presentations or record live streams. Select video, audio and subtitle tracks, then save MP4, Matroska or compatible subtitle-only WebVTT output without transcoding.
• Inspect before downloading: expose available tracks and pause before fetching media payload. Track IDs remain stable when a manifest reorders its representations; unavailable selections return an explicit error.
• Recording and time ranges: set a live recording duration, finish a recording on demand, or select a finite HLS/DASH range. Ranges follow segment boundaries rather than individual frames.
• Pause, restart and retry: persist committed segments and track selection in SQLite, verify cached resources before reuse, and recover interrupted output finalization. aria2.retryMedia retains the task's GID and recovery data; aria2.finishMedia finalizes a live recording.
• Media progress: report download or recording phases and completed media duration. Final output size remains unknown until remuxing finishes; live streams do not show a fabricated completion percentage.

Browser capture support

• Accept captured HLS/DASH manifests, ordered media fragments, separate source tracks and relative track offsets through media-input and media=collection.
• Support AES-128 keys and IVs supplied with captured inputs. OpenSSL handles decryption, and FFmpeg checks candidate output. Inline live manifests retain their original URLs for subsequent refreshes.
• Apply browser request headers to their observed origins, including scheme and port. Redirects, child playlists, segments and key requests each select their own context instead of inheriting another origin's credentials.
• Advertise media capabilities and structured errors through RPC so clients can negotiate capture support and distinguish authentication, protected-media and selection failures.

Browser discovery and recording are handled by the client; the engine accepts captured inputs for downloading and remuxing.

Engine changes and fixes

• Integrate GPAC 26.07.0 for manifests and segment timing, and FFmpeg 8.1.2 for demuxing and remuxing. Transfers use the existing libcurl transport; the engine does not launch an external downloader or FFmpeg process.
• Refactor task lifecycle, RPC, options, HTTP transport, BitTorrent and platform code into focused modules while retaining the existing CLI, RPC and libaria2 entry points.
• Centralize output naming. Use accepted payload headers for implicit HTTP filenames, preserve already-decoded browser hints, and retain the resolved path across restarts. Media titles keep embedded dots and receive the selected container extension.
• Fix BitTorrent progress freezing after hash failures or file-selection changes by consuming libtorrent's native file progress, while retaining native completion checks.
• Preserve separate HLS audio renditions, subtitle timing and presentation offsets through remuxing, including supported discontinuities and multi-period DASH content.

Scope

DRM and unsupported encryption remain explicit errors. There is no transcoding. Captured fragments must form compatible media streams; arbitrary complete videos cannot be concatenated through this interface. Live recovery is limited to media still available from the server, and output containers must support the selected codecs.

See the media download guide for CLI examples, RPC fields, track selection and recovery behavior.

Downloads

Release binaries and SHA-256 checksums are attached after the release build completes.

Full changelog: v2.7.5...v2.8.0