Skip to content

FrameMeld V0.1.2

Choose a tag to compare

View all tags
@LiTA8341 LiTA8341 released this 09 Aug 13:32
V0.1.2
64086b8

FrameMeld V0.1.2 adds precise device and export diagnostics for host integrations while preserving ordinary FFmpeg pass-through and standalone encoder fallback behavior.

Highlights

  • Added opt-in structured-status-json-v1 lifecycle events covering progress, first frame, first encoded packet, performance summary, child return codes, and failure domains.
  • Added device-diagnostics-json-v1 with FFmpeg Vulkan inventory and conservative DXGI-to-RIFE mapping evidence. Mappings without stable UUID/LUID identity are reported as candidate, ambiguous, unmatched, or unknown rather than exact.
  • AMD AMF and Intel QSV are reported as separate system-default binding branches; NVIDIA NVENC retains explicit -gpu binding support.
  • Host-planned adapter metadata is kept separate from runtime-observed device binding, avoiding false claims that a requested GPU was actually selected.
  • Ordinary commands without -framemeld continue to pass through to the bundled FFmpeg 9 core.

Download

FrameMeld_ffmpeg-V0.1.2-windows-x64.zip

SHA-256: 3BECBD156A9FBABCD0EE42C081B5FD6122A279DB2FA08D033E793393382CCDB3

Extract the archive and run the top-level framemeld-runtime\ffmpeg.exe. This is a Windows x64 prebuilt runtime.

Verification

  • 65/65 unit tests passed with the bundled Python/VapourSynth runtime.
  • 720p60 RIFE motion-blur to HEVC smoke test passed.
  • Nine real headless engine paths passed: RIFE interpolation, RIFE motion blur, balanced/adaptive policy, SVP interpolation, old/SVP/RIFE deduplication, and blur/timescale/color processing.
  • NVIDIA RTX 5070 Ti was physically tested. AMD AMF and Intel QSV logic is covered by tests but still requires vendor-hardware field validation.

FrameMeld is licensed under GPL-3.0-only. The archive includes the full license, third-party notices, and pinned runtime manifest.

Assets 3
Loading