On Thu, 2018-05-03 at 11:07 +0800, Haihao Xiang wrote:
> Signed-off-by: Haihao Xiang
> ---
> libavcodec/vaapi_encode_h265.c | 29 -
> 1 file changed, 28 insertions(+), 1 deletion(-)
>
> diff --git a/libavcodec/vaapi_encode_h265.c b/libavcodec/vaapi_encode_h265.c
> ind
On 4/27/18 6:21 AM, Jan Ekström wrote:
> Personally I would be for removal of the WebM muxing feature in dashenc
> altogether, since the dashenc feature has never seemingly worked, and
> since there is a whole separate WebM-specific DASH meta muxer in
> webmdashenc.
>
> But these patches should a
We may check priv->sei_needed only when writing SEI messages.
Signed-off-by: Haihao Xiang
---
libavcodec/vaapi_encode_h264.c | 15 ---
1 file changed, 8 insertions(+), 7 deletions(-)
diff --git a/libavcodec/vaapi_encode_h264.c b/libavcodec/vaapi_encode_h264.c
index 56ad217b4a..905c5
On 5/1/2018 6:27 PM, Paul B Mahol wrote:
> Specifically for yuv444, yuv422, yuv420 format when main stream has no alpha,
> and alpha
> is straight.
>
> Signed-off-by: Paul B Mahol
> ---
> libavfilter/vf_overlay.c | 75 +---
> libavfilter/vf_overlay.h | 85 +++
On Mon, 2018-04-23 at 23:51 +0100, Mark Thompson wrote:
> On 23/04/18 08:08, Xiang, Haihao wrote:>> On 20/04/18 08:27, Haihao Xiang
> wrote:
> > > > '-sei xxx' is added to control SEI insertion, so far only mastering
> > > > display colour colume is available for testing. Another patch is
> > > > r
'-sei xxx' is added to control SEI insertion, so far only mastering
display colour colume is available for testing.
v2: use the mastering display parameters from
AVMasteringDisplayMetadata, set SEI_MASTERING_DISPLAY to 8 to match
the H.264 part and take VAAPIEncodeH265Context::sei_needed as a ORed
Signed-off-by: Haihao Xiang
---
libavcodec/vaapi_encode_h265.c | 29 -
1 file changed, 28 insertions(+), 1 deletion(-)
diff --git a/libavcodec/vaapi_encode_h265.c b/libavcodec/vaapi_encode_h265.c
index 326fe4fe66..5fe487dfc5 100644
--- a/libavcodec/vaapi_encode_h265.c
Similar to H264, cbs_h265_{read, write}_nal_unit() can handle HEVC
prefix SEI NAL units. Currently mastering display colour volume SEI
message is added only, we may add more SEI message if needed later
v2: Fix coding style and rebase the code
Signed-off-by: Haihao Xiang
---
libavcodec/cbs_h2645
Signed-off-by: Haihao Xiang
---
libavcodec/cbs_h2645.c| 1 +
libavcodec/cbs_h265.h | 6 ++
libavcodec/cbs_h265_syntax_template.c | 17 +
3 files changed, 24 insertions(+)
diff --git a/libavcodec/cbs_h2645.c b/libavcodec/cbs_h2645.c
index a4cc
From: Aman Gupta
The new logic follows a recommendation by @rcombs to use
dequeueInputBuffer with a timeout of 0 as a way to detect
whether the codec wants more data. The dequeued buffer index is
kept in MediaCodecDecContext until it can be used next.
A similar technique is also used by the Goog
From: Aman Gupta
---
libavcodec/mediacodec_wrapper.c | 15 +++
libavcodec/mediacodec_wrapper.h | 2 ++
2 files changed, 17 insertions(+)
diff --git a/libavcodec/mediacodec_wrapper.c b/libavcodec/mediacodec_wrapper.c
index 9bf96e9383..c47c2c9a41 100644
--- a/libavcodec/mediacodec_wr
From: Aman Gupta
The output_buffer_count==0 special case is no longer required, and
can cause spurious EAGAIN to surface to the user when input buffers
are filled up. Since the caller now knows if the decoder is accepting
new input (via current_input_buffer>=0), let the wait parameter
control whe
From: Aman Gupta
---
libavcodec/mediacodecdec.c | 22 +++---
1 file changed, 19 insertions(+), 3 deletions(-)
diff --git a/libavcodec/mediacodecdec.c b/libavcodec/mediacodecdec.c
index 2ac22dd1f6..3a4240aa95 100644
--- a/libavcodec/mediacodecdec.c
+++ b/libavcodec/mediacodecdec.
Le 03/05/2018 à 12:21 AM, Timo Rothenpieler a écrit :
Hi
thanks for your feedback.
I was not sure of whether to put the capability check with the others
in nvenc_check_capabilities because if the cap is missing this would
remove the encoder altogether:
ex: ln. 453 : if ((ret = nvenc_check
Le 03/05/2018 à 12:21 AM, Timo Rothenpieler a écrit :
Hi
thanks for your feedback.
I was not sure of whether to put the capability check with the others
in nvenc_check_capabilities because if the cap is missing this would
remove the encoder altogether:
ex: ln. 453 : if ((ret = nvenc_check
>
> About the past, it appears to me that there is a deeply rooted aversion by
> some people toward some code. This just doesnt belong here.
>
Correct, mpeg4video decoding is some of the least understandable and
undocumented code in the entirety of libavcodec.
Decoding spans the following files in
On Sun, Apr 29, 2018 at 11:24:19PM +, Kieran Kunhya wrote:
> On Sun, 29 Apr 2018 at 20:20 Michael Niedermayer
> wrote:
>
> > Signed-off-by: Michael Niedermayer
> > ---
> > libavcodec/mpeg4videodec.c | 4
> > 1 file changed, 4 deletions(-)
> >
> > diff --git a/libavcodec/mpeg4videodec.c
---
MAINTAINERS| 1 -
libavcodec/Makefile| 2 +-
libavcodec/libxvid_rc.c| 164 -
libavcodec/mpegvideo.h | 14 +---
libavcodec/mpegvideo_enc.c | 24 +-
5 files changed, 6 insertions(+), 199 deletions(-)
delete mode 10064
On 3 May 2018 at 00:10, Michael Niedermayer wrote:
> On Wed, May 02, 2018 at 10:23:08PM +0100, Rostislav Pehlivanov wrote:
> > On 2 May 2018 at 21:19, Carl Eugen Hoyos wrote:
> >
> > > 2018-05-02 5:35 GMT+02:00, Rostislav Pehlivanov :
> > > > On 1 May 2018 at 21:58, Carl Eugen Hoyos wrote:
> >
On Sun, Apr 29, 2018 at 09:19:15PM +0200, Michael Niedermayer wrote:
> Signed-off-by: Michael Niedermayer
> ---
> libavcodec/mpeg4videodec.c | 30 +-
> 1 file changed, 21 insertions(+), 9 deletions(-)
will apply
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6
On Wed, May 02, 2018 at 10:23:08PM +0100, Rostislav Pehlivanov wrote:
> On 2 May 2018 at 21:19, Carl Eugen Hoyos wrote:
>
> > 2018-05-02 5:35 GMT+02:00, Rostislav Pehlivanov :
> > > On 1 May 2018 at 21:58, Carl Eugen Hoyos wrote:
> > >
> > >> 2018-05-01 21:00 GMT+02:00, Rostislav Pehlivanov :
>
Hi
thanks for your feedback.
I was not sure of whether to put the capability check with the others in
nvenc_check_capabilities because if the cap is missing this would remove
the encoder altogether:
ex: ln. 453 : if ((ret = nvenc_check_capabilities(avctx)) < 0)
got
Le 03/05/2018 à 12:14 AM, Timo Rothenpieler a écrit :
Am 02.05.2018 um 23:58 schrieb Timo Rothenpieler:
Am 02.05.2018 um 23:18 schrieb pkv.stream:
Hello,
The patch enables dynamic bitrate through ReconfigureEncoder method
from nvenc API.
This is useful for live streaming in case of network c
Le 02/05/2018 à 11:58 PM, Timo Rothenpieler a écrit :
Am 02.05.2018 um 23:18 schrieb pkv.stream:
Hello,
The patch enables dynamic bitrate through ReconfigureEncoder method
from nvenc API.
This is useful for live streaming in case of network congestion.
A similar patch for changing aspect rat
Am 02.05.2018 um 23:58 schrieb Timo Rothenpieler:
Am 02.05.2018 um 23:18 schrieb pkv.stream:
Hello,
The patch enables dynamic bitrate through ReconfigureEncoder method
from nvenc API.
This is useful for live streaming in case of network congestion.
A similar patch for changing aspect ratio d
2018-05-02 23:50 GMT+02:00, Marton Balint :
>
> On Wed, 2 May 2018, Carl Eugen Hoyos wrote:
>
>> 2018-05-02 22:48 GMT+02:00, Marton Balint :
>>> Inspired by the VideoLAN text decoder and its port to
>>> FFmpeg made by Aman Gupta.
>>
>> While this may be great, I would still like to see the light-we
On Wed, 2 May 2018, Carl Eugen Hoyos wrote:
2018-05-02 22:48 GMT+02:00, Marton Balint :
Inspired by the VideoLAN text decoder and its port to
FFmpeg made by Aman Gupta.
While this may be great, I would still like to see the light-weight
decoder that does not depend on an external library in
Am 02.05.2018 um 23:18 schrieb pkv.stream:
Hello,
The patch enables dynamic bitrate through ReconfigureEncoder method from
nvenc API.
This is useful for live streaming in case of network congestion.
A similar patch for changing aspect ratio dynamically was previously
submitted by Miroslav Sl
2018-05-02 23:23 GMT+02:00, Rostislav Pehlivanov :
> On 2 May 2018 at 21:19, Carl Eugen Hoyos wrote:
>
>> 2018-05-02 5:35 GMT+02:00, Rostislav Pehlivanov :
>> > On 1 May 2018 at 21:58, Carl Eugen Hoyos wrote:
>> >
>> >> 2018-05-01 21:00 GMT+02:00, Rostislav Pehlivanov :
>> >> > Its a reminder of
2018-05-02 23:24 GMT+02:00, James Almer :
> On 5/2/2018 6:12 PM, Carl Eugen Hoyos wrote:
>> 2018-05-02 23:09 GMT+02:00, James Almer :
>>
>>> Which just made me realize we have been allowing the muxing of all kind
>>> of bullshit in AVI all this time and nobody bothered to prevent it.
>>
>> Yes, I d
On 5/2/2018 6:12 PM, Carl Eugen Hoyos wrote:
> 2018-05-02 23:09 GMT+02:00, James Almer :
>
>> Which just made me realize we have been allowing the muxing of all kind
>> of bullshit in AVI all this time and nobody bothered to prevent it.
>
> Yes, I did.
How did you try to prevent it? The fourccs
On 2 May 2018 at 21:19, Carl Eugen Hoyos wrote:
> 2018-05-02 5:35 GMT+02:00, Rostislav Pehlivanov :
> > On 1 May 2018 at 21:58, Carl Eugen Hoyos wrote:
> >
> >> 2018-05-01 21:00 GMT+02:00, Rostislav Pehlivanov :
> >> > Its a reminder of a bygone era. Less flexible than the internal RC
> >> > sys
Hello,
The patch enables dynamic bitrate through ReconfigureEncoder method from
nvenc API.
This is useful for live streaming in case of network congestion.
A similar patch for changing aspect ratio dynamically was previously
submitted by Miroslav Slugen:
https://patchwork.ffmpeg.org/patch/2
2018-05-02 22:48 GMT+02:00, Marton Balint :
> Inspired by the VideoLAN text decoder and its port to
> FFmpeg made by Aman Gupta.
While this may be great, I would still like to see the light-weight
decoder that does not depend on an external library in FFmpeg.
Does this patch implement auto-detect
2018-05-02 22:50 GMT+02:00, Hendrik Leppkes :
> If anything at all, this should most definitely not go into movvideo
> tags. This is about AVI files, so if it should go anywhere, it should
> be in ff_codec_bmp_tags. But of course this would have the side-effect
> that it actually allows encoding s
2018-05-02 23:09 GMT+02:00, James Almer :
> Which just made me realize we have been allowing the muxing of all kind
> of bullshit in AVI all this time and nobody bothered to prevent it.
Yes, I did.
(And thank you for accusing everybody.)
> Seriously, this is really sloppy. We're allowing VP9 and
On 5/2/2018 5:50 PM, Hendrik Leppkes wrote:
> On Wed, May 2, 2018 at 8:52 PM, James Almer wrote:
>> On 5/2/2018 3:44 PM, Carl Eugen Hoyos wrote:
>>> Hi!
>>>
>>> Attached patch fixes ticket #7110 for me.
>>
>> hevc in AVI is not a thing, and adding a non official fourcc to
>> ff_codec_movvideo_tags
2018-05-02 23:07 GMT+02:00, James Almer :
> On 5/2/2018 5:32 PM, Carl Eugen Hoyos wrote:
>> Are three enough?
>
> No.
Which other application do you know?
Carl Eugen
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listin
On 5/2/2018 5:32 PM, Carl Eugen Hoyos wrote:
> 2018-05-02 22:30 GMT+02:00, James Almer :
>> On 5/2/2018 4:47 PM, Carl Eugen Hoyos wrote:
>
I doubt we're the only ones that try to not write non standard files...
>>>
>>> Do you know immediately of another (general-usage!) tool?
>>
>> Why are yo
On Wed, May 2, 2018 at 8:52 PM, James Almer wrote:
> On 5/2/2018 3:44 PM, Carl Eugen Hoyos wrote:
>> Hi!
>>
>> Attached patch fixes ticket #7110 for me.
>
> hevc in AVI is not a thing, and adding a non official fourcc to
> ff_codec_movvideo_tags to support weird files created by faulty software
>
Inspired by the VideoLAN text decoder and its port to FFmpeg made by Aman
Gupta.
Signed-off-by: Marton Balint
---
doc/decoders.texi| 18 ++-
libavcodec/libzvbi-teletextdec.c | 265 +--
libavcodec/version.h | 2 +-
3 files changed
Most decoders (pgssubdec, ccaption_dec) are using -1 or UINT32_MAX for a
subtitle event which should be cleared at the next event.
Signed-off-by: Marton Balint
---
doc/decoders.texi| 3 ++-
libavcodec/libzvbi-teletextdec.c | 2 +-
2 files changed, 3 insertions(+), 2 deletions(-)
Signed-off-by: Marton Balint
---
libavcodec/libzvbi-teletextdec.c | 25 -
1 file changed, 25 deletions(-)
diff --git a/libavcodec/libzvbi-teletextdec.c b/libavcodec/libzvbi-teletextdec.c
index 44fca17b5d..a800ad34ae 100644
--- a/libavcodec/libzvbi-teletextdec.c
+++ b/liba
2018-05-02 22:30 GMT+02:00, James Almer :
> On 5/2/2018 4:47 PM, Carl Eugen Hoyos wrote:
>>> I doubt we're the only ones that try to not write non standard files...
>>
>> Do you know immediately of another (general-usage!) tool?
>
> Why are you asking me to list other software when you are the one
On 5/2/2018 4:47 PM, Carl Eugen Hoyos wrote:
> 2018-05-02 21:26 GMT+02:00, James Almer :
>> On 5/2/2018 3:59 PM, Carl Eugen Hoyos wrote:
>>> 2018-05-02 20:52 GMT+02:00, James Almer :
On 5/2/2018 3:44 PM, Carl Eugen Hoyos wrote:
>>>
> Attached patch fixes ticket #7110 for me.
hevc
2018-05-02 5:35 GMT+02:00, Rostislav Pehlivanov :
> On 1 May 2018 at 21:58, Carl Eugen Hoyos wrote:
>
>> 2018-05-01 21:00 GMT+02:00, Rostislav Pehlivanov :
>> > Its a reminder of a bygone era. Less flexible than the internal RC
>> > system, probably worse and most definitely broken. Drop it. No on
2018-05-02 22:01 GMT+02:00, Paul B Mahol :
> On 5/2/18, Carl Eugen Hoyos wrote:
>> Hi!
>>
>> Attached patch fixes ticket #7110 for me.
>>
>> Please comment, Carl Eugen
>>
>
> NACK.
Why did you ask for a sample if you were not interested
in fixing it?
Or do have a better idea?
Carl Eugen
On 5/2/18, Carl Eugen Hoyos wrote:
> Hi!
>
> Attached patch fixes ticket #7110 for me.
>
> Please comment, Carl Eugen
>
NACK.
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
On 2 May 2018 at 19:46, wm4 wrote:
> On Wed, 2 May 2018 19:37:27 +0100
> Rostislav Pehlivanov wrote:
>
> > On 2 May 2018 at 19:16, wm4 wrote:
> >
> > > On Wed, 2 May 2018 19:14:21 +0100
> > > Rostislav Pehlivanov wrote:
> > >
> > > > On 2 May 2018 at 19:04, Marton Balint wrote:
> > > >
> > >
2018-05-02 21:26 GMT+02:00, James Almer :
> On 5/2/2018 3:59 PM, Carl Eugen Hoyos wrote:
>> 2018-05-02 20:52 GMT+02:00, James Almer :
>>> On 5/2/2018 3:44 PM, Carl Eugen Hoyos wrote:
>>
Attached patch fixes ticket #7110 for me.
>>>
>>> hevc in AVI is not a thing, and adding a non official four
On 5/2/2018 3:59 PM, Carl Eugen Hoyos wrote:
> 2018-05-02 20:52 GMT+02:00, James Almer :
>> On 5/2/2018 3:44 PM, Carl Eugen Hoyos wrote:
>
>>> Attached patch fixes ticket #7110 for me.
>>
>> hevc in AVI is not a thing, and adding a non official fourcc to
>> ff_codec_movvideo_tags to support weird
2018-05-02 20:52 GMT+02:00, James Almer :
> On 5/2/2018 3:44 PM, Carl Eugen Hoyos wrote:
>> Attached patch fixes ticket #7110 for me.
>
> hevc in AVI is not a thing, and adding a non official fourcc to
> ff_codec_movvideo_tags to support weird files created by
> faulty software that are not even m
On 5/2/2018 3:44 PM, Carl Eugen Hoyos wrote:
> Hi!
>
> Attached patch fixes ticket #7110 for me.
hevc in AVI is not a thing, and adding a non official fourcc to
ff_codec_movvideo_tags to support weird files created by faulty software
that are not even mov/mp4 is not a good idea.
Why the hell is
On Wed, 2 May 2018 19:37:27 +0100
Rostislav Pehlivanov wrote:
> On 2 May 2018 at 19:16, wm4 wrote:
>
> > On Wed, 2 May 2018 19:14:21 +0100
> > Rostislav Pehlivanov wrote:
> >
> > > On 2 May 2018 at 19:04, Marton Balint wrote:
> > >
> > > >
> > > >
> > > > On Tue, 1 May 2018, Rostislav Peh
Hi!
Attached patch fixes ticket #7110 for me.
Please comment, Carl Eugen
From 281899c95c5b94242fa2bdbb4e830eecaef78f8d Mon Sep 17 00:00:00 2001
From: Carl Eugen Hoyos
Date: Wed, 2 May 2018 20:43:09 +0200
Subject: [PATCH] lavf/isom: Recognize fourcc HEVC.
Fixes ticket #7110.
---
libavformat/iso
On 2 May 2018 at 19:16, wm4 wrote:
> On Wed, 2 May 2018 19:14:21 +0100
> Rostislav Pehlivanov wrote:
>
> > On 2 May 2018 at 19:04, Marton Balint wrote:
> >
> > >
> > >
> > > On Tue, 1 May 2018, Rostislav Pehlivanov wrote:
> > >
> > > On 1 May 2018 at 23:22, Paul B Mahol wrote:
> > >>
> > >> On
On 2 May 2018 at 19:04, Marton Balint wrote:
>
>
> On Tue, 1 May 2018, Rostislav Pehlivanov wrote:
>
> On 1 May 2018 at 23:22, Paul B Mahol wrote:
>>
>> On 5/2/18, Michael Niedermayer wrote:
>>> > Hi
>>> >
>>> > On Tue, May 01, 2018 at 09:40:01PM +0200, Paul B Mahol wrote:
>>> >> Signed-off-by:
On Wed, 2 May 2018 19:14:21 +0100
Rostislav Pehlivanov wrote:
> On 2 May 2018 at 19:04, Marton Balint wrote:
>
> >
> >
> > On Tue, 1 May 2018, Rostislav Pehlivanov wrote:
> >
> > On 1 May 2018 at 23:22, Paul B Mahol wrote:
> >>
> >> On 5/2/18, Michael Niedermayer wrote:
> >>> > Hi
> >>> >
On Tue, 1 May 2018, Rostislav Pehlivanov wrote:
On 1 May 2018 at 23:22, Paul B Mahol wrote:
On 5/2/18, Michael Niedermayer wrote:
> Hi
>
> On Tue, May 01, 2018 at 09:40:01PM +0200, Paul B Mahol wrote:
>> Signed-off-by: Paul B Mahol
>> ---
>> libavcodec/mjpegenc.c | 5 -
>> libav
On Fri, Mar 16, 2018 at 11:14 AM, Carl Eugen Hoyos wrote:
> I meant:
> What happens if you concat all these files (with "cat") before
> feeding the resulting large file to ffmpeg?
>
> Carl Eugen
We'd love to get this HLS input working, any ideas on what this patch
would need for it to be applied?
On Wed, 2 May 2018 17:49:05 +0100
Rostislav Pehlivanov wrote:
> On 2 May 2018 at 17:39, wm4 wrote:
>
> > On Wed, 2 May 2018 13:44:48 +0200
> > Nicolas George wrote:
> >
> > > Vittorio Giovara (2018-05-01):
> > > > Well no, let's step back a little.
> > > >
> > > > First of all there is no
On 2 May 2018 at 17:39, wm4 wrote:
> On Wed, 2 May 2018 13:44:48 +0200
> Nicolas George wrote:
>
> > Vittorio Giovara (2018-05-01):
> > > Well no, let's step back a little.
> > >
> > > First of all there is no stigma about adding fields to AVCodecContext,
> > > in fact, the more, the merrier, ri
On Wed, 2 May 2018 13:44:48 +0200
Nicolas George wrote:
> Vittorio Giovara (2018-05-01):
> > Well no, let's step back a little.
> >
> > First of all there is no stigma about adding fields to AVCodecContext,
> > in fact, the more, the merrier, right?
> >
> > Secondly, there _is_ concern about ad
Good morning,
we are looking for an experienced developer in ffmpeg to help a Startup
operating in video sharing, building a transcoder. They use C for most of their
backend development. The project is relatively short (about a month) and
ideally based in Berlin but location can be discussed. P
Hi all,
So I’ve noticed that ffmpeg does not always properly follow the number we
specify for hls_time when generating hls content.
For example, if we have an MP4/AAC file at 44.1kHz sampling rate, we would
expect that specifying 9.75238095238095 (420 frames) would return a manifest
with the s
On 5/2/18, Nicolas George wrote:
> Paul B Mahol (2018-05-02):
>> Patches and actual proposals are better than agreeing of some written
>> text that glorifies status quo.
>
> Depends on the quality of the patches.
Depends on who sends patches and reviewer.
_
Paul B Mahol (2018-05-02):
> Patches and actual proposals are better than agreeing of some written
> text that glorifies status quo.
Depends on the quality of the patches.
--
Nicolas George
signature.asc
Description: Digital signature
___
ffmpeg-de
On 5/2/18, Paul B Mahol wrote:
> Signed-off-by: Paul B Mahol
> ---
> libavfilter/drawutils.c | 11 ---
> libavfilter/drawutils.h | 1 +
> libavutil/colorspace.h| 12
> tests/ref/fate/filter-pixfmts-pad | 10 +-
> 4 files changed, 26 i
Signed-off-by: Paul B Mahol
---
libavfilter/drawutils.c | 11 ---
libavfilter/drawutils.h | 1 +
libavutil/colorspace.h| 12
tests/ref/fate/filter-pixfmts-pad | 10 +-
4 files changed, 26 insertions(+), 8 deletions(-)
diff --git a/lib
On 5/2/18, Nicolas George wrote:
> Vittorio Giovara (2018-05-01):
>> Well no, let's step back a little.
>>
>> First of all there is no stigma about adding fields to AVCodecContext,
>> in fact, the more, the merrier, right?
>>
>> Secondly, there _is_ concern about adding a field to AVCodec (not avc
Vittorio Giovara (2018-05-01):
> Well no, let's step back a little.
>
> First of all there is no stigma about adding fields to AVCodecContext,
> in fact, the more, the merrier, right?
>
> Secondly, there _is_ concern about adding a field to AVCodec (not avctx),
> since is a delicate point of entr
On 9/11/16, Paul B Mahol wrote:
> On 9/10/16, Nicolas George wrote:
>> Le quartidi 24 fructidor, an CCXXIV, Paul B Mahol a ecrit :
>>> So everybody agrees, we should proceed.
>>
>> I am proceeding, but as you can see in the patch, there is still a fair
>> amount of work to be done. Still, people
On Wed, May 02, 2018 at 04:35:21 +0100, Rostislav Pehlivanov wrote:
> On 1 May 2018 at 21:58, Carl Eugen Hoyos wrote:
> > 2018-05-01 21:00 GMT+02:00, Rostislav Pehlivanov :
> > > ever used it either, except for mislead people.
> > Is the above part of the commit message?
> Yep, its part of the com
Option "4x(MFX_LOOKAHEAD_DS_4x)" is provided but can't be set due to
wrong maximum value.
Signed-off-by: Zhong Li
---
libavcodec/qsvenc_h264.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/libavcodec/qsvenc_h264.c b/libavcodec/qsvenc_h264.c
index 718bf9c..7aa65e9 100644
---
On 26.04.2018 16:06, Tobias Rapp wrote:
Fixes stream field order written by avformat_write_header when "top"
option is specified on the command-line.
Signed-off-by: Tobias Rapp
---
fftools/ffmpeg.c | 6 ++
1 file changed, 6 insertions(+)
[...]
Pushed, thanks to both of you for the rev
75 matches
Mail list logo
