Downloaded bytes and total file size are different facts. Flux can measure bytes already received even when a media server has not supplied a complete output size. A useful progress display must distinguish exact values from estimates rather than show a confident percentage based on a made-up total.
Direct files usually provide more size information
An ordinary file response can provide Content-Length or a range response with a known total. Streaming media may instead expose a sequence of segments, variable bitrates and separate audio. The final container can also differ in size from the sum of the network payloads because muxing changes its structure.
Duration can help estimate progress
For a finite recording, available media duration, manifest information and processing progress can help describe how far the task has advanced. Where the source exposes sufficient bitrate or size metadata, the app can estimate an output amount. Such an estimate should remain visibly approximate and can change as more information arrives.
Read the indicators together
- Downloaded bytes describe data already transferred.
- Network speed is current throughput, not the source’s promised bitrate.
- A known byte total supports a file-style percentage.
- A media-based estimate may use duration or segment progress.
- Remaining time can change when speed, source information or processing work changes.
Live and incomplete sources
A live stream has no fixed remaining duration while it continues publishing content. An inaccessible or partial manifest can also prevent a reliable estimate. Treat an unknown total as missing source information rather than automatically a stalled download. Check whether bytes continue increasing and whether the task has entered media processing before deciding what action to take.
Sources and release context
This guide describes the Flux 2.6.6 documentation. Check the current release record for package conditions.
