VideoHelp Forum




+ Reply to Thread
Results 1 to 8 of 8
  1. Member
    Join Date
    Aug 2015
    Location
    Quebec, Canada
    Search PM
    Hello all

    I'm using TMPGenc MPEG Smart Renderer 6 to remove a precise part of a video (frame to frame), it's working perfectly, only frames around is re-encoded and I output losslessly.

    the problem : TMPGenc add this tag on the output file "Stardard: Component", that isn't there on the original video, see example

    Width : 1 920 pixels
    Height : 1 080 pixels
    Display aspect ratio : 16:9
    Frame rate mode : Constant
    Frame rate : 23.976 (24000/1001) FPS
    Standard : Component -----------------------THIS ONE
    Color space : YUV
    Chroma subsampling : 4:2:0
    Bit depth : 8 bits
    Scan type : Progressive

    is it possible to easily remove this tag ? or managed TMPGenc not to add it ?

    I've tried many similar program, Lossless Cut, SolveigMM Video Splitter, Avidemux, Bandicut. None of them give a result as good as TMPGenc but none of them add this tag "Stardard:Component" neither.

    I've tried ffmpeg to remove all tag, and it's not working for this one.

    Thanks guys
    Quote Quote  
  2. TMPGEnc embeds a “Standard : Component” metadata field in some output formats;
    you can stop it by changing export/container settings or remove it afterward with a metadata editor.

    Prevent tag when exporting (TMPGEnc Video Mastering Works — general steps)
    1. Open your project and go to the Export/Encode dialog for the target format (MP4/MKV/TS, etc.).
    2. Select the Preset/Template you use, then click **Advanced** or **Option** to open container/format settings.
    3. Look for any metadata, stream label, or MXF/AVC/HEVC "component" options:
    - For MP4/MKV/TS: uncheck options labeled **Write metadata**, **Write stream tags**,
    **Add encoder tag**, **Add component**, **Write creation metadata**, or similar.
    - For MXF or professional formats: set **Write Component/Standard metadata** = Off, or switch container profile to a more basic/Raw profile.
    4. Save the adjusted preset and re-export. Verify with MediaInfo or ffprobe that the tag is gone.

    For TMPGEnc MPEG Smart Renderer 6

    - Open Smart Renderer 6 and load your project/profile.
    - Click your export profile → choose Edit (or double‑click the profile).
    - In the Profile Editor, open the Output Settings or Format tab.
    - Click Advanced (or Options) for the chosen container (MP4/TS/M2TS).
    - Look for metadata/stream tag options and disable:
    Write metadata
    Write stream tags
    Add encoder/standard/component
    Write creation metadata If you see a checkbox for Component or Standard, uncheck it.
    - Save the edited profile and export using that profile.

    Remove tag from existing files (simplest GUI tool)
    Use Avidemux (free) or MKVToolNix GUI (for MKV) or a metadata editor:
    1. Open file in Avidemux → File → Save (choose container) — ensure "Copy" for video/audio and no metadata options selected.
    2. For MKV: open MKVToolNix GUI → add file → Output → Global tags/Attachments — remove unwanted tags → Start multiplexing.
    3. Verify with MediaInfo/ffprobe.

    STEP-BY-STEP

    TMPGEnc has no explicit toggle, simplest reliable approach is re-muxing with ffmpeg:

    1) Check existing tags:

    Code:
    ffprobe -v quiet -show_format -show_streams "input.mp4"
    2) Remux and drop all metadata:

    Code:
    ffmpeg -i "input.mp4" -map 0 -c copy -map_metadata -1 "output.mp4"
    Incremental change: if you only want to remove a specific tag (e.g., "STANDARD:Component"), first view metadata, then:

    Code:
    ffmpeg -i "input.mp4" -map 0 -c copy -metadata:s:v:0 comment="" "output.mp4"
    After export/remux, verify with ffprobe or MediaInfo;
    if tag persists, export to a different container (e.g., MP4 → MKV) then remux back without metadata.

    Hope this helps ..
    Last edited by videoAI; 9th Nov 2025 at 19:15.
    There is nothing wrong .. with my environment
    Quote Quote  
  3. Member
    Join Date
    Aug 2015
    Location
    Quebec, Canada
    Search PM
    Thanks for those solution / ideas, unfortunately none are working to remove the Stardard:Component metadata tag.

    if someone else round have more ideas or have already face this, feel free to suggest

    Thanks

    kalemvar
    Quote Quote  
  4. Can you post a small sample? I wanna try a different tool ..
    Last edited by videoAI; 10th Nov 2025 at 03:30.
    There is nothing wrong .. with my environment
    Quote Quote  
  5. Member
    Join Date
    Aug 2015
    Location
    Quebec, Canada
    Search PM
    sent in PM
    Quote Quote  
  6. Did you send me the original file [before cutting]?
    If yes, the original already has the 'Standard: Component'

    General
    Complete name : C:\T\MetaData\xxxxx_S01E01_Blink.mp4
    Format : MPEG-4
    Format profile : Base Media / Version 2
    Codec ID : mp42 (mp42/isom/avc1)
    File size : 31.4 MiB
    Duration : 30 s 30 ms
    Overall bit rate mode : Variable
    Overall bit rate : 8 781 kb/s
    Frame rate : 23.976 FPS
    Encoded date : 2025-11-10 10:36:46 UTC
    Tagged date : 2025-11-10 10:36:46 UTC
    Writing application : TMPGEnc MPEG Smart Renderer 6 Trial Version 6.1.2.20

    Video
    ID : 1
    Format : AVC
    Format/Info : Advanced Video Codec
    Format profile : High@L4
    Format settings : CABAC / 4 Ref Frames
    Format settings, CABAC : Yes
    Format settings, Reference fra : 4 frames
    Codec ID : avc1
    Codec ID/Info : Advanced Video Coding
    Duration : 30 s 30 ms
    Bit rate mode : Variable
    Bit rate : 8 138 kb/s
    Maximum bit rate : 10 000 kb/s
    Width : 1 920 pixels
    Height : 1 080 pixels
    Display aspect ratio : 16:9
    Frame rate mode : Constant
    Frame rate : 23.976 (24000/1001) FPS
    Standard : Component
    Color space : YUV
    Chroma subsampling : 4:2:0
    Bit depth : 8 bits
    Scan type : Progressive
    Bits/(Pixel*Frame) : 0.164
    Stream size : 29.1 MiB (93%)
    Writing library : AVC Coding
    Encoded date : 2025-11-10 10:36:46 UTC
    Tagged date : 2025-11-10 10:36:46 UTC
    Color range : Limited
    Color primaries : BT.709
    Transfer characteristics : BT.709
    Matrix coefficients : BT.709
    Codec configuration box : avcC

    Audio
    ID : 2
    Format : AC-3
    Format/Info : Audio Coding 3
    Commercial name : Dolby Digital
    Codec ID : ac-3
    Duration : 30 s 30 ms
    Source duration : 30 s 48 ms
    Bit rate mode : Constant
    Bit rate : 640 kb/s
    Channel(s) : 6 channels
    Channel layout : L R C LFE Ls Rs
    Sampling rate : 48.0 kHz
    Frame rate : 31.250 FPS (1536 SPF)
    Compression mode : Lossy
    Stream size : 2.29 MiB (7%)
    Source stream size : 2.29 MiB (7%)
    Language : English
    Service kind : Complete Main
    Default : Yes
    Alternate group : 1
    Encoded date : 2025-11-10 10:36:46 UTC
    Tagged date : 2025-11-10 10:36:46 UTC
    Dialog Normalization : -31 dB
    compr : -0.28 dB
    cmixlev : -3.0 dB
    surmixlev : -3 dB
    dialnorm_Average : -31 dB
    dialnorm_Minimum : -31 dB
    dialnorm_Maximum : -31 dB
    Originally Posted by kalemvar1 View Post
    sent in PM
    There is nothing wrong .. with my environment
    Quote Quote  
  7. Member
    Join Date
    Aug 2015
    Location
    Quebec, Canada
    Search PM
    file without tag sent in PM, sorry for that
    Quote Quote  
  8. NP ..

    I ran some tests, generated Metadata into Json files for comparison,
    used my own meta data utility, & used Losslesscut to test few things ..

    To appreciate the complexity of editing Metadata in general, I included
    some useful info at the end of this post.

    I have not used any TMPGEnc products in the last 15 years, although
    I did in the past, but not for Metadata config per se.

    But I do have some experience writing Apps that read and save Metadata.

    I think your options are:

    1- Find A way to prevent TMPGEnc from adding any Metadata (or at least
    not adding the field in question), so far no straight forward solution. You can
    try editing the config file(s) at the file system directly.

    2- Use another tool to cut. Losslesscut is my preferred option here. [check
    out the latest v.367, and its Metadata editing feature].

    3- Since every tool you use most certainly will attempt to edit, or add to the
    Metadata, if you wish to keep the Metadata intact, you can try extracting it
    before the cut and adding it afterwards.

    Hope this helps a bit ..

    Originally Posted by kalemvar1 View Post
    file without tag sent in PM, sorry for that
    ==================================================

    Some Vendors embed extensive, standardized metadata (MXF, XMP, EXIF, ID3-like),
    others use proprietary atoms/boxes (MP4/QuickTime) or sidecar files. [store metadata in files]

    Support levels differ by product focus: professional tools (Avid, Adobe, Apple Pro apps)
    follow standards closely; consumer platforms (YouTube, Facebook, Instagram) normalize or drop many tags.

    Key tags: technical (codec, bitrate, resolution, color profile), descriptive (title, description,
    keywords), rights (copyright, creator), timecode/asset IDs, and scene/shot markers.

    VENDOR SUMMARY

    - Adobe Premiere / After Effects (high support)
    - Formats/tags: XMP, IPTC, QuickTime atoms, MXF metadata.
    - Adherence: Strong to XMP/IPTC and SMPTE when using MXF; writes sidecar XMP for some exports.
    - Notes: Preserves many descriptive and technical tags; good for editorial workflows.

    - Avid Media Composer (professional)
    - Formats/tags: MXF with SMPTE, AAF for sequence-level metadata.
    - Adherence: High for broadcast standards (SMPTE/AS-11, AS-10).
    - Notes: Strong for timecode, tape/generation metadata, asset tracking.

    - Apple Final Cut Pro / Compressor (medium–high)
    - Formats/tags: QuickTime atoms, MXF (in pro workflows), limited XMP.
    - Adherence: Good for QuickTime conventions; less emphasis on IPTC/XMP.
    - Notes: Apple-specific atoms may appear; metadata often retained inside .mov.

    - DaVinci Resolve (high)
    - Formats/tags: QuickTime atoms, MXF, XML for project interchange, sidecar support.
    - Adherence: Good to industry standards; strong HDR/color metadata support
    (SMPTE ST 2086/CTA-861.3).
    - Notes: Excellent technical/color metadata handling.

    - FFmpeg / open-source tools (variable)
    - Formats/tags: Reads/writes many containers’ tags (MP4 atoms, Matroska tags, XMP via wrappers).
    - Adherence: Capable but depends on flags/containers; some metadata lost if not explicit.
    - Notes: Powerful for batch extraction/rewriting; requires care to preserve complex metadata.

    - MP4/QuickTime (container behavior)
    - Tags: atoms (ftyp, moov, meta, udta) with keys for title/artist/comment, custom atoms possible.
    - Adherence: Flexible but many apps use proprietary atoms; no single universal schema.

    - Matroska / MKV
    - Tags: XML-based tags, supports extensive custom fields.
    - Adherence: Flexible, but consumer tools may ignore nonstandard tags.

    - MXF (broadcast)
    - Tags: SMPTE metadata sets, extensive descriptive/technical fields.
    - Adherence: Designed for professional interchange; vendors implementing MXF usually follow standards closely.

    - YouTube / Vimeo / Social Platforms (low–medium retention)
    - Tags: Platform-side metadata fields (title, description, tags, thumbnails); many container tags stripped or ignored.

    - Cameras (Sony, Canon, RED, ARRI)
    - Tags: Camera-specific metadata (lens, exposure, color metadata, timecode),
    often in sidecar or proprietary headers (R3D, ARRIRAW).

    COMMON STANDARDS & TAGS
    - XMP/IPTC: descriptive (title, creator, keywords, rights). Widely supported in Adobe/pro apps.
    - EXIF: image-origin metadata; limited for video but used in some camera formats.
    - SMPTE / MXF sets: timecode, tape IDs, technical descriptors for broadcast.
    - QuickTime atoms / MP4 boxes: technical and descriptive; many vendor-specific atoms.
    - Matroska tags: XML extensible metadata.
    - Sidecars (XML/JSON/AAF/EDL/CPL): used to carry richer editorial/compliance metadata.

    LEVELS OF SUPPORT
    - High: Avid, Adobe (XMP), MXF-based pro gear — preserves standards, extensive tags.
    - Medium: Apple, DaVinci, FFmpeg (with correct options) — good support but container/vendor quirks.
    - Low: Social platforms, consumer transcoders — strip or normalize many embedded tags.
    - For web: expect platforms to use only title/description/tags — store rich metadata in sidecars or CMS.

    ==================================================
    There is nothing wrong .. with my environment
    Quote Quote  



Similar Threads

Visit our sponsor! Try DVDFab and backup Blu-rays!