[FFmpeg-devel] Fwd: Fate test for mxfdec.c: prefer metadata from Footer -

Am 2023-02-16 18:14, schrieb emcodem@ffastrans.com:
> Am 2023-02-12 01:25, schrieb Tomas Härdin:
>> fre 2023-02-03 klockan 14:54 +0100 skrev emcodem@ffastrans.com:
>>> Am 2021-07-03 15:13, schrieb emcodem@ffastrans.com:
>>> > Am 2021-06-28 21:58, schrieb emcodem@ffastrans.com:
>>> > > Am 2021-06-28 03:00, schrieb Marton Balint:
>>> > > > On Sun, 27 Jun 2021, emcodem@ffastrans.com wrote:
>>> > > >
>>> > > > > Am 2021-06-27 20:12, schrieb Marton Balint:
>>> > > > > > Why? I though it is enough if you store the partition
>>> > > > > > number in the
>>> > > > > > metadata set, that way you should be able to compare if the
>>> > > > > > existing
>>> > > > > > metadata set is better than the current one when adding a
>>> > > > > > new
>>> > > > > > metadata
>>> > > > > > set. Or am I missing something?
>>> > > > >
>>> > > > > OK, i just had a try on this but honestly i don't know how
>>> > > > > this
>>> > > > > could work without a very deep change of the whole mxfdec.c.
>>> > > > > The problem is that i cannot just add a field to the struct
>>> > > > > MXFMetadataSet as this points to raw data which has been read
>>> > > > > from
>>> > > > > the mxf file. I could add a field but if i initialize the
>>> > > > > value, i
>>> > > > > will automatically destroy the original raw data which was
>>> > > > > read from
>>> > > > > the mxf file.
>>> > > >
>>> > > > See the attached patch, that is what I had in mind. Or is it
>>> > > > overkill?
>>> > > > Can you test it with your dataset and see if it makes any
>>> > > > difference?
>>> > > >
>>> > > > Thanks,
>>> > > > Marton
>>> > > > _______________________________________________
>>> > > > 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".
>>> > >
>>> > > Tested your patch pleasure, thanks for the support! The "score
>>> > > approach" seems to work in practice exactly as my previous patch,
>>> > > the
>>> > > only thing i fear about is that it is a little harder now to
>>> > > foresee
>>> > > which metadata source is taken from a users perspective but i
>>> > > also
>>> > > think it is now more compliant than it was before.
>>> > >
>>> > > Using my test fileset which contains 4.476 mxf files (not all
>>> > > unique,
>>> > > maybe half is duplicates and most focus on xdcamhd and D10), we
>>> > > have
>>> > > 90 differences between ffprobe before your patch and after your
>>> > > patch.
>>> > > All of the differences are only in files that have openincomplete
>>> > > header. Most of the differences just changes the duration from a
>>> > > guessed one to the analyzed one:
>>> > >
>>> > > All STREAMS (NEW - OLD):
>>> > >       "duration_ts": 3000,              "duration_ts": 3099,
>>> > >       "duration": "120.000000",         "duration": "123.960000",
>>> > > FORMAT      (NEW - OLD):
>>> > >     "duration": "120.000000",           "duration": "123.969813",
>>> > >     "bit_rate": "61178142",             "bit_rate": "59219070",
>>> > >
>>> > > Exception one Op1b self contained file, where the "old" version
>>> > > did
>>> > > not spit out a "duration" value at all, so it was not even
>>> > > calculated
>>> > > from bitrate, it was just missing in the format section and set
>>> > > to 0
>>> > > in the stream section.
>>> > > Exception two, there were 4 files (3 were samples from IRT and 1
>>> > > a
>>> > > real world file from old omneon version) where the startc OLD was
>>> > > 0
>>> > > and the new one was the MP starttimecode from MP, so perfect.
>>> > > So the conclusion is that of course your version had the same
>>> > > effect
>>> > > on my testfileset than my patch version, so thats nice.
>>> > >
>>> > > Also, the FATE samples i shared will still work and can be used
>>> > > for
>>> > > this patch.
>>> > > Attached a patch for adding only the fate samples. Note that
>>> > > these
>>> > > Fate tests of course fail when the patch for mxfdec.c is not
>>> > > applied.
>>> > > https://we.tl/t-MVmyG2mZHq
>>> > >
>>> > > Thanks a lot!
>>> > > -emcodem
>>> > > _______________________________________________
>>> > > 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".
>>> >
>>> > Unfortunately the wetransfer link for the fate samples expired, so
>>> > i
>>> > thought it might be a good idea to resend it as link to gdrive:
>>> > https://drive.google.com/file/d/1yXTdS9RfOsduzg49vBLEshdmIzdaVQfd/view?usp=sharing
>>> >
>>> > Also attached the 2 patches: 1 from cus for mxfdec.c and one from
>>> > myself for the corresponding fate samples.
>>> > After applying the mxfdec.c patch, fate will pass with the
>>> > currently
>>> > existing tests but the files in the zip must be uploaded to the
>>> > fate
>>> > suite before applying my corresponding patch of course (otherwise
>>> > the
>>> > files don't exist).
>>> >
>>> > It would be cool if someone found the time and wants to apply this.
>>> >
>>> > Thanks!
>>> > -emcodem
>>> 
>>> Hi Thomas,
>>> sorry i totally forgot about completing the fate tests for this.
>>> The needed file is meanwhile in the official fate-suite repo so this
>>> should pass the automatic fate tests.
>>> 
>>> I did add 2 different tests for the patch that Marton applied that
>>> makes
>>> the demuxer prefer closed complete footer over header.
>>> Both tests use the same file in fate-suite:
>>> omneon_8.3.0.0_xdcam_startc_footer.mxf
>>> This reference file is the shortest completely original example that
>>> i
>>> was able to produce on a real omneon broadcast server. It serves as a
>>> good reference not only for this patch.
>>> 
>>> Test 1) test if TC is preferred from footer.
>>> Test 2) test if it still works as expected when there is no footer.
>>> (more or less inverted test 1) This is done by simulating a
>>> "truncated
>>> file" using subfile protocol i chose the end of file is in the video
>>> data of the last mpeg2 frame because that is what i see mostly with
>>> truncated files in production.
>>> 
>>> Hope this can be applied now as it is.
>> 
>> Meant to reply to this earlier, but yes good samples are crucial for
>> these kinds of tests. Obviously footer metadata will tend to be the
>> most accurate and should be preferred.
>> 
>> It's getting late, hopefully I'll have some time to look at this next
>> week. There are some other things that need doing in mxfdec as well..
>> 
>> /Tomas
> 
> Let me know if you need assistence with any of the "other doings" :D

