On 10-02-2019 10:20 PM, Reto Kromer wrote:
Best regards, Reto
Pushed as 6174686bc346e24fd146a725a97d77e571ebf5b4
Thanks,
Gyan
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Add AV_NOPTS_VALUE check for AVFrame.pkt_dts to avoid print the
pkt_dts as negative number like:
"0,3616613, -9223372036854775808, 1001, 3110400, 0x75e37a65"
Signed-off-by: Jun Zhao
---
tests/api/api-h264-test.c | 10 +++---
1 files changed, 7 insertions(+), 3 deletions(-)
diff -
Mark Thompson:
> On 05/02/2019 20:08, Andreas Rheinhardt wrote:
>> Currently, a fragment's unit array is constantly reallocated during
>> splitting of a packet. This commit adds the ability to keep the unit
>> array by distinguishing between the number of allocated and the number
>> of valid units
---
libavcodec/libaribb24.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/libavcodec/libaribb24.c b/libavcodec/libaribb24.c
index 28f20ca767..3a59938451 100644
--- a/libavcodec/libaribb24.c
+++ b/libavcodec/libaribb24.c
@@ -249,11 +249,11 @@ static int libaribb24_h
Fixes some rather embarrassing mistakes that somehow passed my
eyes.
* Now catches if memory allocation has failed during bprint usage
by checking av_bprint_is_complete().
* Now catches if adding an ASS rectangle into an AVSubtitle failed.
* Returns AVERROR_INVALIDDATA if we get an invalid regio
---
libavcodec/libaribb24.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/libavcodec/libaribb24.c b/libavcodec/libaribb24.c
index d6cccd117b..43da2b675d 100644
--- a/libavcodec/libaribb24.c
+++ b/libavcodec/libaribb24.c
@@ -202,7 +202,7 @@ static int libaribb24_close(AVCodecC
---
libavcodec/libaribb24.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/libavcodec/libaribb24.c b/libavcodec/libaribb24.c
index 43da2b675d..28f20ca767 100644
--- a/libavcodec/libaribb24.c
+++ b/libavcodec/libaribb24.c
@@ -367,9 +367,9 @@ static void libaribb24_flush(AVC
On 10/02/2019 23:11, Andreas Rheinhardt wrote:
> Mark Thompson:
>> On 05/02/2019 20:08, Andreas Rheinhardt wrote:
>>> int ff_cbs_read_extradata(CodedBitstreamContext *ctx,
>>>CodedBitstreamFragment *frag,
>>> - const AVCodecParameters *par)
>>>
On Mon, Feb 11, 2019 at 1:01 AM Michael Niedermayer wrote:
>
> On Sun, Feb 03, 2019 at 09:38:40PM +0200, Jan Ekström wrote:
> > +#define RGB_TO_BGR(c) ((c & 0xff) << 16 | (c & 0xff00) | ((c >> 16) &
> > 0xff))
>
> c should be protected by a ()
>
First of all, thank you for the technical review.
On Sun, Feb 10, 2019 at 02:53:58PM +0800, Jun Zhao wrote:
> Add AV_NOPTS_VALUE check for AVFrame.pkt_dts to avoid print the
> pkt_dts as negative number like:
> "0,3616613, -9223372036854775808, 1001, 3110400, 0x75e37a65"
>
> Signed-off-by: Jun Zhao
> ---
> tests/api/api-h264-test.c |
Mark Thompson:
> On 05/02/2019 20:08, Andreas Rheinhardt wrote:
>> int ff_cbs_read_extradata(CodedBitstreamContext *ctx,
>>CodedBitstreamFragment *frag,
>> - const AVCodecParameters *par)
>> + const AVCodecParameters *pa
On 05/02/2019 20:08, Andreas Rheinhardt wrote:
> This commit changes various places that make use of cbs to keep the
> fragments' unit arrays instead of constantly reallocating them.
>
> The more units a packet is split into, the bigger the benefit.
> So MPEG-2 benefits the most; for a video comin
On Sun, Feb 03, 2019 at 09:38:40PM +0200, Jan Ekström wrote:
> * Outputs ASS lines with basic coloring and font scaling for each
> given region.
> * Sets the default style to the resolution of the subtitle plane
> (for example, 960x540 / 36pt font for profile A).
> * Has options to:
> * Disab
On 05/02/2019 20:08, Andreas Rheinhardt wrote:
> Up until now, a fragment that got reused was zeroed twice: Once during
> uninit and once during reading the next packet/extradata/buffer. The
> second zeroing has now been made optional.
>
> This is also in preparation of actually reusing a fragment
On 05/02/2019 20:08, Andreas Rheinhardt wrote:
> Currently, a fragment's unit array is constantly reallocated during
> splitting of a packet. This commit adds the ability to keep the unit
> array by distinguishing between the number of allocated and the number
> of valid units in the unit array.
>
On Thu, 31 Jan 2019 at 15:00, Tomas Härdin wrote:
>
> > 1. The entropy calculation in block_cmp() omits the score of histogram[0]
> > from the final sum.
> > It's tempting to do this to bias the scores in favour of 0-bytes, but in
> > reality, blocks with a majority of 0 (or any other byte) will
2019-02-10 23:04 GMT+01:00, Marton Balint :
>
>
> On Sun, 3 Feb 2019, Charles Liu wrote:
>
>> Binary searching would hang if the fragment items do NOT have timestamp
>> for the specified stream.
>>
>> For example, a fmp4 consists of separated 'moof' boxes for each track, and
>> separated 'sidx' for
On Sat, 9 Feb 2019, Marton Balint wrote:
On Sat, 9 Feb 2019, Carl Eugen Hoyos wrote:
2019-02-05 22:14 GMT+01:00, Marton Balint :
If we enable a component but a dependant library is disabled, then the
enabled
component gets silently disabled. Warning about disabled explicitly
enabled
co
On Sun, 3 Feb 2019, Charles Liu wrote:
Binary searching would hang if the fragment items do NOT have timestamp for the
specified stream.
For example, a fmp4 consists of separated 'moof' boxes for each track, and
separated 'sidx' for each segment, but no 'mfra' box.
Then every fragment item
On 2/10/2019 5:12 PM, James Almer wrote:
> If nb_bits is zero when reading an OBU, then it's not a bug in CBS but an
> invalid bitstream, and we should abort gracefully instead.
>
> Signed-off-by: James Almer
> ---
> rav1e is currently encoding invalid Metadata OBUs without trailing bits, which
>
If nb_bits is zero when reading an OBU, then it's not a bug in CBS but an
invalid bitstream, and we should abort gracefully instead.
Signed-off-by: James Almer
---
rav1e is currently encoding invalid Metadata OBUs without trailing bits, which
are triggering the assert when parsed by CBS. This cha
On 05/02/2019 16:51, Eoff, Ullysses A wrote:
>> -Original Message-
>> From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf Of
>> Mark Thompson
>> Sent: Monday, February 04, 2019 1:26 AM
>> To: ffmpeg-devel@ffmpeg.org
>> Subject: Re: [FFmpeg-devel] [PATCH v2 01/11] vaapi_en
We don't have anything useful to put in this field, but there is still
meant to be a marker bit in the middle of it.
---
libavcodec/vaapi_encode_mpeg2.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/libavcodec/vaapi_encode_mpeg2.c b/libavcodec/vaapi_encode_mpeg2.c
index 174
---
libavcodec/vaapi_encode_vp9.c | 30 +++---
1 file changed, 15 insertions(+), 15 deletions(-)
diff --git a/libavcodec/vaapi_encode_vp9.c b/libavcodec/vaapi_encode_vp9.c
index 8fb399f115..f89fd0d07a 100644
--- a/libavcodec/vaapi_encode_vp9.c
+++ b/libavcodec/vaapi_encode
---
libavcodec/vaapi_encode_mpeg2.c | 24 +---
1 file changed, 13 insertions(+), 11 deletions(-)
diff --git a/libavcodec/vaapi_encode_mpeg2.c b/libavcodec/vaapi_encode_mpeg2.c
index 9d42c3e644..174611ff24 100644
--- a/libavcodec/vaapi_encode_mpeg2.c
+++ b/libavcodec/vaapi_enco
---
libavcodec/vaapi_encode_vp9.c | 17 +
1 file changed, 13 insertions(+), 4 deletions(-)
diff --git a/libavcodec/vaapi_encode_vp9.c b/libavcodec/vaapi_encode_vp9.c
index 97142dcc49..8fb399f115 100644
--- a/libavcodec/vaapi_encode_vp9.c
+++ b/libavcodec/vaapi_encode_vp9.c
@@ -178
---
doc/encoders.texi | 4 +++
libavcodec/vaapi_encode.c | 57 ---
libavcodec/vaapi_encode.h | 9 ++-
3 files changed, 65 insertions(+), 5 deletions(-)
diff --git a/doc/encoders.texi b/doc/encoders.texi
index 39b8fc1d37..21b6d147fe 100644
--- a/do
Doesn't change anything, but makes the behaviour better match that of the
other codecs (the CONSTANT_QUALITY_ONLY flag already ensures that CQP is
the only RC mode selectable for MJPEG).
---
libavcodec/vaapi_encode_mjpeg.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/li
---
libavcodec/vaapi_encode_vp8.c | 16 ++--
1 file changed, 10 insertions(+), 6 deletions(-)
diff --git a/libavcodec/vaapi_encode_vp8.c b/libavcodec/vaapi_encode_vp8.c
index 166636cd84..ddbe4c9075 100644
--- a/libavcodec/vaapi_encode_vp8.c
+++ b/libavcodec/vaapi_encode_vp8.c
@@ -161,
Always write it as a RawData block, even if there is no SEI as well.
---
libavcodec/vaapi_encode_h264.c | 40 +++---
1 file changed, 17 insertions(+), 23 deletions(-)
diff --git a/libavcodec/vaapi_encode_h264.c b/libavcodec/vaapi_encode_h264.c
index fb55eb7779..b65ee4b
Also fixes QP going out of range when modified by the quant factor/offset
values, and clarifies the QP behaviour for >8-bit modes.
---
libavcodec/vaapi_encode_h265.c | 32
1 file changed, 20 insertions(+), 12 deletions(-)
diff --git a/libavcodec/vaapi_encode_h265.
Use the frame-skip feature to maintain a specified framerate from the
point of view of the driver.
---
"max_fps" collides with an option used in lavf, so renamed to "vfr_max_fps"
here. (That hopefully also makes it clearer what the use of the option is.)
doc/encoders.texi | 7 +++
li
Allow setting the mode explicitly, and try to make a sensible choice
given the available parameters if not.
---
doc/encoders.texi | 24 +++
libavcodec/vaapi_encode.c | 382 +++---
libavcodec/vaapi_encode.h | 65 +++
3 files changed, 358 insertions(+),
Also fixes QP going out of range when modified by the quant factor/offset
values.
---
libavcodec/vaapi_encode_h264.c | 31 +++
1 file changed, 19 insertions(+), 12 deletions(-)
diff --git a/libavcodec/vaapi_encode_h264.c b/libavcodec/vaapi_encode_h264.c
index 4ea62d96f
On 2/10/19, Thilo Borgmann wrote:
> Am 10.02.19 um 20:09 schrieb Paul B Mahol:
>> On 2/10/19, Thilo Borgmann wrote:
>>> Am 10.02.19 um 19:58 schrieb Paul B Mahol:
On 2/10/19, Thilo Borgmann wrote:
> Hi,
>
>> I'm requesting the reimbursement of travel expenses for the Google
On 10/02/2019 18:49, Carl Eugen Hoyos wrote:
> 2019-02-10 19:21 GMT+01:00, Mark Thompson :
>> On 05/02/2019 13:27, Carl Eugen Hoyos wrote:
>>> 2019-01-28 0:47 GMT+01:00, Mark Thompson :
>>>
+if (avctx->color_range == AVCOL_RANGE_MPEG) {
+av_log(avctx, AV_LOG_WARNING, "Input vi
On 2/10/19, Thilo Borgmann wrote:
> Am 10.02.19 um 19:58 schrieb Paul B Mahol:
>> On 2/10/19, Thilo Borgmann wrote:
>>> Hi,
>>>
I'm requesting the reimbursement of travel expenses for the Google
Mentor Summit.
...
>>>
>>> a little late, however I'd also like to request reimbursemen
Am 10.02.19 um 20:09 schrieb Paul B Mahol:
> On 2/10/19, Thilo Borgmann wrote:
>> Am 10.02.19 um 19:58 schrieb Paul B Mahol:
>>> On 2/10/19, Thilo Borgmann wrote:
Hi,
> I'm requesting the reimbursement of travel expenses for the Google
> Mentor Summit.
> ...
a litt
Am 10.02.19 um 19:58 schrieb Paul B Mahol:
> On 2/10/19, Thilo Borgmann wrote:
>> Hi,
>>
>>> I'm requesting the reimbursement of travel expenses for the Google
>>> Mentor Summit.
>>> ...
>>
>> a little late, however I'd also like to request reimbursement for my travel
>> there last October [1].
>>
On 2/10/19, Thilo Borgmann wrote:
> Hi,
>
>> I'm requesting the reimbursement of travel expenses for the Google
>> Mentor Summit.
>> ...
>
> a little late, however I'd also like to request reimbursement for my travel
> there last October [1].
>
> Total cost of my flight: 1348.33€
Have picture of
2019-02-10 13:06 GMT+01:00, Kieran O Leary :
> On Sat, 9 Feb 2019, 06:49 Gyan > although the `-lossless 1` encoding does return as lossless in SSIM.
>
> What ssim command did you use, and why use this over a hash muxer like
> framehash? I'm always on the lookout for losslessness verification method
2019-02-10 5:44 GMT+01:00, Gyan :
>
>
> On 09-02-2019 04:45 PM, 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
Hi,
I'd like to request reimbursement for my travel to the LDP [1].
Accomodation was sponsored by the LDP team, so travel costs are rather low:
21.90€
Will send the paperwork to Stefano.
Thanks,
Thilo
[1] https://lists.ffmpeg.org/pipermail/ffmpeg-devel/2018-October/235352.html
__
Hi,
> I'm requesting the reimbursement of travel expenses for the Google
> Mentor Summit.
> ...
a little late, however I'd also like to request reimbursement for my travel
there last October [1].
Total cost of my flight: 1348.33€
Will send the paperworks to Stefano as usual.
Thanks,
Thilo
[
2019-02-10 19:21 GMT+01:00, Mark Thompson :
> On 05/02/2019 13:27, Carl Eugen Hoyos wrote:
>> 2019-01-28 0:47 GMT+01:00, Mark Thompson :
>>
>>> +if (avctx->color_range == AVCOL_RANGE_MPEG) {
>>> +av_log(avctx, AV_LOG_WARNING, "Input video does not appear "
>>> + "to use fu
On Sun, 10 Feb 2019, at 19:37, Werner Robitza wrote:
> > Those options are just for non-free cases, and to be honest, I don't see
> > why FFmpeg should advertise those.
>
> That is not correct. The following options/dependencies are not
> present in Homebrew core:
>
> chromaprint, fdk-aac, game-
On Sat, Feb 9, 2019 at 11:59 PM Jean-Baptiste Kempf wrote:
>
> On Sat, 9 Feb 2019, at 11:59, Werner Robitza wrote:
> > Then the only consequence can be to remove these options or support
> > for these libraries altogether, because you'll find plenty of guides
> > and recommendations on how to buil
On 04/02/2019 14:41, Michael Dirks wrote:
> On 04.02.2019 11:05, Mark Thompson wrote:
>> Can you explain what this "skip frame" actually does in the encoder? The
>> concept does not exist in H.264 or H.265, as far as I know.
>
> I believe this has to do with the pic_struct flag which has a value
On 10-02-2019 05:36 PM, Kieran O Leary wrote:
What ssim command did you use, and why use this over a hash muxer like
framehash? I'm always on the lookout for losslessness verification methods.
The barebones command:
ffmpeg -i main -i ref -lavfi ssim -f null -
framehash will be sensitiv
On 05/02/2019 13:27, Carl Eugen Hoyos wrote:
> 2019-01-28 0:47 GMT+01:00, Mark Thompson :
>
>> +if (avctx->color_range == AVCOL_RANGE_MPEG) {
>> +av_log(avctx, AV_LOG_WARNING, "Input video does not appear "
>> + "to use full-range: output colours may be incorrect.\n");
>
On 05/02/2019 13:25, Carl Eugen Hoyos wrote:
> 2019-01-28 0:47 GMT+01:00, Mark Thompson :
>> ---
>> libavcodec/vaapi_encode_vp9.c | 41 +--
>> 1 file changed, 25 insertions(+), 16 deletions(-)
>>
>> diff --git a/libavcodec/vaapi_encode_vp9.c b/libavcodec/vaapi_encod
On 10-02-2019 11:31 PM, Carl Eugen Hoyos wrote:
2019-02-10 18:44 GMT+01:00, Michael Niedermayer :
On Sat, Feb 09, 2019 at 01:58:06PM +0100, Carl Eugen Hoyos wrote:
Hi!
Currently if the "loop" option gets specified for -f image2pipe, there is
no indication for the user that the option will no
2019-02-10 18:44 GMT+01:00, Michael Niedermayer :
> On Sat, Feb 09, 2019 at 01:58:06PM +0100, Carl Eugen Hoyos wrote:
>> Hi!
>>
>> Currently if the "loop" option gets specified for -f image2pipe, there is
>> no indication for the user that the option will not work, patch attached.
>>
>> Please comm
On Sat, Feb 09, 2019 at 01:58:06PM +0100, Carl Eugen Hoyos wrote:
> Hi!
>
> Currently if the "loop" option gets specified for -f image2pipe, there is
> no indication for the user that the option will not work, patch attached.
>
> Please comment, Carl Eugen
> img2dec.c | 33 +++
2019-02-10 1:55 GMT+01:00, Jan Ekström :
> On Sat, Feb 9, 2019 at 2:58 PM Carl Eugen Hoyos wrote:
>>
>> Hi!
>>
>> Currently if the "loop" option gets specified for -f image2pipe, there is
>> no indication for the user that the option will not work, patch attached.
>>
>> Please comment, Carl Eugen
Best regards, Reto
0001-doc-faq-update-macOS-and-URLs.patch
Description: Binary data
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
lör 2019-02-09 klockan 13:10 + skrev Matthew Fearnley:
> - Clamp ME range to -64..63 (prevents corruption when me_range is too high)
> - Allow MV's up to *and including* the positive range limit
> - Allow out-of-edge ME by padding the prev buffer with a border of 0's
> - Try previous MV before
2019-02-10 13:32 GMT+01:00, Reto Kromer :
> Best regards, Reto
Patch applied.
Thank you, Carl Eugen
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
On 10-02-2019 04:41 PM, Moritz Barsnick wrote:
On Sun, Feb 10, 2019 at 12:20:38 +0530, Gyan wrote:
On 10-02-2019 11:37 AM, Reto Kromer wrote:
Should fix a few nits in man. Best regards, Reto
Removed trailing whitespace from patch and pushed as
d20902fd2399ae04cbd5c02e83fbd90c68592555 with a
lör 2019-02-09 klockan 13:10 + skrev Matthew Fearnley:
> - Improve block choices by counting 0-bytes in the entropy score
> - Make histogram use uint16_t type, to allow byte counts from 16*16
> (current block size) up to 255*255 (maximum allowed 8bpp block size)
> - Make sure score table is big
Best regards, Reto
0001-doc-snow-fix-typos.patch
Description: Binary data
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
On Sat, 9 Feb 2019, 06:49 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't realized that -crf 0 only works with
> >>> newer versions.
> >>>
> >>> C
On Sun, 10 Feb 2019, 11:57 Martin Vignali Hello,
>
> >
> > > Use +ildct flag to switch between progressive and interlace encoding
> > >
> > > Use AVFrame flag to switch between tff and bff frame organization.
> > >
> >
> > Is this what you mean by altering the -setparams filter?
> >
> > In order t
Hello,
>
> > Use +ildct flag to switch between progressive and interlace encoding
> >
> > Use AVFrame flag to switch between tff and bff frame organization.
> >
>
> Is this what you mean by altering the -setparams filter?
>
> In order to choose between top field first and bottom field first, i use
On Sun, Feb 10, 2019 at 12:20:38 +0530, Gyan wrote:
> On 10-02-2019 11:37 AM, Reto Kromer wrote:
> > Should fix a few nits in man. Best regards, Reto
>
> Removed trailing whitespace from patch and pushed as
> d20902fd2399ae04cbd5c02e83fbd90c68592555 with a couple of corrections added.
Hmm, these
Found with the help of codespell-1.14.0.
Signed-off-by: Moritz Barsnick
---
doc/bitstream_filters.texi | 2 +-
doc/codecs.texi| 2 +-
doc/filters.texi | 16
doc/formats.texi | 2 +-
doc/general.texi | 8
doc/muxers.texi
Hi,
On Sat, Feb 9, 2019 at 6:10 PM Martin Vignali
wrote:
> Hello,
>
> Patchs in attach add interlace encoding support to prores aw encoding
>
Thanks so much for adding this. I can really only judge by the metadata for
now, but this all looks good to me (ffmpeg encode and mediainfo check):
$ ./
67 matches
Mail list logo
