hwren (3):
lavc: add avs2 parser
lavf: add avs2 fourcc
lavc,doc,configure: add avs2 video decoder wrapper
Changelog| 1 +
configure| 4 ++
doc/decoders.texi| 6 ++
doc/general.texi | 14
libavcodec/Makefile | 2 +
libavcodec
Signed-off-by: hwren
---
libavcodec/Makefile | 1 +
libavcodec/avcodec.h | 1 +
libavcodec/avs2_parser.c | 95
libavcodec/codec_desc.c | 7
libavcodec/parser.c | 1 +
libavcodec/version.h | 4 +-
6 files changed, 107 in
Signed-off-by: hwren
---
Changelog | 1 +
configure | 4 ++
doc/decoders.texi | 6 ++
doc/general.texi | 14
libavcodec/Makefile| 1 +
libavcodec/allcodecs.c | 1 +
libavcodec/libdavs2.c | 177 ++
Signed-off-by: hwren
---
libavformat/riff.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/libavformat/riff.c b/libavformat/riff.c
index 8911725..4153372 100644
--- a/libavformat/riff.c
+++ b/libavformat/riff.c
@@ -369,6 +369,7 @@ const AVCodecTag ff_codec_bmp_tags[] = {
{ AV_CODEC_ID_Z
On 07/16/2018 02:55 AM, Michael Niedermayer wrote:
On Sun, Jul 15, 2018 at 09:13:04PM +0200, Mina wrote:
Hi,
This patch introduces Grey-Edge algorithm as part of the Color Constancy
Filter project in GSOC.
V3 changes:
- corrected typo in documentation
- corrected wrong value in documentat
> >
> > Is there anyone reviewing my patch? I sent 9 patchs about 20 days ago, but
> > only one patch received reply at June 14.
>
> Theres a maintainer listed for mips in MAINTAINERs
> he should review the patches. If he has no time then someone else should
> maybe help him
> Also it may make
Plan to push tonight.
On 14-07-2018 02:15 PM, Gyan Doshi wrote:
Date: Sat, 14 Jul 2018 13:59:51 +0530
Subject: [PATCH] avformat/mov: only set handler_name from mdia->hdlr
6 FATE references updated.
Fixes #7104
___
ffmpeg-devel mailing list
ffmpeg-dev
Hi all
Just wanted to remind everyone who submits fate tests to fate.ffmpeg.org
that testing releases is also a good idea.
It feels like iam the only one testing release/2.8 for example when
i look at http://fatebeta.ffmpeg.org/v2.8
thanks
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF
From: James Darnley
---
Michael, can you test this for the same failure you saw last time?
tests/fate/vcodec.mak | 24
tests/ref/vsynth/vsynth1-vc2-t5_3 | 4
tests/ref/vsynth/vsynth1-vc2-thaar | 4
tests/ref/vsynth/vsynth2-vc2-t5_3
Hi,
This patch introduces Grey-Edge algorithm as part of the Color
Constancy Filter project in GSOC.
V4 changes:
- Fixed error in filter.texi that resulted in breaking "make
doc/ffprobe-all.html"
Best regards,
Mina Sami
>From 7e24e01bc3a8303e4876b6a455dfc7d933efb6aa Mon Sep 17 00:00:00
I'll likely be pushing a change to the MOV demuxer tonight which will
change a tag, so you'll probably need to re-gen your refs.
Regards,
Gyan
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Hi Marton,
>
> In the current implementation per-frame timecode is stored as
> AV_PKT_DATA_STRINGS_METADATA side data, when AVPackets become AVFrames, the
> AV_PKT_DATA_STRINGS_METADATA is automatically converted to entries in the
> AVFrame->metadata AVDictionary. The dictionary key is "timeco
On 7/16/2018 7:29 AM, Michael Niedermayer wrote:
> Hi all
>
> Just wanted to remind everyone who submits fate tests to fate.ffmpeg.org
> that testing releases is also a good idea.
> It feels like iam the only one testing release/2.8 for example when
> i look at http://fatebeta.ffmpeg.org/v2.8
For
Hi Michael,
On Sat, Jul 14, 2018 at 4:01 PM Michael Niedermayer
wrote:
> On Fri, Jul 13, 2018 at 12:43:36PM +0100, Marcin Gorzel wrote:
> > Rematrixing supports up to 64 channels. However, there is only a limited
> number of channel layouts defined. Since the in/out channel count is
> obtained f
Hello,
I have updated patch 2, it shall work now.
Thank you,
Vasile Toncu
On Mon, Jul 16, 2018 at 4:49 PM, Vasile Toncu
wrote:
> Hello,
>
> I have updated patch 2, it shall work now.
>
> Thank you,
> Vasile Toncu
>
> On Wed, May 30, 2018 at 2:00 PM, Vasile Toncu
> wrote:
>
>> Hello,
>>
>> So
Hello,
I have updated patch 2, it shall work now.
Thank you,
Vasile Toncu
On Wed, May 30, 2018 at 2:00 PM, Vasile Toncu
wrote:
> Hello,
>
> Sorry for the late reply, I've been working on other projects.
> Here is patch 2, which adds vf_reinterlace filter. To my understanding,
> patch 2 and pat
Hello,
I have updated patch 3, it shall work now.
Thank you,
Vasile Toncu
From 23bdcea190ccb801e3d5a0eb081fb28b17144452 Mon Sep 17 00:00:00 2001
From: Vasile Toncu
Date: Mon, 16 Jul 2018 16:13:10 +0200
Subject: [PATCH] Patch 3 - Move reinterlace to tinterlace
---
configure
On 16-07-2018 03:34 PM, Gyan Doshi wrote:
Plan to push tonight.
On 14-07-2018 02:15 PM, Gyan Doshi wrote:
Date: Sat, 14 Jul 2018 13:59:51 +0530
Subject: [PATCH] avformat/mov: only set handler_name from mdia->hdlr
6 FATE references updated.
Fixes #7104
Pushed as 8aa6d9a8d37b365c8989d11e0d1
> +static const enum AVPixelFormat input_pix_fmts[] = {
> +AV_PIX_FMT_NV12,
> +AV_PIX_FMT_0RGB,
> +AV_PIX_FMT_BGR0,
> +AV_PIX_FMT_RGB0,
> +AV_PIX_FMT_GRAY8,
> +AV_PIX_FMT_YUV420P,
> +AV_PIX_FMT_YUYV422,
That is really interesting feedback guys. I have been thinking about things
mostly in a MOV independent timecode track (or tracks) kind of way, but I know
OMF, MXF, AAF, etc handle it more analogously to packet/frame side data.
Usually ffmpeg has some kind of superset of functionality for handli
> On Jul 16, 2018, at 2:56 PM, Jonathan Morley wrote:
>
> That is really interesting feedback guys. I have been thinking about things
> mostly in a MOV independent timecode track (or tracks) kind of way, but I
> know OMF, MXF, AAF, etc handle it more analogously to packet/frame side data.
>
>
On Mon, Jul 16, 2018 at 03:37:15PM +0100, Marcin Gorzel wrote:
> Hi Michael,
>
> On Sat, Jul 14, 2018 at 4:01 PM Michael Niedermayer
> wrote:
>
> > On Fri, Jul 13, 2018 at 12:43:36PM +0100, Marcin Gorzel wrote:
> > > Rematrixing supports up to 64 channels. However, there is only a limited
> > nu
> if theres a file with 5 video streams it doesnt make sense to summarize
> teh file with the bitrate of 1 stream
> Also the user has no indication of this change, the number is just different
> theres nothing informing him that it is no longer the files bitrate
I was thinking to output stats for
With some (garbled) OGG data, PTS can overflow causing undefined behavior.
This patch avoids that by zeroing out PTS values greater than 2^62.
From 26a8582bc04f5bddc037ffcce99025e2f977abe0 Mon Sep 17 00:00:00 2001
From: Fredrik Hubinette
Date: Mon, 16 Jul 2018 14:54:43 -0700
Subject: [PATCH] Avoid
On Sun, Jul 15, 2018 at 1:03 AM Michael Niedermayer
wrote:
>
> On Sat, Jul
> 14, 2018 at 12:04:46PM +0200, Marton Balint wrote:
> >
> >
> > On Sat, 14 Jul 2018, Michael Niedermayer wrote:
> >
> > >On Fri, Jul 13, 2018 at 10:51:00AM +0200, Marton Balint wrote:
> > >>
> > >>
> > >>On Thu, 12 Jul 201
On 17-07-2018 02:38 AM, Wang Cao wrote:
I was thinking to output stats for each video/audio stream one line by
another. It seems this would be a huge change to users who are not
aware. Keeping the old file bitrate looks good to me. Can I extend
this to output file bitrate for each output file?
26 matches
Mail list logo
