From: "Tomas Härdin" <git@haerdin.se>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] mxfenc.c: look for reel_name within streams as well
Date: Wed, 06 Sep 2023 20:29:08 +0200
Message-ID: <3b0a28e8793f7bc79762b9b5dec9429d0f0c2b83.camel@haerdin.se> (raw)
In-Reply-To: <8E129170-900A-4E57-990F-9FB6D1EF922A@cine.dev>
ons 2023-09-06 klockan 12:16 +0200 skrev Bart Styczen:
> If an MXF file has reel_name stored in a stream, while copying or
> remuxing file, some (most) of the stream metadata is lost.
> Here’s the file:
> https://streams.videolan.org/ffmpeg/incoming/original.mxf
> After running ffmpeg -i original.mxf -c copy output.mxf, and checking
> with ffprobe,
> the original file has the following stream metadata:
> > file_package_umid:
> > 0x060A2B340101010501010D431300000064F640280FA57031060E2B347F7F2A80
> > file_package_name: B002C0006_230803_1932_000001 (0)
> > track_name : B002C0006_230803_1932_000001 (0)_v1
> > reel_umid :
> > 0x060A2B340101010501010D431300000064F640280FA67031060E2B347F7F2A80
> > reel_name : B002C0006_230803_1932_000001 (1)
> > timecode : 00:06:15:21
>
> And the copied file only these:
> > file_package_umid:
> > 0x060A2B340101010501010D001339242252947134203924220052947134203901
> > file_package_name: B002C0006_230803_1932_000001 (0)
>
>
> After applying the patch, copied file correctly shows reel metadata
> and the timecode:
> > file_package_umid:
> > 0x060A2B340101010501010D001321CA09529471342721CA090052947134272101
> > file_package_name: B002C0006_230803_1932_000001 (0)
> > reel_umid :
> > 0x060A2B340101010501010D001321CA09529471342721CA090052947134272102
> > reel_name : B002C0006_230803_1932_000001 (1)
> > timecode : 00:06:15:21
>
>
> The track_name is still missing though, so I will continue to
> investigate the issue.
Sounds like a mismatch in behavior between mxfdec and mxfenc. Timecode
etc going missing suggests a deeper issue to which this patch is likely
the wrong fix..
You should report this on trac if you haven't already
/Tomas
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
next prev parent reply other threads:[~2023-09-06 18:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-06 10:16 Bart Styczen
2023-09-06 10:27 ` Paul B Mahol
2023-09-06 10:55 ` Bartłomiej Styczeń
2023-09-06 18:29 ` Tomas Härdin [this message]
2023-09-06 19:35 ` Bartłomiej Styczeń
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3b0a28e8793f7bc79762b9b5dec9429d0f0c2b83.camel@haerdin.se \
--to=git@haerdin.se \
--cc=ffmpeg-devel@ffmpeg.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
This inbox may be cloned and mirrored by anyone:
git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
ffmpegdev@gitmailbox.com
public-inbox-index ffmpegdev
Example config snippet for mirrors.
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git