lotobo/av-tools
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 4 Wiki Activity
Files
597ea044b6637df721bee04d496dd9f0fa3de0b5
av-tools/docs/REFERENCE_IMPLEMENTATIONS.md

4.8 KiB
Raw Blame History

Reference implementations

Inspection dates: 2026-07-24 (initial implementation) and 2026-07-26 (remaining-slice integration).

The references were cloned beside av-tools under /mnt/DATA/git/references/; no reference repository was nested in this working tree. Revisions are full immutable commit ids.

Repository Revision inspected Used for Copied or adapted
av-tools, git@git.add-ideas.de:lotobo/av-tools.git no revision: canonical main was unborn and had no commits canonical destination and licence/history check the empty repository was scaffolded in place; no prior code existed
Toolbox SDK, https://git.add-ideas.de/lotobo/toolbox-sdk.git ef2dab4b46c61812c9a877d8a19fe497b4a4630a (SDK 0.2.3) manifest schema/definition, AppShell, context behavior, shared styles, token-free registry, nested-path checks and toolchain baseline published 0.2.3 packages are direct dependencies; documented usage patterns were followed; no SDK source file was copied
Toolbox Portal, https://git.add-ideas.de/lotobo/toolbox-portal.git bda9da044d61c109afd9969d357cc27f76648938 initially; 5c052bc6d1073a66600cfddc44c0e16da34bede8 for final integration release ZIP/sidecar/lock formats, independent assembly, catalogue behavior, path security, nested deployment and production headers no portal application source was copied; the AV smoke harness consumes only an exact cloned Portal revision; the separate Portal worktree contains its own reviewed integration patch
ffmpeg.wasm, https://github.com/ffmpegwasm/ffmpeg.wasm.git f876f907c7e9b9bf51d4ed0b913a855a63ae63fc; pinned release baseline 71aa99d37c02a7b4c435275ca9ef50e612f6efa1 current API, worker lifecycle, filesystem, loading, ST/MT behavior, licence documentation and build layout no reference-worktree source was copied; wrapper/util remain exact npm dependencies, while the five core assets are rebuilt from the recorded source/toolchain/patch profile and verified against the build lock

For the pinned package set, the more specific upstream release tag v12.15 at 71aa99d37c02a7b4c435275ca9ef50e612f6efa1 was also inspected. It contains @ffmpeg/ffmpeg 0.12.15 and the source configuration for core 0.12.10. That revision's build selects FFmpeg n5.1.4. The shipped 0.12.10-reviewed-stack5m.1 assets additionally apply upstream ffmpeg.wasm commit b409e36475bc21f0451b5b1e1d126fa82871439a; exact build and source identities are in SOURCE.md and docs/FFMPEG_BUILD.md.

The active /mnt/DATA/git/toolbox-portal worktree has immutable revision 5c052bc6d1073a66600cfddc44c0e16da34bede8 as HEAD. Its staged cache-rule extension is documented separately and is not represented as a published revision.

Official behavior references:

  • https://ffmpegwasm.netlify.app/docs/overview/
  • https://ffmpegwasm.netlify.app/docs/getting-started/usage/
  • https://ffmpegwasm.netlify.app/docs/api/ffmpeg/classes/ffmpeg/
  • https://ffmpegwasm.netlify.app/docs/faq/
  • https://ffmpeg.org/ffmpeg.html
  • https://ffmpeg.org/ffprobe.html
  • https://ffmpeg.org/ffmpeg-formats.html
  • https://ffmpeg.org/ffmpeg-filters.html
  • https://ffmpeg.org/ffmpeg-utils.html

Command plans are based on those primary references and runtime capability queries, not unverified command snippets.