Skip to content

v0.1.9.4 — Auto-transcode when a file can't play directly

Choose a tag to compare

View all tags
@kosm1x kosm1x released this 23 Jul 03:17
v0.1.9.4
7f8ae6d

A patch on v0.1.9.3.

Videos that "should" play but don't, now play automatically

Even with FFmpeg installed and working, a file can use a codec that VLMP thought the browser could play directly, but the browser actually can't decode (for example AV1 — browser support for it is inconsistent — or 8-bit 4:2:2/4:4:4 H.264). Before, that showed an error. Now the player automatically retries by transcoding the moment direct play fails, so the video just plays (using your GPU if hardware transcoding is on). No setting to change — it's automatic.

If transcoding itself can't run (FFmpeg missing/unreachable by the service), you'll get a clear message instead of a silent failure.

Also fixed

  • A very low-resolution source (under 360p) could produce an empty, unplayable transcode — it now falls back to the lowest quality rung.
  • A browser with no HLS support now shows a clear message instead of loading forever.

Audited R1+R2; the retry logic is loop-proof and verified live. 376 tests.

Version note: package metadata reads 0.1.9-4 (npm requires three-part semver); this is the v0.1.9.4 release.

SmartScreen warns on the unsigned installer — "More info → Run anyway". FFmpeg is not bundled (the installer offers a winget install).

Assets 3
Loading