This is mostly for Tomas Härdin i guess because we have a history with 
this...
Attached a revised version of the fate tests for the "prefer metadata 
from Footer" patch.
Thanks to the guys i met on the Linux days in Chemnitz, we found and 
fixed an issue that would only occur on Mac (needed to changed quoting 
around subfile protocol to fix it). Special thanks to the great Mr. Carl 
Eugen at this point but also to Thilo who actally executed the revison 
and Alex Strasser (sorry that we didnt have the chance to say goodbye 
actually, it was great to meet you all) :D

Please let me know any doubts.

Thanks,
emcodem

Message ID	c2a14a2aa4c6e4c6b36c20815d35a5b1@ffastrans.com
State	New
Headers	show Delivered-To: ffmpegpatchwork2@gmail.com Received-SPF: pass (google.com: domain of ffmpeg-devel-bounces@ffmpeg.org designates 79.124.17.100 as permitted sender) client-ip=79.124.17.100; MIME-Version: 1.0 Date: Mon, 13 Mar 2023 18:06:25 +0100 From: emcodem@ffastrans.com To: ffmpeg-devel@ffmpeg.org In-Reply-To: <6d89e141275e43a4b85f4d16fd82be37@ffastrans.com> References: <20210524103027.30367-1-emcodem@ffastrans.com> <20210626082010.11899-1-emcodem@ffastrans.com> <alpine.LSU.2.20.2106271143280.30253@iq> <28b01b132d9b3b93617f712c951d0ab6d5ccd65c.camel@acc.umu.se> <alpine.LSU.2.20.2106272005250.11763@iq> <801ee217bbfbf30c2b86720821e7166b@ffastrans.com> <alpine.LSU.2.20.2106280011190.11763@iq> <5a59585298a4427f94b7fb3e6f930bd4@ffastrans.com> <b9fb44b04a61430ffa54e2aa784bfa26@ffastrans.com> <1fd4513f2a8f38069878c10a15287394@ffastrans.com> <a32eb453ad475f590114a9550fe2295a@ffastrans.com> <4cf141e02b0abdff716c7787f2f7de64e502485a.camel@haerdin.se> <60d949d662f60e6bfa8493af0f725c58@ffastrans.com> <6d89e141275e43a4b85f4d16fd82be37@ffastrans.com> User-Agent: Roundcube Webmail/1.5.2 Message-ID: <c2a14a2aa4c6e4c6b36c20815d35a5b1@ffastrans.com> Content-Type: multipart/mixed; boundary="=_0cbd8dc81a839bc8b42f83ee8a75fe5e" Fwd: Fate test for mxfdec.c: prefer metadata from Footer - Precedence: list Reply-To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" <ffmpeg-devel-bounces@ffmpeg.org>
Series	[FFmpeg-devel] Fwd: Fate test for mxfdec.c: prefer metadata from Footer - \| expand [FFmpeg-devel] Fwd: Fate test for mxfdec.c: prefer metadata from Footer -

Context	Check	Description
andriy/commit_msg_x86	warning	The first line of the commit message must start with a context terminated by a colon and a space, for example "lavu/opt: " or "doc: ".
yinshiyou/configure_loongarch64	warning	Failed to apply patch
andriy/make_x86	success	Make finished
andriy/make_fate_x86	success	Make fate finished

[FFmpeg-devel] Fwd: Fate test for mxfdec.c: prefer metadata from Footer -

Checks

Commit Message

Patch