Fixed
- Progress bar pinned even when ffmpeg's
time=field is valid but stuck behind the encoder (single-job, no GPU contention). v0.3.43 fixed the case wheretime=N/A, but on some files the muxer's clock advances at first then parks at e.g.time=00:03:13for the rest of the encode while frames keep being produced — confirmed in the field withprogress=6.43%, fps=386→397, ETA increasingon a single-job-at-a-time run. Fix: parse bothtime=andframe=every progress line and use whichever yields higher progress.frame=is always honest (it's just the encoder's output counter),time=reflects the muxer's commit position which can lag arbitrarily on files with timing quirks. Taking the max of the two means we never under-report when the muxer's clock is stuck behind the encoder.
Docker images
Pinned to this release:
docker pull ghcr.io/i-ial9000/shrinkerr:0.3.44 # portable (amd64 + arm64, CPU)
docker pull ghcr.io/i-ial9000/shrinkerr:0.3.44-nvenc # x86_64 + NVIDIA GPU (NVENC)
docker pull ghcr.io/i-ial9000/shrinkerr:0.3.44-edge # as above but ffmpeg master
docker pull ghcr.io/i-ial9000/shrinkerr:0.3.44-edge-nvencFloating tags (:latest, :edge, :nvenc, :edge-nvenc) track the most recent release of each lineage.