On Fri, Jan 3, 2020 at 5:28 PM James Almer wrote:
>
> On 1/3/2020 10:16 PM, James Zern wrote:
> > Signed-off-by: James Zern
> > ---
> > libavcodec/libvpxenc.c | 3 +--
> > 1 file changed, 1 insertion(+), 2 deletions(-)
> >
> > diff --git a/libav
On Wed, Jan 8, 2020 at 3:00 PM Wonkap Jang
wrote:
>
> Documentation change for adding support for encoding
> with temporal scalability in VP9.
> ---
> doc/encoders.texi | 18 +++---
> 1 file changed, 15 insertions(+), 3 deletions(-)
>
This could be a part of the first patch in the se
Hi,
On Fri, Jan 10, 2020 at 9:59 AM Wonkap Jang
wrote:
>
> This commit reuses the configuration options for VP8 that enables
> temporal scalability for VP9. It also adds a way to enable three
> preset temporal structures (refer to the documentation for more
> detail) that can be used in offline e
On Tue, Jan 14, 2020 at 11:07 AM Wonkap Jang
wrote:
>
> This commit reuses the configuration options for VP8 that enables
> temporal scalability for VP9. It also adds a way to enable three
> preset temporal structures (refer to the documentation for more
> detail) that can be used in offline encod
On Wed, Jan 15, 2020 at 6:20 PM Wonkap Jang
wrote:
>
> HI,
> My comments are in-line.
>
> On Tue, Jan 14, 2020 at 8:55 PM James Zern
> wrote:
>
> > On Tue, Jan 14, 2020 at 11:07 AM Wonkap Jang
> > wrote:
> > > [...]
> > > +
> > > +
On Thu, Jan 16, 2020 at 11:04 AM Wonkap Jang wrote:
>
> James,
>
> On Thu, Jan 16, 2020 at 10:58 AM Wonkap Jang <
> wonkap-at-google@ffmpeg.org> wrote:
>
> > This commit reuses the configuration options for VP8 that enables
> > temporal scalability for VP9. It also adds a way to enable three
>
On Mon, Dec 23, 2019 at 12:53 PM Wang Cao wrote:
>
> Signed-off-by: Wang Cao
> ---
> doc/encoders.texi | 3 +++
> libavcodec/libaomenc.c | 6 ++
> 2 files changed, 9 insertions(+)
>
lgtm. sorry for losing track of this.
> [...]
> +if (ctx->enable_restoration >= 0)
> + codecct
On Fri, Jan 17, 2020 at 2:45 PM James Zern wrote:
>
> On Mon, Dec 23, 2019 at 12:53 PM Wang Cao wrote:
> >
> > Signed-off-by: Wang Cao
> > ---
> > doc/encoders.texi | 3 +++
> > libavcodec/libaomenc.c | 6 ++
> > 2 files changed, 9 insertions(
On Fri, Jan 17, 2020 at 1:50 PM Wonkap Jang
wrote:
>
> This commit reuses the configuration options for VP8 that enables
> temporal scalability for VP9. It also adds a way to enable three
> preset temporal structures (refer to the documentation for more
> detail) that can be used in offline encodi
On Thu, Jan 23, 2020 at 2:26 AM James Almer wrote:
>
> This allows the user enable the realtime encoding speed mode
>
> Signed-off-by: James Almer
> ---
> The g_usage field is present since 1.0.0, but the AOM_USAGE_* defines were
> introduced with the real time mode about a year ago. Builds befor
On Fri, Jan 17, 2020 at 1:56 PM Wonkap Jang
wrote:
>
> Hi James,
>
> On Fri, Jan 17, 2020 at 1:50 PM Wonkap Jang wrote:
>
> > This commit reuses the configuration options for VP8 that enables
> > temporal scalability for VP9. It also adds a way to enable three
> > preset temporal structures (refe
On Mon, Feb 3, 2020 at 10:02 AM Wonkap Jang
wrote:
>
> In order for rate control to correctly allocate bitrate to each temporal
> layer, correct temporal layer id has to be set to each frame. This
> commit provides the ability to set correct temporal layer id for each
> frame.
> ---
> libavcodec/
On Mon, Feb 3, 2020 at 10:02 AM Wonkap Jang
wrote:
>
> This commit reuses the configuration options for VP8 that enables
> temporal scalability for VP9. It also adds a way to enable three
> preset temporal structures (refer to the documentation for more
> detail) that can be used in offline encodi
On Mon, Feb 3, 2020 at 5:45 PM Wonkap Jang
wrote:
>
> Hi
>
> On Mon, Feb 3, 2020 at 12:45 PM James Zern
> wrote:
>
> > On Mon, Feb 3, 2020 at 10:02 AM Wonkap Jang
> > wrote:
> > >
> > > In order for rate control to correctly allocate bitrate to e
On Thu, Feb 6, 2020 at 8:58 AM Wonkap Jang
wrote:
>
> Hi James,
>
> On Wed, Feb 5, 2020 at 5:29 PM James Zern
> wrote:
>
> > On Mon, Feb 3, 2020 at 5:45 PM Wonkap Jang
> > wrote:
> > >
> > > Hi
> > >
> > > On Mon, Feb 3
On Fri, Feb 7, 2020 at 10:44 AM Wonkap Jang
wrote:
>
> Hi James,
>
> On Fri, Feb 7, 2020 at 10:36 AM Wonkap Jang wrote:
>
> > In order for rate control to correctly allocate bitrate to each temporal
> > layer, correct temporal layer id has to be set to each frame. This
> > commit provides the abi
On Mon, Feb 10, 2020 at 10:30 AM Wonkap Jang
wrote:
>
> In order for rate control to correctly allocate bitrate to each temporal
> layer, correct temporal layer id has to be set to each frame. This
> commit provides the ability to set correct temporal layer id for each
> frame.
> ---
> doc/encode
On Mon, Feb 10, 2020 at 12:58 PM James Zern wrote:
>
> On Mon, Feb 10, 2020 at 10:30 AM Wonkap Jang
> wrote:
> >
> > In order for rate control to correctly allocate bitrate to each temporal
> > layer, correct temporal layer id has to be set to each frame. This
> &g
Hi,
On Fri, Apr 23, 2021 at 8:58 AM Mohammad Izadi
wrote:
>
> HDR10+ metadata is stored in the bit stream for HEVC. The story is different
> for VP9 and cannot store the metadata in the bit stream. HDR10+ should be
> passed to packet side data an stored in the container (mkv) for VP9.
>
> This
On Sun, Apr 25, 2021 at 3:39 PM Andreas Rheinhardt
wrote:
>
> Here the packet size is known before allocating the packet because
> the encoder provides said information (and works with internal buffers
> itself), so one can pass this information to ff_alloc_packet2() to
> avoid the implicit use of
Hi,
On Wed, May 12, 2021 at 8:33 PM Danny Wu wrote:
>
> > Shouldn't google not produce invalid files? Also, can you link one of
> > these videos to test this issue?
>
I filed a bug for this (b/188197059).
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmp
On Fri, May 21, 2021 at 2:19 AM Andreas Rheinhardt
wrote:
>
> Here the packet size is known before allocating the packet because
> the encoder provides said information (and works with internal buffers
> itself), so one can use this information to avoid the implicit use of
> another intermediate b
On Fri, May 21, 2021 at 2:18 AM Andreas Rheinhardt
wrote:
>
> Here the packet size is known before allocating the packet because
> the encoder provides said information (and works with internal buffers
> itself), so one can use this information to avoid the implicit use of
> another intermediate b
On Fri, May 21, 2021 at 2:19 AM Andreas Rheinhardt
wrote:
>
> Signed-off-by: Andreas Rheinhardt
> ---
> libavcodec/libvpxenc.c | 64 --
> 1 file changed, 31 insertions(+), 33 deletions(-)
>
lgtm.
___
ffmpeg-deve
On Wed, May 26, 2021 at 6:35 PM Mohammad Izadi
wrote:
> [...]
> +static void add_hdr10_plus(AVFifoBuffer *fifo, struct FrameHDR10Plus *data)
> +{
> +av_fifo_grow(fifo, sizeof(FrameHDR10Plus));
This return should be checked.
> +av_fifo_generic_write(fifo, data, sizeof(FrameHDR10Plus), NUL
On Tue, Jun 1, 2021 at 6:47 PM Mohammad Izadi
wrote:
> [...]
> +static av_cold int add_hdr10_plus(AVFifoBuffer *fifo, struct FrameHDR10Plus
> *data)
> +{
> +int err = av_fifo_grow(fifo, sizeof(FrameHDR10Plus));
Prefer sizeof(var) for these to match the rest of the code.
_
On Tue, Jun 1, 2021 at 6:23 PM Mohammad Izadi
wrote:
>
> On Fri, May 28, 2021 at 4:49 AM Michael Niedermayer
> wrote:
>
> > On Thu, May 27, 2021 at 09:44:10AM -0700, Mohammad Izadi wrote:
> > > HDR10+ metadata is stored in the bit stream for HEVC. The story is
> > different for VP9 and cannot sto
Hi,
On Wed, Jun 2, 2021 at 1:55 PM Valerii Zapodovnikov
wrote:
>
> HDR10+ test bitstream https://www.webmproject.org/vp9/levels/
>
> BTW, who knows what is Profile 4 VP9 (i.e. VP9.4)?
> https://stackoverflow.com/questions/61413665
>
This link is talking about a file with DRM. VP9 allows for 4 p
On Sat, Jun 5, 2021 at 10:16 PM Valerii Zapodovnikov
wrote:
>
> Yes, RGB is signalled by Identity matrix if and only if XYZ is not
> in transfer. XYZ primaries are just normal primaries that can be
> used for normal RGB, no problem, so I do not check for them.
> No need to test for sRGB primaries
On Sat, Jun 12, 2021 at 12:10 PM Thilo Borgmann wrote:
>
> Hi,
>
> if init fails, it's likely originating from the library's config. This and
> 2/2 are for easier debugging in that case instead of having to run again with
> loglevel DEBUG.
>
> ---
> libavcodec/libaomenc.c | 10 ++
> 1
On Sat, Jun 12, 2021 at 12:12 PM Thilo Borgmann wrote:
>
> $subject
>
> ---
> libavcodec/libvpxenc.c | 10 ++
> 1 file changed, 6 insertions(+), 4 deletions(-)
lgtm. Same comment for the else as for libaomenc.c
___
ffmpeg-devel mailing list
ff
On Wed, Jun 16, 2021 at 3:53 PM Mohammad Izadi
wrote:
>
> HDR10+ metadata is stored in the bit stream for HEVC. The story is different
> for VP9 and cannot store the metadata in the bit stream. HDR10+ should be
> passed to packet side data an stored in the container (mkv) for VP9.
>
> This CL is
Hi,
On Sun, Jun 13, 2021 at 12:46 PM Thilo Borgmann wrote:
>
> Hi,
>
> not sure about the spec backing this up, however the following site lists AV1
> support in WebM:
> https://developer.mozilla.org/en-US/docs/Web/Media/Formats/Video_codecs
>
This should probably get a version bump.
I think th
On Thu, Jun 17, 2021 at 10:21 PM Mohammad Izadi
wrote:
>
> HDR10+ metadata is stored in the bit stream for HEVC. The story is different
> for VP9 and cannot store the metadata in the bit stream. HDR10+ should be
> passed to packet side data an stored in the container (mkv) for VP9.
>
> This CL i
On Tue, Jun 22, 2021 at 1:46 PM James Zern wrote:
>
> On Thu, Jun 17, 2021 at 10:21 PM Mohammad Izadi
> wrote:
> >
> > HDR10+ metadata is stored in the bit stream for HEVC. The story is
> > different for VP9 and cannot store the metadata in the bit stream. HDR10+
>
On Wed, Dec 19, 2018 at 10:24 AM Rene Claus
wrote:
>
> This commit adds configuration options to libvpxenc.c that can be used to
> tune the sharpness parameter of the loop filter for VP8 and VP9.
>
> Signed-off-by: Rene Claus
> ---
> doc/encoders.texi | 4
> libavcodec/libvpxenc.c | 5
On Wed, Dec 19, 2018 at 2:03 PM James Almer wrote:
>
> On 12/19/2018 6:52 PM, Rene Claus wrote:
> > This commit adds configuration options to libvpxenc.c that can be used to
> > tune the sharpness parameter for VP8 and VP9.
> >
> > Signed-off-by: Rene Claus
> > ---
> > doc/encoders.texi | 4
On Thu, Dec 20, 2018 at 7:51 PM Rene Claus
wrote:
>
> This commit adds configuration options to libvpxenc.c that can be used to
> tune the sharpness parameter for VP8 and VP9.
>
> Signed-off-by: Rene Claus
> ---
> doc/encoders.texi | 4
> libavcodec/libvpxenc.c | 6 ++
> 2 files ch
On Fri, Dec 21, 2018 at 1:36 PM Rene Claus
wrote:
>
> This commit adds configuration options to libvpxenc.c that can be used to
> tune the sharpness parameter for VP8 and VP9.
>
> Signed-off-by: Rene Claus
> ---
> doc/encoders.texi | 4
> libavcodec/libvpxenc.c | 6 ++
> 2 files ch
On Fri, Dec 21, 2018 at 11:24 AM James Almer wrote:
>
> On 12/21/2018 1:09 PM, James Zern wrote:
> > On Thu, Dec 20, 2018 at 7:51 PM Rene Claus
> > wrote:
> >>
> >> This commit adds configuration options to libvpxenc.c that can be used to
> >>
On Fri, Dec 21, 2018 at 7:38 PM James Zern wrote:
>
> On Fri, Dec 21, 2018 at 1:36 PM Rene Claus
> wrote:
> >
> > This commit adds configuration options to libvpxenc.c that can be used to
> > tune the sharpness parameter for VP8 and VP9.
> >
> > Sign
On Sat, Feb 9, 2019 at 3:15 AM Carl Eugen Hoyos wrote:
>
> 2019-02-09 7:49 GMT+01:00, Gyan :
> >
> >
> > On 09-02-2019 02:26 AM, Carl Eugen Hoyos wrote:
> >> 2019-02-08 6:08 GMT+01:00, Gyan :
> >>>
> >>> On 08-02-2019 03:31 AM, Carl Eugen Hoyos wrote:
> .
> No strong opinion here, I hadn
> >
> > > +if (avctx->codec_id == AV_CODEC_ID_VP8)
> > > +vp8_encode_set_roi(avctx, frame);
> >
> > The API only exists for VP8, or is this due to different quant scales or
> > something?
>
> currently, VP9 ROI does not work, see my discussion at
> https://groups.google.com/a/w
On Fri, Mar 1, 2019 at 4:51 AM Derek Buitenhuis
wrote:
>
> On 01/03/2019 03:18, Guo, Yejun wrote:
> > yes, that's the reason I pending VP9 work. As for VP8 ROI, another thinking
> > is to first push vp8 roi, since libvpx is an external dependency and we
> > don't
> > know the time when it is avai
On Mon, Mar 4, 2019 at 6:19 AM Guo, Yejun wrote:
>
> Signed-off-by: Guo, Yejun
> ---
> configure | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
lgtm. This is a remnant from when vp8 was the only codec in the library.
___
ffmpeg-devel ma
On Thu, Feb 28, 2019 at 11:23 PM Guo, Yejun wrote:
>
> Signed-off-by: Guo, Yejun
> ---
> libavcodec/libvpxenc.c | 150
> +
> 1 file changed, 150 insertions(+)
>
> diff --git a/libavcodec/libvpxenc.c b/libavcodec/libvpxenc.c
> index c823b8a..fc9b1f
On Fri, Mar 8, 2019 at 5:07 AM Guo, Yejun wrote:
>
> Signed-off-by: Guo, Yejun
> ---
> libavcodec/libvpxenc.c | 150
> +
> 1 file changed, 150 insertions(+)
>
> [...]
> +active_map.active_map = av_malloc(active_map.rows * active_map.cols);
> +
On Tue, Apr 11, 2017 at 9:33 PM, Vignesh Venkatasubramanian
wrote:
> Add an option to webm_dash_manifest demuxer to specify a value for
> "bandwidth" field in the DASH manifest. The value is then used by
> the muxer. Fixes an existing FIXME in the code.
>
> Signed-off-by: Vignesh Venkatasubramania
this was added in 1.6.0
Signed-off-by: James Zern
---
doc/encoders.texi | 2 +-
libavcodec/libvpxenc.c | 3 ++-
2 files changed, 3 insertions(+), 2 deletions(-)
diff --git a/doc/encoders.texi b/doc/encoders.texi
index 594c612b5a..f8f187664c 100644
--- a/doc/encoders.texi
+++ b/doc
added in:
734d760e2f lavc/libvpxenc: add -row-mt option
Signed-off-by: James Zern
---
doc/encoders.texi | 2 ++
1 file changed, 2 insertions(+)
diff --git a/doc/encoders.texi b/doc/encoders.texi
index 594c612b5a..7f4754d160 100644
--- a/doc/encoders.texi
+++ b/doc/encoders.texi
@@ -1679,6
On Thu, Apr 13, 2017 at 6:20 PM, James Zern wrote:
> On Tue, Apr 11, 2017 at 9:33 PM, Vignesh Venkatasubramanian
> wrote:
>> Add an option to webm_dash_manifest demuxer to specify a value for
>> "bandwidth" field in the DASH manifest. The value is then used by
>
On Mon, Apr 17, 2017 at 5:06 PM, Michael Niedermayer
wrote:
> On Thu, Apr 13, 2017 at 06:53:26PM -0700, James Zern wrote:
>> added in:
>> 734d760e2f lavc/libvpxenc: add -row-mt option
>>
>> Signed-off-by: James Zern
>> ---
>> doc/encoders.texi | 2 ++
>&
On Thu, Apr 13, 2017 at 6:44 PM, James Zern wrote:
> this was added in 1.6.0
>
> Signed-off-by: James Zern
> ---
> doc/encoders.texi | 2 +-
> libavcodec/libvpxenc.c | 3 ++-
> 2 files changed, 3 insertions(+), 2 deletions(-)
>
I'll submit this soon
On Thu, Apr 20, 2017 at 1:42 PM, Ronald S. Bultje wrote:
> Hi,
>
> On Thu, Apr 20, 2017 at 2:42 PM, James Zern
> wrote:
>
>> On Thu, Apr 13, 2017 at 6:44 PM, James Zern wrote:
>> > this was added in 1.6.0
>> >
>> > Signed-off-by: James
On Thu, Apr 20, 2017 at 3:06 PM, James Zern wrote:
> On Thu, Apr 20, 2017 at 1:42 PM, Ronald S. Bultje wrote:
>> Hi,
>>
>> On Thu, Apr 20, 2017 at 2:42 PM, James Zern
>> wrote:
>>
>>> On Thu, Apr 13, 2017 at 6:44 PM, James Zern wrote:
>>>
On Thu, Jun 1, 2017 at 7:51 PM, James Almer wrote:
> WebM supports a subset of elements from the Chapters master.
> See https://www.webmproject.org/docs/container/#chapters
>
> Addresses ticket #6425
>
> Signed-off-by: James Almer
> ---
> libavformat/matroskaenc.c | 29 --
Signed-off-by: James Zern
---
doc/encoders.texi | 2 ++
libavcodec/libvpxenc.c | 20
2 files changed, 22 insertions(+)
diff --git a/doc/encoders.texi b/doc/encoders.texi
index 431777c457..23451b7b92 100644
--- a/doc/encoders.texi
+++ b/doc/encoders.texi
@@ -1681,6
On Mon, Nov 13, 2017 at 4:43 PM, James Almer wrote:
> On 11/13/2017 9:01 PM, James Zern wrote:
>> Signed-off-by: James Zern
>> ---
>> doc/encoders.texi | 2 ++
>> libavcodec/libvpxenc.c | 20
>> 2 files changed, 22 insertions(+)
>&
On Mon, Nov 13, 2017 at 6:05 PM, James Zern wrote:
> On Mon, Nov 13, 2017 at 4:43 PM, James Almer wrote:
>> On 11/13/2017 9:01 PM, James Zern wrote:
>>> Signed-off-by: James Zern
>>> ---
>>> doc/encoders.texi | 2 ++
>>> libavcodec/libvp
On Nov 14, 2017 18:53, "James Zern" wrote:
On Mon, Nov 13, 2017 at 6:05 PM, James Zern wrote:
> On Mon, Nov 13, 2017 at 4:43 PM, James Almer wrote:
>> On 11/13/2017 9:01 PM, James Zern wrote:
>>> Signed-off-by: James Zern
>>> ---
>>> doc/encoders
On Mon, Nov 13, 2017 at 4:01 PM, James Zern wrote:
> Signed-off-by: James Zern
> ---
> doc/encoders.texi | 2 ++
> libavcodec/libvpxenc.c | 20
> 2 files changed, 22 insertions(+)
>
Applied with an additional note in the commit message about the
Signed-off-by: James Zern
---
libavcodec/libvpx.c | 12 +---
1 file changed, 1 insertion(+), 11 deletions(-)
diff --git a/libavcodec/libvpx.c b/libavcodec/libvpx.c
index 1eca97a081..36f915a8e5 100644
--- a/libavcodec/libvpx.c
+++ b/libavcodec/libvpx.c
@@ -40,9 +40,7 @@ static const enum
Signed-off-by: James Zern
---
libavcodec/libvpxenc.c | 25 +++--
1 file changed, 3 insertions(+), 22 deletions(-)
diff --git a/libavcodec/libvpxenc.c b/libavcodec/libvpxenc.c
index fbb842499b..0258396d08 100644
--- a/libavcodec/libvpxenc.c
+++ b/libavcodec/libvpxenc.c
Signed-off-by: James Zern
---
libavcodec/libvpxdec.c | 25 -
1 file changed, 25 deletions(-)
diff --git a/libavcodec/libvpxdec.c b/libavcodec/libvpxdec.c
index ad0ea3b02a..2ae29d202a 100644
--- a/libavcodec/libvpxdec.c
+++ b/libavcodec/libvpxdec.c
@@ -70,7 +70,6
this will simplify libvpxenc/dec.c and ensure more stable versions of
the codecs are present.
Signed-off-by: James Zern
---
configure | 20 ++--
1 file changed, 10 insertions(+), 10 deletions(-)
diff --git a/configure b/configure
index c8e2e35192..bfb1d9ab3a 100755
--- a
On Sun, Nov 19, 2017 at 6:03 AM, James Almer wrote:
> On 11/17/2017 10:50 PM, James Zern wrote:
>> this will simplify libvpxenc/dec.c and ensure more stable versions of
>> the codecs are present.
>>
>> Signed-off-by: James Zern
>> ---
>> configure | 20
On Sun, Nov 19, 2017 at 5:57 AM, James Almer wrote:
> On 11/17/2017 10:50 PM, James Zern wrote:
>> Signed-off-by: James Zern
>> ---
>> libavcodec/libvpx.c | 12 +---
>> 1 file changed, 1 insertion(+), 11 deletions(-)
>>
>> diff --git a/libavcodec/
On Mon, Nov 20, 2017 at 11:17 AM, James Zern wrote:
> On Sun, Nov 19, 2017 at 6:03 AM, James Almer wrote:
>> On 11/17/2017 10:50 PM, James Zern wrote:
>>> this will simplify libvpxenc/dec.c and ensure more stable versions of
>>> the codecs are present.
>&g
On Mon, Nov 20, 2017 at 11:51 AM, James Almer wrote:
> On 11/20/2017 4:38 PM, James Zern wrote:
>> On Mon, Nov 20, 2017 at 11:17 AM, James Zern wrote:
>>> On Sun, Nov 19, 2017 at 6:03 AM, James Almer wrote:
>>>> On 11/17/2017 10:50 PM, James Zern wrote:
>>&g
On Fri, Nov 17, 2017 at 5:50 PM, James Zern wrote:
> Signed-off-by: James Zern
> ---
> libavcodec/libvpx.c | 12 +---
> 1 file changed, 1 insertion(+), 11 deletions(-)
>
applied.
___
ffmpeg-devel mailing list
ffmpeg-devel@
On Fri, Nov 17, 2017 at 5:50 PM, James Zern wrote:
> Signed-off-by: James Zern
> ---
> libavcodec/libvpxenc.c | 25 +++--
> 1 file changed, 3 insertions(+), 22 deletions(-)
>
applied.
___
ffmpeg-devel mailing li
On Fri, Nov 17, 2017 at 5:50 PM, James Zern wrote:
> Signed-off-by: James Zern
> ---
> libavcodec/libvpxdec.c | 25 -
> 1 file changed, 25 deletions(-)
>
applied.
___
ffmpeg-devel mailing list
ffmpeg-devel@
Corpus VBR mode is a variant of standard VBR where the complexity
distribution midpoint is passed in rather than calculated for a specific
clip or chunk.
The valid range is [0, 1]. 0 (default) uses standard VBR.
Signed-off-by: James Zern
---
doc/encoders.texi | 5 +
libavcodec
On Mon, Nov 20, 2017 at 5:36 PM, James Zern wrote:
> Corpus VBR mode is a variant of standard VBR where the complexity
> distribution midpoint is passed in rather than calculated for a specific
> clip or chunk.
>
> The valid range is [0, 1]. 0 (default) uses standard VBR.
&g
On Mon, Nov 27, 2017 at 10:55 AM, James Zern wrote:
> On Mon, Nov 20, 2017 at 5:36 PM, James Zern wrote:
>> Corpus VBR mode is a variant of standard VBR where the complexity
>> distribution midpoint is passed in rather than calculated for a specific
>> clip or chunk.
>&g
b6-.ivf
> Fixes: ducks_take_off_444_720p50.y4m.vp9.webm.ivf.s107375_r01-05_b6-.ivf
>
> Reported-by: James Zern
> Signed-off-by: Michael Niedermayer
> ---
> libavcodec/vp9.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
lgtm. t
On Wed, Oct 12, 2016 at 6:22 AM, Matthieu Bouron
wrote:
> From: Matthieu Bouron
>
> ---
> configure| 4 +++
> libavcodec/Makefile | 2 ++
> libavcodec/allcodecs.c | 4 +++
> libavcodec/mediacodecdec.c | 14
> libavcodec/mediacodec
since:
3e5e5bd Merge commit '398f015f077c6a2406deffd9e37ff34b9c7bb3bc'
Signed-off-by: James Zern
---
ffmpeg.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/ffmpeg.c b/ffmpeg.c
index 693981f..af8ed76 100644
--- a/ffmpeg.c
+++ b/ffmpeg.c
@@ -533,7 +533,7 @@ s
Ronald,
On Fri, Oct 14, 2016 at 10:01 AM, Ronald S. Bultje wrote:
> This is intended to workaround bug "665 Integer Divide Instruction May
> Cause Unpredictable Behavior" on some early AMD CPUs, which causes a
> div-by-zero in this codepath, such as reported in Mozilla bug #1293996.
>
> Note that
On Fri, Oct 14, 2016 at 11:31 AM, Michael Niedermayer
wrote:
> On Fri, Oct 14, 2016 at 08:29:37PM +0200, Michael Niedermayer wrote:
>> On Fri, Oct 14, 2016 at 11:09:30AM -0700, James Zern wrote:
>> > Ronald,
>> >
>> > On Fri, Oct 14, 2016 at 10:01 AM, Ronald S.
On Fri, Oct 14, 2016 at 11:54 AM, Ronald S. Bultje wrote:
> Hi Michael,
>
> On Fri, Oct 14, 2016 at 2:31 PM, Michael Niedermayer > wrote:
>
>> On Fri, Oct 14, 2016 at 08:29:37PM +0200, Michael Niedermayer wrote:
>> > On Fri, Oct 14, 2016 at 11:09:30AM -0700, J
On Thu, Oct 20, 2016 at 8:31 AM, Kagami Hiiragi wrote:
> vp9_cx_iface actually allows values in range [0..2].
> This fixes ticket #5894.
>
> Signed-off-by: Kagami Hiiragi
> ---
> libavcodec/libvpxenc.c | 7 ++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
This is all right in the sens
On Thu, Oct 20, 2016 at 11:51 AM, Rostislav Pehlivanov
wrote:
> On 20 October 2016 at 16:31, Kagami Hiiragi wrote:
>
>> vp9_cx_iface actually allows values in range [0..2].
>> This fixes ticket #5894.
>>
>> Signed-off-by: Kagami Hiiragi
>> ---
>> libavcodec/libvpxenc.c | 7 ++-
>> 1 file ch
On Fri, Oct 21, 2016 at 1:14 AM, Kagami Hiiragi wrote:
> On 21/10/16 06:14, James Zern wrote:
>> On Thu, Oct 20, 2016 at 8:31 AM, Kagami Hiiragi wrote:
>>> vp9_cx_iface actually allows values in range [0..2].
>>> This fixes ticket #5894.
>>&g
On Fri, Oct 21, 2016 at 1:22 AM, James Zern wrote:
> On Fri, Oct 21, 2016 at 1:14 AM, Kagami Hiiragi wrote:
>> On 21/10/16 06:14, James Zern wrote:
>>> On Thu, Oct 20, 2016 at 8:31 AM, Kagami Hiiragi
>>> wrote:
>>>> vp9_cx_iface actually allows values
On Fri, Oct 21, 2016 at 4:55 AM, Ronald S. Bultje wrote:
> Hi,
>
> On Thu, Oct 20, 2016 at 11:14 PM, James Zern > wrote:
>
>> On Thu, Oct 20, 2016 at 8:31 AM, Kagami Hiiragi
>> wrote:
>> > vp9_cx_iface actually allows values in range [0..2].
>> > Thi
From: Kagami Hiiragi
vp9_cx_iface actually allows values in range [0..2].
This fixes ticket #5894.
Signed-off-by: Kagami Hiiragi
---
libavcodec/libvpxenc.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/libavcodec/libvpxenc.c b/libavcodec/libvpxenc.c
index 2db87f7..68
On Fri, Oct 21, 2016 at 3:10 PM, Kagami Hiiragi wrote:
> On 22/10/16 01:06, James Zern wrote:
>> From: Kagami Hiiragi
>>
>> vp9_cx_iface actually allows values in range [0..2].
>> This fixes ticket #5894.
>>
>> Signed-off-by: Kagami Hiiragi
>> ---
&g
On Sat, Nov 5, 2016 at 1:50 PM, James Almer wrote:
> If the value is negative then it means padding at the start of the packet
> instead of at the end.
>
> Based on a patch by Hendrik Leppkes.
>
> Signed-off-by: James Almer
> ---
> libavformat/matroskadec.c | 12 +---
> 1 file changed, 9
On Fri, Nov 18, 2016 at 2:01 PM, Alex Converse wrote:
> Levels are specified at https://www.webmproject.org/vp9/levels/
> ---
> libavcodec/libvpxenc.c | 10 ++
> 1 file changed, 10 insertions(+)
>
lgtm
> diff --git a/libavcodec/libvpxenc.c b/libavcodec/libvpxenc.c
> index 68f25a4..51f42
On Fri, Nov 18, 2016 at 2:01 PM, Alex Converse wrote:
> Report the actual level of the encoded output if a level is
> targeted or the level is passively tracked with a target of 0.
> ---
> libavcodec/libvpxenc.c | 31 +++
> 1 file changed, 31 insertions(+)
>
lgtm.
I d
On Tue, Nov 22, 2016 at 12:04 PM, James Zern wrote:
> On Fri, Nov 18, 2016 at 2:01 PM, Alex Converse
> wrote:
>> Report the actual level of the encoded output if a level is
>> targeted or the level is passively tracked with a target of 0.
>> ---
>>
On Tue, Nov 22, 2016 at 12:08 PM, James Zern wrote:
> On Tue, Nov 22, 2016 at 12:04 PM, James Zern wrote:
>> On Fri, Nov 18, 2016 at 2:01 PM, Alex Converse
>> wrote:
>>> Report the actual level of the encoded output if a level is
>>> targeted or the level is p
On Mon, Nov 28, 2016 at 10:32 AM, Alex Converse wrote:
> On Tue, Nov 22, 2016 at 3:10 PM, James Zern wrote:
>> On Tue, Nov 22, 2016 at 12:08 PM, James Zern wrote:
>>> On Tue, Nov 22, 2016 at 12:04 PM, James Zern wrote:
>>>> On Fri, Nov 18, 2016 at 2:01
On Mon, Nov 28, 2016 at 10:34 AM, Alex Converse wrote:
> Report the actual level of the encoded output if a level is
> targeted or the level is passively tracked with a target of 0.
> ---
> libavcodec/libvpxenc.c | 32
> 1 file changed, 32 insertions(+)
>
lgtm
__
On Mon, Dec 12, 2016 at 12:12 PM, Alex Converse wrote:
> Fixes "Failed to set VP9E_GET_LEVEL codec control: Codec does not
> implement requested capability" log messages on VP8 encodes.
> ---
> libavcodec/libvpxenc.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
lgtm
__
On Tue, Jul 12, 2016 at 11:49 AM, Vignesh Venkatasubramanian
wrote:
>>> > Alright, i have a working patch for the decoder locally (i will push
>>> > that to the ML shortly).
>>>
>>> Here it is: http://ffmpeg.org/pipermail/ffmpeg-devel/2016-July/196403.html
>>
>>
>> Thanks, that resolves my concern
On Thu, Jun 30, 2016 at 4:16 PM, Vignesh Venkatasubramanian
wrote:
> Chrome canary now supports decoding of VP9 streams with alpha
> channel [1]. Add support to ffmpeg for creating such files.
>
> [1] https://codereview.chromium.org/2096813002/
>
> Signed-off-by: Vignesh Venkatasubramanian
> ---
On Tue, Jul 12, 2016 at 11:48 AM, Vignesh Venkatasubramanian
wrote:
> On Mon, Jul 11, 2016 at 5:55 PM, James Zern
> wrote:
>> On Thu, Jul 7, 2016 at 11:43 AM, Vignesh Venkatasubramanian
>> wrote:
>>
>>> [...]
>>> -av_image_copy(pictur
On Thu, Jul 14, 2016 at 12:15 PM, Vignesh Venkatasubramanian
wrote:
> +ret = vpx_init(
> +avctx,
> +(avctx->codec_id == AV_CODEC_ID_VP8) ?
> +&vpx_codec_vp8_dx_algo : &vpx_codec_vp9_dx_algo,
> +1);
101 - 200 of 426 matches
Mail list logo
