2018-11-10 4:31 GMT+01:00, Lewis Fox :
> I originally planned on putting a shared function for writing the elementary
> stream descriptor in mov_esds.c, along side the function that reads the
> elementary stream descriptor. However, the implementation in movenc.c used
> the MOVTrack class, which w
2018-11-08 17:34 GMT+01:00, Jan Ekström :
> Then regarding the rest. Do I understand correctly that you do
> not trust dolby's specification and/or mpeg-4 ra and would only
> like identifiers be added that have been seen in the wild?
This is not trust-related, I simply believe this patch is good
2018-11-08 8:25 GMT+01:00, Jan Ekström :
> When looking into something that is specified, wouldn't you go
> through it and enable what it mentions if you notice that there
> were actually more things than you originally thought?!
This may be acceptable for "DTS4" or similar but in general, it
is
This fixes an issue that was reported on the mpv issue tracker. some more
informations can be found there including test files.
https://github.com/mpv-player/mpv/issues/6153
0001-avcodec-videotoolbox-fix-cropping-with-HEVC-and-h264.patch
Description: Binary data
___
Signed-off-by: Paul B Mahol
---
libavfilter/Makefile | 1 +
libavfilter/af_astretch.c | 330 ++
libavfilter/allfilters.c | 1 +
3 files changed, 332 insertions(+)
create mode 100644 libavfilter/af_astretch.c
diff --git a/libavfilter/Makefile b/libav
vf_bwdif's frame management logic is almost identical to that of yadif.
The only difference is that it tracks the first and last fields in a
sequence, and that requires slight changes to the common code.
Assuming it's reasonable to do that tracking even though yadif doesn't
need it, we can then re
After adding field type management to the common yadif logic, we can
remove the duplicate copy of that logic from bwdif.
---
libavfilter/bwdif.h | 34 +
libavfilter/vf_bwdif.c | 235 +---
libavfilter/x86/vf_bwdif_init.c | 3 +-
3 files change
On 10/23/2018 1:49 AM, Mark Wu wrote:
> After inspecting the source code of x265, mpv and ffmpeg, I've found that
> ffmpeg mistakenly regards EVC_NAL_BLA_N_LP and HEVC_NAL_IDR_N_LP as non-
> reference frames, which are acutally reference frames according to the
> specification in x265, and drops
The bwdif filter can use common yadif frame management if we track
when a field is the first or last field in a sequence. While this
information is not used by yadif, the added benefit of removing the
duplicated frame management logic makes it worth tracking this state
in the common code.
---
liba
On Sun, 4 Nov 2018, Marton Balint wrote:
On Sun, 4 Nov 2018, James Almer wrote:
On 11/4/2018 9:06 AM, Marton Balint wrote:
Also add SIMD which works on lines because it is faster then calculating
it on
8x8 blocks using pixelutils.
Signed-off-by: Marton Balint
---
configure
On date Monday 2018-11-05 16:12:04 +0100, Michael Niedermayer encoded:
> On Mon, Nov 05, 2018 at 12:06:46PM -0200, Pedro Arthur wrote:
> > Hi,
> > I'm requesting the reimbursement of travel expenses for the Google
> > Mentor Summit.
> > I mentored the Super Resolution project, more details can be f
Ping
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
On Fri, Nov 09, 2018 at 09:11:31PM +0800, Jun Zhao wrote:
> They are come from 2003 and delete them.
>
> Signed-off-by: Jun Zhao
> ---
> fftools/ffmpeg.c |6 --
> 1 files changed, 0 insertions(+), 6 deletions(-)
LGTM
thx
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF13
On Fri, Nov 09, 2018 at 11:20:45PM +0100, Paul B Mahol wrote:
> On 11/9/18, Michael Niedermayer wrote:
> > Fixes: Out of memory
> > Fixes:
> > 10970/clusterfuzz-testcase-minimized-ffmpeg_AV_CODEC_ID_IMM4_fuzzer-5698750043914240
> >
> > Found-by: continuous fuzzing process
> > https://github.com/go
On Fri, Nov 09, 2018 at 06:31:38AM +0100, Andreas Rheinhardt wrote:
> The first element of H264RedundantPPSContext is not a pointer to an
> AVClass as required.
>
> Signed-off-by: Andreas Rheinhardt
> ---
> libavcodec/h264_redundant_pps_bsf.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(
Firstly, I want to say sorry about the repeat messages yesterday. It
was my first time using git-send-email (and a mailing list in
general), and I had some problems. I think I have things figured out
now.
On Sat, Nov 10, 2018 at 6:32 AM Carl Eugen Hoyos wrote:
>
> 2018-11-10 4:31 GMT+01:00, Lewis
The valid range is -255 to 255.
Signed-off-by: James Almer
---
libavcodec/cbs_av1.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/libavcodec/cbs_av1.h b/libavcodec/cbs_av1.h
index f662265f75..84622ed189 100644
--- a/libavcodec/cbs_av1.h
+++ b/libavcodec/cbs_av1.h
@@ -210,7
Signed-off-by: James Almer
---
See https://0x0.st/sljR.webm
libavcodec/cbs_av1.c | 30 +-
1 file changed, 9 insertions(+), 21 deletions(-)
diff --git a/libavcodec/cbs_av1.c b/libavcodec/cbs_av1.c
index ff32a6fca5..215f9384e8 100644
--- a/libavcodec/cbs_av1.c
+++ b/li
18 matches
Mail list logo
