Embed export settings as container metadata - #428
Open
RufanMelfor wants to merge 1 commit into
Open
Conversation
|
All contributors have signed the CLA. Thank you! |
…etadata Every export now writes a JSON snapshot of the settings actually used (codec, quality, resolution, blend width, and AI/autocam parameters) into the output video's "comment" container tag - readable via `ffprobe -show_entries format_tags` or most media tools. Useful for telling apart a batch of test exports with varying AI/blend settings without a separate sidecar file. Adds EncoderConfig::metadata_comment (set on the output context before write_header, since muxers bake container metadata into the header) and StitchJob::metadata_comment(String) builder; both reco-cli and reco-gui build the JSON automatically for every export, no new flag needed. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
RufanMelfor
force-pushed
the
feat/export-metadata-comment
branch
from
July 16, 2026 10:37
5ffb0a8 to
2519fa2
Compare
Contributor
Author
|
I have read the CLA Document and I hereby sign the CLA |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Every export now writes a JSON snapshot of the settings actually used
(codec, quality, resolution, blend width, and AI/autocam parameters) into
the output video's "comment" container tag — readable via
ffprobe -show_entries format_tagsor most media tools. Useful for telling apart abatch of test exports with varying AI/blend settings without needing a
separate sidecar file.
Adds
EncoderConfig::metadata_comment(set on the output context beforewrite_header, since muxers bake container metadata into the header atthat point — MP4's
moovudtaatom, Matroska's Tags element, etc.) anda
StitchJob::metadata_comment(String)builder. Bothreco-cliandreco-guibuild the JSON automatically for every export — no new flag orcheckbox needed.
Verified:
fmt --check/build/cargo test -p reco-io -p reco-cli -p reco-guiclean (only the pre-existing, unrelatedmatroska_reader_sees_partial_writestiming gap fails, confirmedidentical with or without this change).