Skip to content

FEATURE REQUEST: Add an interface for embedding tags in MKV files #1008

Open

Description

@iamdamosuzuki

We'd love to have an interface (somewhere in the config tag) that allows users to embed metadata into specific MKV tags.

Eventually it'd be great to have acces to the entire NMAAHC Standard Tag Set. However, for now just these tags would be incredibly helpful:

  • ENCODER_SETTINGS
  • ENCODED_BY
  • _PRE_TRANSFER_NOTES
  • _TRANSFER_NOTES

Additionally, the DATE_DIGITIZED tag should have a toggle that allows it to be automatically updated with the current date, and the DATE_TAGGED tag should automatically be updated with the current date if tagging occurs.

paging @BleakleyMcD to see if he has anything to add

Activity

  1. dericed commented on Aug 27, 2026

    @dericed
    Member

    what should ENCODER_SETTINGS and ENCODED_BY be set to?

  2. BleakleyMcD commented on Aug 27, 2026

    @BleakleyMcD

    @BleakleyMcD thinks that is a great idea!

  3. iamdamosuzuki commented on Aug 27, 2026

    @iamdamosuzuki
    ContributorAuthor

    We're using the ENCODER_SETTINGS convention that NMAAHC uses, which @BleakleyMcD came up with. This is a string that contains the playback VTR, TBC, ADC, Computer and Software settings. Since vrecord can't know that stuff, this should be a freetext field that the user can enter manually. ENCODED_BY can also be a free text field

  4. dmarcuswalker commented on Sep 29, 2026

    @dmarcuswalker

    Also looking forward to this feature! Below is a reference to share for how we document coding history by attaching a TXT file in the MKV; we are planning to start using the ENCODER_SETTINGS embedded field.

    Coding History
    Playback Deck: Panasonic AG-1980P; SN: G0TC00339
    Audio: Sonifex RB-UL4; SN: 086243
    Digital Processing Synchronizer: Leitch DPS-575; SN: 10115; Firmware: 1.51
    Video Capture Card: Blackmagic Design UltraStudio 4K Mini; SN: 9836238

    I should note that the computer and software settings are not included, largely because this is already captured for us in the _capture_options.log (but maybe we should start including that as well?) Also, I'm thinking now that we should start indicating what source video signal type was captured (e.g., composite, Y/C, component, SDI)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions