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 | 12 +---
1 files changed, 9 insertions(+), 3 deletions(-)
Fix build warning like "warning: ISO C90 forbids mixed declarations
and code" after adjust the location for malloc fail check.
Signed-off-by: Jun Zhao
---
libavfilter/tests/integral.c |9 +
1 files changed, 5 insertions(+), 4 deletions(-)
diff --git a/libavfilter/tests/integral.c
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.
Thanks,
Gyan
___
> On Feb 10, 2019, at 12:45, Gyan wrote:
>
>
>
> On 19-01-2019 12:33 PM, Steven Liu wrote:
>> when set option fmp4_init_filename to init_%v.mp4
>> before patch:
>> the init file will be init_%v_0.mp4, init_%v_1.mp4
>> after patch:
>> the init file will be init_0.mp4, init_1.mp4
>>
>>
Should fix a few nits in man. Best regards, Reto
0001-doc-filters-fix-typos.patch
Description: Binary data
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Need to check malloc fail before using it, so adjust the location
in the code.
Signed-off-by: Jun Zhao
---
libavfilter/tests/integral.c |6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/libavfilter/tests/integral.c b/libavfilter/tests/integral.c
index
From: mptcultist
fixed issue where if sidx was after another sidx and happened to point to the
same media, it wouldn't be read.
this is done by counting the sidx atoms before they're read. for #7572
---
libavformat/isom.h | 2 ++
libavformat/mov.c | 45
On 19-01-2019 12:33 PM, Steven Liu wrote:
when set option fmp4_init_filename to init_%v.mp4
before patch:
the init file will be init_%v_0.mp4, init_%v_1.mp4
after patch:
the init file will be init_0.mp4, init_1.mp4
Reported-By: Gyan Doshi
Signed-off-by: Steven Liu
---
libavformat/hlsenc.c
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 opinion here, I hadn't realized that -crf 0 only works with
newer
On Fri, Feb 8, 2019 at 2:38 AM Jan Ekström wrote:
>
> On Sat, Feb 2, 2019 at 3:31 PM Jan Ekström wrote:
> >
> > A decoder wrapper for the libaribb24 library found in various
> > distributions and currently utilized by VLC.
> >
> > Requires GPLv3 with the current most recent release, but as the
>
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
Seems like a good idea.
The reason for the pipe
Hi!
Attached patch simplifies the debugging of icy metadata, required to
answer the tickets of one regular reporter.
Please comment, Carl Eugen
From 170f6bcf79b4486adf1121f7e5f01b6617fd1e79 Mon Sep 17 00:00:00 2001
From: Carl Eugen Hoyos
Date: Sun, 10 Feb 2019 00:59:30 +0100
Subject: [PATCH]
2019-02-10 0:23 GMT+01:00, Marton Balint :
>
> On Sat, 9 Feb 2019, Carl Eugen Hoyos wrote:
>
>> 2019-02-09 23:14 GMT+01:00, Marton Balint :
>>> Instead of ISO-10646 you probably should use UCS-2BE, VLC
>>> is also doing this and the specs refer to the basic multilingual
>>> plane. ISO-10646 alone
On Sat, 9 Feb 2019, Carl Eugen Hoyos wrote:
2019-02-09 23:14 GMT+01:00, Marton Balint :
On Sat, 9 Feb 2019, Carl Eugen Hoyos wrote:
+#if CONFIG_ICONV
+if (len && *p < 0x20) {
+const char *encodings[] = {
+"ISO6937", "ISO-8859-5", "ISO-8859-6", "ISO-8859-7",
Simplifies code.
Signed-off-by: James Almer
---
libavformat/mov.c | 21 -
1 file changed, 8 insertions(+), 13 deletions(-)
diff --git a/libavformat/mov.c b/libavformat/mov.c
index 9b9739f788..986c54e74e 100644
--- a/libavformat/mov.c
+++ b/libavformat/mov.c
@@ -5268,9
On Sat, Feb 9, 2019 at 7:39 PM Carl Eugen Hoyos wrote:
>
> 2019-02-09 17:42 GMT+01:00, Marton Balint :
> > On Sat, 9 Feb 2019, Carl Eugen Hoyos wrote:
> >
> >> From 9033f0a18727a7a576c4cc06b9985d6d922d46ad Mon Sep 17 00:00:00 2001
> >> From: Carl Eugen Hoyos
> >> Date: Sat, 9 Feb 2019 00:49:51
On Sat, 9 Feb 2019, at 11:59, Werner Robitza wrote:
> You could print an even more obvious warning message when these
> options are used.
> If that is a big concern, it can be easily dealt with.
>
> > And yes, I strongly advise against the project advertising those non-free
> > options.
>
>
2019-02-09 23:14 GMT+01:00, Marton Balint :
>
>
> On Sat, 9 Feb 2019, Carl Eugen Hoyos wrote:
>
> +#if CONFIG_ICONV
> +if (len && *p < 0x20) {
>> +const char *encodings[] = {
>> +"ISO6937", "ISO-8859-5", "ISO-8859-6", "ISO-8859-7",
>> "ISO-8859-8",
>> +
2019-02-09 23:26 GMT+01:00, Carl Eugen Hoyos :
> Hi!
>
> Attached patch constifies a few pointers at the next version bump.
And the patch.
Carl Eugen
From cb2afc8b7e28b476d908daf1ae693bd007fb2abc Mon Sep 17 00:00:00 2001
From: Carl Eugen Hoyos
Date: Sat, 9 Feb 2019 23:22:59 +0100
Subject:
Hi!
Attached patch constifies a few pointers at the next version bump.
Please comment, Carl Eugen
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
On Sat, 9 Feb 2019, Carl Eugen Hoyos wrote:
+#if CONFIG_ICONV
+if (len && *p < 0x20) {
+const char *encodings[] = {
+"ISO6937", "ISO-8859-5", "ISO-8859-6", "ISO-8859-7", "ISO-8859-8",
+"ISO-8859-9", "ISO-8859-10", "ISO-8859-11", "", "ISO-8859-13",
+
On 2/9/19, Carl Eugen Hoyos wrote:
> 2019-01-30 14:47 GMT+01:00, Carl Eugen Hoyos :
>> 2019-01-29 22:47 GMT+01:00, Carl Eugen Hoyos :
>>> Hi!
>>>
>>> Attached patch fixes decoding NO_DATA amr-wb frames.
>>
>> Now with patch.
>
> Ping.
>
> This patch is supposed to fix the duration of files with
2019-01-30 14:47 GMT+01:00, Carl Eugen Hoyos :
> 2019-01-29 22:47 GMT+01:00, Carl Eugen Hoyos :
>> Hi!
>>
>> Attached patch fixes decoding NO_DATA amr-wb frames.
>
> Now with patch.
Ping.
This patch is supposed to fix the duration of files with NO_DATA
frames.
Carl Eugen
2019-02-09 19:25 GMT+01:00, Reto Kromer :
> The attached patch should fix nits in the doc.
Patch applied.
Thank you, Carl Eugen
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Hello,
Patchs in attach add interlace encoding support to prores aw encoding
Use +ildct flag to switch between progressive and interlace encoding
Use AVFrame flag to switch between tff and bff frame organization.
If AVFrame->interlaced value is not set to 1, but +ildct is set (interlace
2019-02-09 17:42 GMT+01:00, Marton Balint :
> On Sat, 9 Feb 2019, Carl Eugen Hoyos wrote:
>
>> From 9033f0a18727a7a576c4cc06b9985d6d922d46ad Mon Sep 17 00:00:00 2001
>> From: Carl Eugen Hoyos
>> Date: Sat, 9 Feb 2019 00:49:51 +0100
>> Subject: [PATCH] lavf/mpegts: Convert service_name and
On Sat, 9 Feb 2019, Carl Eugen Hoyos wrote:
From 9033f0a18727a7a576c4cc06b9985d6d922d46ad Mon Sep 17 00:00:00 2001
From: Carl Eugen Hoyos
Date: Sat, 9 Feb 2019 00:49:51 +0100
Subject: [PATCH] lavf/mpegts: Convert service_name and service_provider to
utf-8.
Fixes ticket #6320.
---
2019-02-09 16:46 GMT+01:00, Wang Bin :
>>
>> 2019-02-05 0:59 GMT+01:00, James Almer :
>> > On 1/31/2019 4:23 PM, Carl Eugen Hoyos wrote:
>> >> 2019-01-31 17:04 GMT+01:00, Magnus Röös :
>> >>> Partial port of the ARM Neon for aarch64.
>> >>
>> >> Reproduced a >20% speedup for fate-vp8 and applied.
>
> 2019-02-05 0:59 GMT+01:00, James Almer :
> > On 1/31/2019 4:23 PM, Carl Eugen Hoyos wrote:
> >> 2019-01-31 17:04 GMT+01:00, Magnus Röös :
> >>> Partial port of the ARM Neon for aarch64.
> >>
> >> Reproduced a >20% speedup for fate-vp8 and applied.
> >>
> >> Thank you, Carl Eugen
> >
> > This
2019-02-09 14:37 GMT+01:00, Carl Eugen Hoyos :
> 2019-02-01 1:13 GMT+01:00, Michael Niedermayer :
>> On Thu, Jan 31, 2019 at 09:54:14PM +0100, Carl Eugen Hoyos wrote:
>>> 2019-01-31 21:43 GMT+01:00, Carl Eugen Hoyos :
>>> > Hi!
>>> >
>>> > Attached patch persistently uses "const" for AVInputFormat
2019-02-09 15:44 GMT+01:00, Carl Eugen Hoyos :
> 2019-02-09 15:42 GMT+01:00, James Almer :
>> On 2/9/2019 11:23 AM, Carl Eugen Hoyos wrote:
>>> Hi!
>>>
>>> Attached patch is supposed to constify all occurrences of
>>> AVOutputFormat in libavformat.
>>>
>>> Please comment, Carl Eugen
>>>
>>>
>>>
2019-02-09 15:42 GMT+01:00, James Almer :
> On 2/9/2019 11:23 AM, Carl Eugen Hoyos wrote:
>> Hi!
>>
>> Attached patch is supposed to constify all occurrences of
>> AVOutputFormat in libavformat.
>>
>> Please comment, Carl Eugen
>>
>>
>> 0001-lavf-Constify-AVOutputFormat-pointer.patch
>>
>> From
On 2/9/2019 11:23 AM, Carl Eugen Hoyos wrote:
> Hi!
>
> Attached patch is supposed to constify all occurrences of
> AVOutputFormat in libavformat.
>
> Please comment, Carl Eugen
>
>
> 0001-lavf-Constify-AVOutputFormat-pointer.patch
>
> From ba32f41824df07b7a6cb45964ef912c5fc05b276 Mon Sep 17
Hi!
Attached patch is supposed to constify all occurrences of
AVOutputFormat in libavformat.
Please comment, Carl Eugen
From ba32f41824df07b7a6cb45964ef912c5fc05b276 Mon Sep 17 00:00:00 2001
From: Carl Eugen Hoyos
Date: Sat, 9 Feb 2019 15:21:17 +0100
Subject: [PATCH] lavf: Constify
On Wed, Feb 06, 2019 at 08:23:15PM +0100, Carl Eugen Hoyos wrote:
> 2019-02-06 20:17 GMT+01:00, Michael Niedermayer :
> > On Wed, Feb 06, 2019 at 01:57:37PM +0100, Carl Eugen Hoyos wrote:
> >> 2019-02-03 18:21 GMT+01:00, Michael Niedermayer :
> >> > Fixes:
2019-02-01 1:13 GMT+01:00, Michael Niedermayer :
> On Thu, Jan 31, 2019 at 09:54:14PM +0100, Carl Eugen Hoyos wrote:
>> 2019-01-31 21:43 GMT+01:00, Carl Eugen Hoyos :
>> > Hi!
>> >
>> > Attached patch persistently uses "const" for AVInputFormat pointer
>> > after the next version bump.
>>
>> Now
- 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 enough for a full block's worth of bytes
- Calculate *xored
- 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 checking the rest (improves speed in some cases)
- More robust
2019-02-09 13:27 GMT+01:00, Michael Niedermayer :
> On Sat, Feb 09, 2019 at 01:24:35AM +0100, Carl Eugen Hoyos wrote:
>> Hi!
>>
>> Attached patch fixes ticket #7721 for the reporter.
>>
>> Please comment, Carl Eugen
>
>> parseutils.c |2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
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
From 21b11da9af5166e4bda7398a471a1e1a49352ac3 Mon Sep 17 00:00:00 2001
From: Carl Eugen Hoyos
Date: Sat, 9 Feb 2019
On Sat, Feb 09, 2019 at 01:24:35AM +0100, Carl Eugen Hoyos wrote:
> Hi!
>
> Attached patch fixes ticket #7721 for the reporter.
>
> Please comment, Carl Eugen
> parseutils.c |2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
> 9771b8afcf3e4d4a5fe55cd63f60a03cc25a117a
>
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't realized that -crf 0 only works with
newer versions.
Can
On Fri, Feb 8, 2019 at 10:18 PM Jean-Baptiste Kempf wrote:
>
> On Fri, 8 Feb 2019, at 22:08, Lou Logan wrote:
> > On Fri, Feb 8, 2019, at 11:27 AM, Jean-Baptiste Kempf wrote:
> > >
> > > Also, the AUR recipe does not push for non-free packages.
> >
> > The proposed homebrew formulae will not push
43 matches
Mail list logo
