Sorry for Pinging again :-(
I know it's not much that the patch does but the resulting functionality
from a user perspective can be really useful, especially when using
programatically calculated avs scripts.From 243bb2cbae9fabc78fe7f48cb90ae1c620c51a51 Mon Sep 17 00:00:00 2001
From: emcodem
Da
---
libavformat/mov.c | 8
1 file changed, 8 insertions(+)
In quicktime reference files, exposing the parsed info for external essences
location can be very handy for users
diff --git a/libavformat/mov.c b/libavformat/mov.c
index 1c07cff6b5..e9625c0cf9 100644
--- a/libavformat/mov.c
++
Am 2021-03-06 10:48, schrieb Jan Ekström:
On Sat, Mar 6, 2021 at 10:38 AM emcodem wrote:
---
libavformat/mov.c | 8
1 file changed, 8 insertions(+)
In quicktime reference files, exposing the parsed info for external
essences location can be very handy for users
Unfortunately
Added support for reading Start Timecode from Footer (if any).
Specifically targets Omneon 6.4.3.0 but also works on other Versions and
Vendors, e.g. when Header is OpenIncomplete.
Function mxf_resolve_strong_ref_reverse can potentially be re-used for getting
other values like Duration and
Orig
Sorry for the delay on this, should have corrected it much earlier.
There was some confusion in the interlaced analysis. From 3rdparty decoders
perspective, a clip
can only be interlaced when it is NOT field_based. This is because in a
field_based clip, the fields
are separate images, so it is ac
Am 2021-05-24 17:31, schrieb Tomas Härdin:
mån 2021-05-24 klockan 12:30 +0200 skrev emcodem:
Added support for reading Start Timecode from Footer (if any).
Specifically targets Omneon 6.4.3.0 but also works on other Versions
and Vendors, e.g. when Header is OpenIncomplete.
Function
le in how
exactly to do that, you want me to work from my current fork where the
commit i sent is included , alter it and commit again - or you want me
to start from scratch and send a totally new patch?)
Thanks a lot Steve
-emcodem
___
ffmpeg-devel
In case there is a Footer, regarding to SMPTE 377 all versions, the metadata in
Footer shall be correct (where in Header it can be incomplete)..
If there is no footer (stream, truncated...) it will still work as usual.
Tested with a huge set of files and compared old/new ffprobes, it will not
cha
Am 2021-06-27 20:12, schrieb Marton Balint:
On Sun, 27 Jun 2021, Tomas Härdin wrote:
Order of parsing depends on the file, we usually do header, footer
and then backwards the partitions. So after your patch metadata in
the second partition will have priority over footer, which is also
agains
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
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!
-emcodemFrom 499a41f0db6cfda746fd8751d4e55e910f495687 Mon Sep 17 00:0
ice.
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
___
Am 2021-07-04 17:28, schrieb Marton Balint:
On Sat, 3 Jul 2021, Tomas Härdin wrote:
lör 2021-07-03 klockan 15:13 +0200 skrev emco...@ffastrans.com:
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://dr
Am 2021-07-04 20:28, schrieb emco...@ffastrans.com:
Am 2021-07-04 17:28, schrieb Marton Balint:
On Sat, 3 Jul 2021, Tomas Härdin wrote:
lör 2021-07-03 klockan 15:13 +0200 skrev emco...@ffastrans.com:
Unfortunately the wetransfer link for the fate samples expired, so i
thought it might be a
devel-requ...@ffmpeg.org with subject "unsubscribe".
Anything left that needs investigation/correction on this one? ...it
looks to be a very nice addition so far.
Thanks
-emcodem
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.
.
Make FATE passed.From 31a37518afa5f9b635e6c52a8f29513bc756c715 Mon Sep 17 00:00:00 2001
From: emcodem
Date: Sun, 17 Jan 2021 01:02:08 +0100
Subject: [PATCH] Populate field order returned by avs script, Trac Ticket 8757
---
libavformat/avisynth.c | 20
1 file changed, 20
ways available.From 0725b04b8855723309662a9b663b346d98117ff1 Mon Sep 17 00:00:00 2001
From: emcodem
Date: Sun, 17 Jan 2021 18:59:41 +0100
Subject: [PATCH] Populate field order returned by avs script, Trac Ticket 8757
---
libavformat/avisynth.c | 15 +++
1 file changed, 15 inse
y greatest
weaknesses :D
Thanks for your patience and also thanks for telling me directly how the
formatting is done correctly.
New patch with formatted comment attached
From 243bb2cbae9fabc78fe7f48cb90ae1c620c51a51 Mon Sep 17 00:00:00 2001
From: emcodem
Date: Thu, 21 Jan 2021 18:59:45 +0100
Subje
Am 2021-01-20 16:41, schrieb Tomas Härdin:
ons 2021-01-20 klockan 00:27 +0100 skrev Marton Balint:
On Tue, 19 Jan 2021, Tobias Rapp wrote:
> On 18.01.2021 23:53, Tomas Härdin wrote:
> > lör 2021-01-16 klockan 08:43 +0800 skrev lance.lmw...@gmail.com:
> > > On Fri, Jan 15, 2021 at 09:43:58PM +0
Am 2021-01-26 00:34, schrieb Marton Balint:
Uhm guys, it is very bad practice: if you just insert a different
manufacturer name then you just cheat. SMPTE 377 has a clear statement
about what goes to the identification, you cannot just write the infos
from a different program there.
Libavfor
Am 2021-01-28 02:21, schrieb lance.lmw...@gmail.com:
I haven't found the s337m freely, so I'm not sure about the Platforma
metadata.
I think we haven't support the field yet, I guess it's 0x3C08 tag, but
I haven't
the document in hand so it's not OK to add it by me.
Yeah the SMPTE are unfortu
Am 2021-01-21 19:08, schrieb emco...@ffastrans.com:
On 2021-01-21 14:10, Stephen Hutchinson wrote:
Yeah, never mind about that. I didn't notice that those are declared
AVSC_INLINE, not AVSC_API, so they don't get used through the dynamic
API loader.
The comment formatting seems to have been me
070",
> >
> > 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
23 matches
Mail list logo
