The changes in my review don't look to have been made.
http://www.ffmpeg.org/pipermail/ffmpeg-devel/2019-March/240931.html
Gyan
On 20-03-2019 01:14 PM, Jing Sun wrote:
Add docs for libsvt_hevc encoder in encoders.texi and general.texi
Signed-off-by: Jun Zhao
Signed-off-by: Zhengxu Huang
Si
On Mon, 18 Mar 2019 13:56:52 +0200
Lauri Kasanen wrote:
> Signed-off-by: Lauri Kasanen
> ---
> libswscale/ppc/swscale_ppc_template.c | 21 +++--
> 1 file changed, 11 insertions(+), 10 deletions(-)
Applying these two.
- Lauri
___
ffmp
2019-03-08 7:39 GMT+01:00, Decai Lin :
> 1. add MaxMBPS checking for level idc setting to align with AVC spec
>AnnexA table A-1/A-6 level limits.
> 2. update h264 level fate test.
>
> Signed-off-by: Decai Lin
> ---
> libavcodec/h264_levels.c | 6 +
> libavcodec/h264_levels.h
2019-03-19 18:11 GMT+01:00, swarajhota...@gmail.com :
> From: Swaraj Hota
>
> Fixes ticket #4519.
> ---
> This is my qualification task for GSoC 2019.
> Please suggest any more changes if required.
There is a zipped section in the files starting at 0xe4,
the password is "meta". Is there anyth
> -Original Message-
> From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf Of
> Carl Eugen Hoyos
> Sent: 2019年3月20日 16:33
> To: FFmpeg development discussions and patches
>
> Subject: Re: [FFmpeg-devel] [PATCH v2 1/1] lavc/h264_levels: add MaxMBPS
> checking and update
1. add MaxMBPS checking for level idc setting to align with AVC spec
AnnexA table A-1/A-6 level limits.
2. update h264 level fate test.
Signed-off-by: Decai Lin
---
libavcodec/h264_levels.c | 4 +++
libavcodec/h264_levels.h | 1 +
libavcodec/h264_metadata_bsf.c | 9 ++-
lib
2019-03-19 20:11 GMT+01:00, Gyan :
>
>
> On 20-03-2019 12:03 AM, Kieran Kunhya wrote:
>
> >From a84db9c39d382a37f76ae72e490d25ca451155c4 Mon Sep 17 00:00:00 2001
> >From: Kieran Kunhya
> >Date: Tue, 19 Mar 2019 18:31:39 +
> >Subject: [PATCH] News: Removal of libndi
> >
> >---
> > src/in
On Wednesday, 20 March 2019 at 00:48, Carl Eugen Hoyos wrote:
> 2019-03-19 23:28 GMT+01:00, Dominik 'Rathann' Mierzejewski
> :
>
> > Were the CVE IDs not known at the time these were pushed to master?
>
> No, how would this be possible?
Easy: you can request the ID at https://cveform.mitre.org/
./ffmpeg -f lavfi -i yuvtestsrc=duration=1:size=1200x1440 \
-s 1200x1440 -f null -vframes 100 -pix_fmt $i -nostats \
-cpuflags 0 -v error -
This uses 32-bit mul, so POWER8 only.
The following output formats get about 4.5x speedup:
rgb24
39980 UNITS in yuv2packed1, 32768 runs,
tis 2019-03-19 klockan 22:53 + skrev Aidan R:
> @@ -69,13 +75,25 @@ static int wsaud_probe(AVProbeData *p)
> if (p->buf[10] & 0xFC)
> return 0;
>
> -if (p->buf[11] != 99 && p->buf[11] != 1)
> +/* valid format values are 99 == adpcm, 1 == snd1 and 0 == pcm */
> +if (p
2019-03-20 13:37 GMT+01:00, Lauri Kasanen :
> @@ -480,5 +722,66 @@ av_cold void ff_sws_init_swscale_vsx(SwsContext *c)
Are there followup patches?
Or why is the following hunk so convoluted?
> +if (c->flags & SWS_BITEXACT)
> +return;
> +#if !HAVE_BIGENDIAN
Are you planning to add b
2019-03-20 12:08 GMT+01:00, Dominik 'Rathann' Mierzejewski
:
> On Wednesday, 20 March 2019 at 00:48, Carl Eugen Hoyos wrote:
>> 2019-03-19 23:28 GMT+01:00, Dominik 'Rathann' Mierzejewski
>> :
>>
>> > Were the CVE IDs not known at the time these were pushed to master?
>>
>> No, how would this be pos
On Wed, 20 Mar 2019 14:41:27 +0100
Carl Eugen Hoyos wrote:
> 2019-03-20 13:37 GMT+01:00, Lauri Kasanen :
>
> > @@ -480,5 +722,66 @@ av_cold void ff_sws_init_swscale_vsx(SwsContext *c)
>
> Are there followup patches?
> Or why is the following hunk so convoluted?
I plan to add the _2 and _X varian
./ffmpeg -f lavfi -i yuvtestsrc=duration=1:size=1200x1440 \
-s 1200x1440 -f null -vframes 100 -pix_fmt $i -nostats \
-cpuflags 0 -v error -
This uses 32-bit mul, so POWER8 only.
The following output formats get about 4.5x speedup:
rgb24
39980 UNITS in yuv2packed1, 32768 runs,
On 3/20/19, Nick Renieris wrote:
> Hello,
>
>>Similarly if we support demuxing "auxilary / secondary or what they are
>> called images" and muxing then we should be able to connect these and not
>> just be able to extract one image.
>>Thats the ideal. The question how to implement this, or if this
On Tue, 19 Mar 2019, at 21:37, Martin Vignali wrote:
> >+Support for the nonfree NDI protocol has been removed, it had
> > been a common source of GPL violations.
> >
> This doesn't justify to break user tools (who respect the ffmpeg licence)
tools who depend on a license violation are viola
> From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf
> Of Mark Thompson
> Sent: Tuesday, March 19, 2019 8:18 AM
> To: ffmpeg-devel@ffmpeg.org
> Subject: [FFmpeg-devel] [PATCH 2/3] lavc/qsvdec: Add VP9 decoder support
>
> From: Zhong Li
>
> VP9 decoder is supported on Intel kab
On 18/03/2019 20:31, James Almer wrote:
> Fixes deadlocks when decoding packets containing more than one of the
> aforementioned
> slices when using frame threads.
>
> Signed-off-by: James Almer
> ---
If there are no other comments / objections, could this be pushed?
- Derek
__
2019-03-20 15:06 GMT+01:00, Lauri Kasanen :
> +case AV_PIX_FMT_BGRA:
> +if (HAVE_POWER8 && cpu_flags & AV_CPU_FLAG_POWER8) {
> +if (!c->needAlpha) {
> +c->yuv2packed1 = yuv2bgrx32_full_1_vsx;
If only non-alpha is supported, I
On Wed, 20 Mar 2019 15:51:20 +0100
Carl Eugen Hoyos wrote:
> 2019-03-20 15:06 GMT+01:00, Lauri Kasanen :
>
> > +case AV_PIX_FMT_BGRA:
> > +if (HAVE_POWER8 && cpu_flags & AV_CPU_FLAG_POWER8) {
> > +if (!c->needAlpha) {
> > +c-
Στις Τετ, 20 Μαρ 2019 στις 4:17 μ.μ., ο/η Paul B Mahol
έγραψε:
> DNG I posted should be decodeable by default, without need for extra
> option(s).
The DNG contents themselves? As in, not just the thumbnail? That's
what the whole GSoC proposal is about though... What about:
>On Tue, Mar 19, 2019
Currectly just standard header path and be found,
check_type/struct will fail if vaapi is installed somewhere else.
---
configure | 18 ++
1 file changed, 10 insertions(+), 8 deletions(-)
diff --git a/configure b/configure
index eaf543df96..0e3c2d24bf 100755
--- a/configure
+++ b/
2019-03-20 16:06 GMT+01:00, Lauri Kasanen :
> On Wed, 20 Mar 2019 15:51:20 +0100
> Carl Eugen Hoyos wrote:
>
>> 2019-03-20 15:06 GMT+01:00, Lauri Kasanen :
>>
>> > +case AV_PIX_FMT_BGRA:
>> > +if (HAVE_POWER8 && cpu_flags & AV_CPU_FLAG_POWER8) {
>> > +
> > >+Support for the nonfree NDI protocol has been removed, it had
> > > been a common source of GPL violations.
> > >
> > This doesn't justify to break user tools (who respect the ffmpeg licence)
>
> tools who depend on a license violation are violating the license too...
>
FFmpeg can be
Martin Vignali (12019-03-20):
> FFmpeg can be compile with GPL and non free component, if the build is not
> redistributed.
> There is no licence violation in this case.
>
> It's not because some people doesn't respect the licence, that every user
> of non free component do the same.
Making it ea
On Wed, 20 Mar 2019, at 16:35, Martin Vignali wrote:
> > > >+Support for the nonfree NDI protocol has been removed, it had
> > > > been a common source of GPL violations.
> > > >
> > > This doesn't justify to break user tools (who respect the ffmpeg licence)
> >
> > tools who depend on a lice
tis 2019-03-19 klockan 22:53 + skrev Aidan R:
> @@ -69,13 +75,25 @@ static int wsaud_probe(AVProbeData *p)
>> if (p->buf[10] & 0xFC)
>> return 0;
>>
>> -if (p->buf[11] != 99 && p->buf[11] != 1)
>> +/* valid format values are 99 == adpcm, 1 == snd1 and 0 == pcm */
>> +
2019-03-09 11:08 GMT+01:00, Carl Eugen Hoyos :
> Attached patch improves decoding this image, reported by Ulf Zibis:
> http://samples.ffmpeg.org/image-samples/flower-separated-contig-16.tif
Patch applied.
Carl Eugen
___
ffmpeg-devel mailing list
ffmpeg
ons 2019-03-20 klockan 15:56 + skrev Aidan R:
> tis 2019-03-19 klockan 22:53 + skrev Aidan R:
> > > @@ -130,20 +161,24 @@ static int wsaud_read_packet(AVFormatContext *s,
> > > AVPacket *pkt)
> > > {
> > > AVIOContext *pb = s->pb;
> > > +AUDDemuxConte
2019-03-15 1:23 GMT+01:00, Carl Eugen Hoyos :
> Attached patch fixes another fate crash on 64bit sparc
Patch applied.
Carl Eugen
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
2019-03-16 0:11 GMT+01:00, Michael Niedermayer :
> On Fri, Mar 15, 2019 at 12:56:05AM +0100, Carl Eugen Hoyos wrote:
>> Hi!
>>
>> Attached patch silences three warnings with clang and makes the
>> pointer type equal to what the function called with the pointer
>> expects.
>>
>> Please comment, Carl
On Wed, 20 Mar 2019 16:31:57 +0100
Carl Eugen Hoyos wrote:
> 2019-03-20 16:06 GMT+01:00, Lauri Kasanen :
> > On Wed, 20 Mar 2019 15:51:20 +0100
> > Carl Eugen Hoyos wrote:
> >
> >> 2019-03-20 15:06 GMT+01:00, Lauri Kasanen :
> >>
> >> > +case AV_PIX_FMT_BGRA:
> >> > +
2019-02-14 22:44 GMT+01:00, Carl Eugen Hoyos :
> New patch with AV_WN64() attached.
Patch applied.
Carl Eugen
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
2019-03-20 17:24 GMT+01:00, Lauri Kasanen :
> On Wed, 20 Mar 2019 16:31:57 +0100
> Carl Eugen Hoyos wrote:
>
>> 2019-03-20 16:06 GMT+01:00, Lauri Kasanen :
>> > On Wed, 20 Mar 2019 15:51:20 +0100
>> > Carl Eugen Hoyos wrote:
>> >
>> >> 2019-03-20 15:06 GMT+01:00, Lauri Kasanen :
>> >>
>> >> > +
2019-02-14 20:18 GMT+01:00, Carl Eugen Hoyos :
> Currently, when muxing TrueHD in spdif, the buffer is always overwritten.
Patch applied, this should be backported imo.
Carl Eugen
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org
2019-02-10 1:01 GMT+01:00, Carl Eugen Hoyos :
> Attached patch simplifies the debugging of icy metadata, required to
> answer the tickets of one regular reporter.
Patch applied.
Carl Eugen
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://f
2019-02-07 20:07 GMT+01:00, Carl Eugen Hoyos :
> Attached patch fixes ticket #7675.
Patch applied.
Carl Eugen
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
2019-01-27 15:18 GMT+01:00, Carl Eugen Hoyos :
> Minimal simplification attached.
Patch applied.
Carl Eugen
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
On 20.03.2019 17:37, Jean-Baptiste Kempf wrote:
On Wed, 20 Mar 2019, at 16:35, Martin Vignali wrote:
[...]
We don't talk about a contribution remove for technical reason.
But a contributor's work remove in order to try to annoy a licence
violator.
Absolutely not. The work was removed because
2019-02-09 15:46 GMT+01:00, Carl Eugen Hoyos :
> 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 libavfor
On Tue, Mar 19, 2019 at 11:28:01PM +0100, Dominik 'Rathann' Mierzejewski wrote:
> Hello,
> please backport fixes for CVE-2019-9718 and CVE-2019-9721 to 3.4
> and 4.0 branches. The relevant commits seem to be:
> 1f00c97bc3475c477f3c468cf2d924d5761d0982
> 894995c41e0795c7a44f81adc4838dedc3932e65
>
>
On 3/20/2019 2:41 PM, Carl Eugen Hoyos wrote:
> 2019-02-09 15:46 GMT+01:00, Carl Eugen Hoyos :
>> 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 const
2019-03-20 18:50 GMT+01:00, James Almer :
> Could you add a comment stating that, much like the FF_API_ defines,
> this ff_const59 define is not part of the public API and will eventually
> disappear without warning?
Done.
Thank you for the suggestion, Carl Eugen
2019-02-09 15:51 GMT+01:00, Carl Eugen Hoyos :
> 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!
>
> Atta
2019-02-09 23:27 GMT+01:00, Carl Eugen Hoyos :
> 2019-02-09 23:26 GMT+01:00, Carl Eugen Hoyos :
>> Attached patch constifies a few pointers at the next version bump.
>
> And the patch.
Patch applied.
Carl Eugen
___
ffmpeg-devel mailing list
ffmpeg-deve
On Wed, Mar 20, 2019 at 12:08:52PM +0100, Dominik 'Rathann' Mierzejewski wrote:
> On Wednesday, 20 March 2019 at 00:48, Carl Eugen Hoyos wrote:
> > 2019-03-19 23:28 GMT+01:00, Dominik 'Rathann' Mierzejewski
> > :
> >
> > > Were the CVE IDs not known at the time these were pushed to master?
> >
>
On Wed, Mar 20, 2019, at 9:58 AM, Carl Eugen Hoyos wrote:
>
> Patch applied.
>
Breaks compilation for me on x86_64 linux:
/usr/bin/ld: libavformat/libavformat.a(allformats.o):(.data.rel.ro+0x398):
undefined reference to `ff_kux_demuxer'
collect2: error: ld returned 1 exit status
make: *** [Make
On Wed, 20 Mar 2019, Jean-Baptiste Kempf wrote:
On Wed, 20 Mar 2019, at 16:35, Martin Vignali wrote:
> > >+Support for the nonfree NDI protocol has been removed, it had
> > > been a common source of GPL violations.
> > >
> > This doesn't justify to break user tools (who respect the ffmp
On Wed, Mar 20, 2019 at 04:06:45PM +0200, Lauri Kasanen wrote:
> ./ffmpeg -f lavfi -i yuvtestsrc=duration=1:size=1200x1440 \
> -s 1200x1440 -f null -vframes 100 -pix_fmt $i -nostats \
> -cpuflags 0 -v error -
>
> This uses 32-bit mul, so POWER8 only.
>
> The following output forma
Maksym Veremeyenko (12019-03-20):
> when do you plan to remove nVidia and BlackmagicDesign parts that is /closed
> source and userland/ ?
"They were talking too" is not a good strategy when the teacher tells
you to be quiet.
But I count you as one vote for removing any non-free components.
Thanks
On Thu, Mar 14, 2019 at 12:03:17AM +0100, Michael Niedermayer wrote:
> Fixes: Timeout (30sec -> 2sec)
> Fixes:
> 13578/clusterfuzz-testcase-minimized-ffmpeg_AV_CODEC_ID_ARBC_fuzzer-5685625527730176
>
> Found-by: continuous fuzzing process
> https://github.com/google/oss-fuzz/tree/master/projects
On Fri, Mar 15, 2019 at 01:30:12AM +0100, Michael Niedermayer wrote:
> Optimization found while looking at
> 13442/clusterfuzz-testcase-minimized-ffmpeg_AV_CODEC_ID_SCPR_fuzzer-5758293933293568
>
> Found-by: continuous fuzzing process
> https://github.com/google/oss-fuzz/tree/master/projects/ffm
I had found that when capturing video for some hours from
USB Camera-B4.09.24.1 (Manufacturer: OmniVision Technologies, Inc.),
sometimes when invoking the ioctl DQBUF, the returned buffer is not
filled with the size we expect for the raw video frame.
Here are two examples for such occurrences:
On 2019-03-18 23:26 +0100, Alexander Strasser wrote:
> On 2019-03-18 00:24 +0100, Nicolas George wrote:
> > Alexander Strasser (12019-03-18):
> > > I tested the EAGAIN version and it worked. I also tested returning a
> >
> > ffmpeg.c uses the non-blocking mode.
>
> That would explain it. I now test
On Tue, Mar 19, 2019 at 10:53:11PM +, Aidan R wrote:
> PCM format AUD files are found in Westwood's Blade Runner game.
> ---
> libavformat/westwood_aud.c | 83
> --
> 1 file changed, 66 insertions(+), 17 deletions(-)
>
> diff --git a/libavformat/we
On Wed, 20 Mar 2019, at 18:03, Maksym Veremeyenko wrote:
> On 20.03.2019 17:37, Jean-Baptiste Kempf wrote:
> > On Wed, 20 Mar 2019, at 16:35, Martin Vignali wrote:
> [...]
> >> We don't talk about a contribution remove for technical reason.
> >> But a contributor's work remove in order to try to an
On Wed, 20 Mar 2019, at 19:34, Marton Balint wrote:
> As I described in similar threads before, whether or not the project want
> closed source support for NDI is a subjective issue, please start a vote
> about the removal of libndi if you want to seek this through.
The removal of libndi is actu
On Wed, 20 Mar 2019, Jean-Baptiste Kempf wrote:
On Wed, 20 Mar 2019, at 19:34, Marton Balint wrote:
As I described in similar threads before, whether or not the project want
closed source support for NDI is a subjective issue, please start a vote
about the removal of libndi if you want to se
Marton Balint (12019-03-20):
> That is just sad an unfair.
Maybe. But let us be very clear about this: the people to blame for this
mess are those who chose a proprietary license for their library in the
first place.
Regards,
--
Nicolas George
signature.asc
Description: PGP signature
__
On Wed, 20 Mar 2019, at 20:52, Marton Balint wrote:
> On Wed, 20 Mar 2019, Jean-Baptiste Kempf wrote:
>
> > On Wed, 20 Mar 2019, at 19:34, Marton Balint wrote:
> >> As I described in similar threads before, whether or not the project want
> >> closed source support for NDI is a subjective issue,
On Wed, 20 Mar 2019, Jean-Baptiste Kempf wrote:
On Wed, 20 Mar 2019, at 20:52, Marton Balint wrote:
On Wed, 20 Mar 2019, Jean-Baptiste Kempf wrote:
> On Wed, 20 Mar 2019, at 19:34, Marton Balint wrote:
>> As I described in similar threads before, whether or not the project want
>> closed so
On 21-03-2019 01:32 AM, Marton Balint wrote:
On Wed, 20 Mar 2019, Jean-Baptiste Kempf wrote:
On Wed, 20 Mar 2019, at 20:52, Marton Balint wrote:
On Wed, 20 Mar 2019, Jean-Baptiste Kempf wrote:
> On Wed, 20 Mar 2019, at 19:34, Marton Balint wrote:
>> As I described in similar threads befor
On Wed, 20 Mar 2019, at 21:02, Marton Balint wrote:
> On Wed, 20 Mar 2019, Jean-Baptiste Kempf wrote:
> > On Wed, 20 Mar 2019, at 20:52, Marton Balint wrote:
> >> On Wed, 20 Mar 2019, Jean-Baptiste Kempf wrote:
> >>
> >> > On Wed, 20 Mar 2019, at 19:34, Marton Balint wrote:
> >> >> As I described
Jean-Baptiste Kempf (12019-03-20):
> 2) Both of those are addressing drivers for actual cards.
> So we're not talking about userland, but accessing drivers which are
> part of the OS, and are therefore exempted by the GPL.
I am not sure I agree with that interpretation. The wording is quite
obscu
On Wed, 20 Mar 2019 at 23:02, Marton Balint wrote:
>
>
> On Wed, 20 Mar 2019, Jean-Baptiste Kempf wrote:
>
> > On Wed, 20 Mar 2019, at 20:52, Marton Balint wrote:
> >> On Wed, 20 Mar 2019, Jean-Baptiste Kempf wrote:
> >>
> >> > On Wed, 20 Mar 2019, at 19:34, Marton Balint wrote:
> >> >> As I desc
On Wed, 20 Mar 2019, at 21:20, Nicolas George wrote:
> Jean-Baptiste Kempf (12019-03-20):
> > 2) Both of those are addressing drivers for actual cards.
> > So we're not talking about userland, but accessing drivers which are
> > part of the OS, and are therefore exempted by the GPL.
>
> I am not
On Wed, 20 Mar 2019, at 21:20, Dennis Mungai wrote:
> At the very best, the lack of consensus on this implies vindictive intent.
> Is there something that the FFmpeg developers (see below) have against
> Newtek, as a company?
> Clearly, they took down the offending FFmpeg build:
> https://trac.ffm
Hi all!
On 2019-03-20 19:56 +0100, Alexander Strasser wrote:
> I had found that when capturing video for some hours from
> USB Camera-B4.09.24.1 (Manufacturer: OmniVision Technologies, Inc.),
> sometimes when invoking the ioctl DQBUF, the returned buffer is not
> filled with the size we expect for
On Wednesday, 20 March 2019 at 18:42, Michael Niedermayer wrote:
> On Tue, Mar 19, 2019 at 11:28:01PM +0100, Dominik 'Rathann' Mierzejewski
> wrote:
> > Hello,
> > please backport fixes for CVE-2019-9718 and CVE-2019-9721 to 3.4
> > and 4.0 branches. The relevant commits seem to be:
> > 1f00c97bc3
On Wednesday, 20 March 2019 at 19:18, Michael Niedermayer wrote:
> On Wed, Mar 20, 2019 at 12:08:52PM +0100, Dominik 'Rathann' Mierzejewski
> wrote:
> > On Wednesday, 20 March 2019 at 00:48, Carl Eugen Hoyos wrote:
> > > 2019-03-19 23:28 GMT+01:00, Dominik 'Rathann' Mierzejewski
> > > :
> > >
> >
Hi,
On Wed, Mar 20, 2019 at 4:15 PM Gyan wrote:
>
>
> On 21-03-2019 01:32 AM, Marton Balint wrote:
> >
> >
> > On Wed, 20 Mar 2019, Jean-Baptiste Kempf wrote:
> >
> >> On Wed, 20 Mar 2019, at 20:52, Marton Balint wrote:
> >>> On Wed, 20 Mar 2019, Jean-Baptiste Kempf wrote:
> >>>
> >>> > On Wed,
From: ffmpeg-devel on behalf of Michael
Niedermayer
Sent: 20 March 2019 19:08
To: FFmpeg development discussions and patches
Subject: Re: [FFmpeg-devel] [PATCH v2] avformat/westwood_aud: Adds PCM format
demux.
> fails probetest:
>
>
> tools/probetest 256 4096
> testing size=1
> testing size=
2019-03-20 19:23 GMT+01:00, Lou Logan :
> On Wed, Mar 20, 2019, at 9:58 AM, Carl Eugen Hoyos wrote:
>>
>> Patch applied.
>>
>
> Breaks compilation for me on x86_64 linux:
Should be fixed, sorry for the nuisance.
Thank you for the report, Carl Eugen
___
2019-03-20 23:20 GMT+01:00, Aidan R :
> From: ffmpeg-devel on behalf of Michael
> Niedermayer
> Sent: 20 March 2019 19:08
> To: FFmpeg development discussions and patches
> Subject: Re: [FFmpeg-devel] [PATCH v2] avformat/westwood_aud: Adds PCM
> format demux.
>
>> fails probetest:
>>
>>
>> tools/
2019-03-20 22:26 GMT+01:00, Alexander Strasser :
> Hi all!
>
> On 2019-03-20 19:56 +0100, Alexander Strasser wrote:
>> I had found that when capturing video for some hours from
>> USB Camera-B4.09.24.1 (Manufacturer: OmniVision Technologies, Inc.),
>> sometimes when invoking the ioctl DQBUF, the re
On 3/20/2019 11:41 AM, Derek Buitenhuis wrote:
> On 18/03/2019 20:31, James Almer wrote:
>> Fixes deadlocks when decoding packets containing more than one of the
>> aforementioned
>> slices when using frame threads.
>>
>> Signed-off-by: James Almer
>> ---
>
> If there are no other comments / obj
Okay, I found out the metadata block contains fields like:
logo (a url to thumbnail), tags (in Chinese), title (in Chinese as well),
and other information which mostly seem to be related to streaming.
I'm not sure though if anything is much useful. Please do suggest
if you think any of these can b
2017-11-01 3:39 GMT+01:00, Michael Niedermayer :
> On Wed, Nov 01, 2017 at 02:17:06AM +0100, Carl Eugen Hoyos wrote:
>> 2017-10-31 17:38 GMT+01:00 Michael Niedermayer :
>> > On Mon, Oct 30, 2017 at 11:51:30PM +0100, Carl Eugen Hoyos wrote:
>> >> Hi!
>> >>
>> >> Attached patch makes sure the loas mu
2019-03-21 0:04 GMT+01:00, Swaraj Hota :
> Okay, I found out the metadata block contains fields like:
> logo (a url to thumbnail), tags (in Chinese),
> title (in Chinese as well),
Can you convert the title to something that your terminal
(set to utf8) can display?
There is "title" metadata, so th
0001-Use-packet-DTS-to-correct-frame-PTS-for-PTS-missing-.patch
Description: Binary data
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
On Wed, 20 Mar 2019, Carl Eugen Hoyos wrote:
2019-03-20 22:26 GMT+01:00, Alexander Strasser :
Hi all!
On 2019-03-20 19:56 +0100, Alexander Strasser wrote:
I had found that when capturing video for some hours from
USB Camera-B4.09.24.1 (Manufacturer: OmniVision Technologies, Inc.),
sometimes
- Current Status
In cuvid decoder wrapper, PTS is resolved based on input packet PTS.
When PTS is missing, cuvid decoder produces monotorically increasing numbers
with same interval.
This does not occur problem when every single frame in video has same frame
duration like fixed frame rate video.
Fixes: Timeout (77sec -> 1sec)
Fixes:
13407/clusterfuzz-testcase-minimized-ffmpeg_AV_CODEC_ID_DXV_fuzzer-5093143018471424
Found-by: continuous fuzzing process
https://github.com/google/oss-fuzz/tree/master/projects/ffmpeg
Signed-off-by: Michael Niedermayer
---
libavcodec/dxv.c | 2 ++
1 file c
Dennis Mungai , 20 Mar 2019 Çar, 23:20 tarihinde şunu
yazdı:
> On Wed, 20 Mar 2019 at 23:02, Marton Balint wrote:
>
> >
> >
> > On Wed, 20 Mar 2019, Jean-Baptiste Kempf wrote:
> >
> > > On Wed, 20 Mar 2019, at 20:52, Marton Balint wrote:
> > >> On Wed, 20 Mar 2019, Jean-Baptiste Kempf wrote:
> >
On Tue, 12 Mar 2019, Marton Balint wrote:
On Tue, 5 Mar 2019, Marton Balint wrote:
set_metadata with many entries is not very efficient, and with small audio
frames the performance loss is noticable. Also with this very simple
calculations (like peak) can be even further optimized.
Unfotu
Hi!
Attached patch makes the only argument to the common probe() function const.
Please comment, Carl Eugen
From 2d8fe30a4fe88c932e8c9c9dfb55150d6aa45f5f Mon Sep 17 00:00:00 2001
From: Carl Eugen Hoyos
Date: Thu, 21 Mar 2019 01:18:37 +0100
Subject: [PATCH] lavf: Constify the probe function argum
2018-11-19 18:41 GMT+01:00, Carl Eugen Hoyos :
> 2018-11-19 18:21 GMT+01:00, Pablo Rubio Fernández :
>
>> It's my first time here. I want to create a patch to add Z16 pixel
>> format.
>> I have did some changes, and I want to know if I'll need change any other
>> file.
>
> Isn't attached poc suffic
It enabled MULTIPLE SIMPLE filter graph concurrency, which bring above about
4%~20% improvement in some 1:N scenarios by CPU or GPU acceleration
Below are some test cases and comparison as reference.
(Hardware platform: Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz)
(Software: Intel iHD driver - 16.9.00
Signed-off-by: hwrenx
---
libavcodec/libdavs2.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/libavcodec/libdavs2.c b/libavcodec/libdavs2.c
index b0eb4fd..218f3ec 100644
--- a/libavcodec/libdavs2.c
+++ b/libavcodec/libdavs2.c
@@ -107,7 +107,7 @@ static int davs2_dump_frames(
Signed-off-by: hwrenx
---
libavcodec/libdavs2.c | 16
1 file changed, 16 insertions(+)
diff --git a/libavcodec/libdavs2.c b/libavcodec/libdavs2.c
index 0808721..b0eb4fd 100644
--- a/libavcodec/libdavs2.c
+++ b/libavcodec/libdavs2.c
@@ -129,6 +129,21 @@ static int davs2_dump_fram
> 在 2019年3月21日，上午9:58，hwrenx 写道：
>
> Signed-off-by: hwrenx
> ---
> libavcodec/libdavs2.c | 16
> 1 file changed, 16 insertions(+)
>
> diff --git a/libavcodec/libdavs2.c b/libavcodec/libdavs2.c
> index 0808721..b0eb4fd 100644
> --- a/libavcodec/libdavs2.c
> +++ b/libavcodec/lib
Add docs for libsvt_hevc encoder in encoders.texi and general.texi
Signed-off-by: Jun Zhao
Signed-off-by: Zhengxu Huang
Signed-off-by: Hassene Tmar
Signed-off-by: Jing Sun
---
doc/encoders.texi | 147 ++
doc/general.texi | 8 +++
2 files
Signed-off-by: Zhengxu Huang
Signed-off-by: Hassene Tmar
Signed-off-by: Jun Zhao
Signed-off-by: Jing Sun
---
configure| 4 +
libavcodec/Makefile | 1 +
libavcodec/allcodecs.c | 1 +
libavcodec/libsvt_hevc.c | 505 +++
4 f
On Thu, Mar 21, 2019, 02:35 Ali KIZIL wrote:
> Dennis Mungai , 20 Mar 2019 Çar, 23:20 tarihinde şunu
> yazdı:
>
> > On Wed, 20 Mar 2019 at 23:02, Marton Balint wrote:
> >
> > >
> > >
> > > On Wed, 20 Mar 2019, Jean-Baptiste Kempf wrote:
> > >
> > > > On Wed, 20 Mar 2019, at 20:52, Marton Balint
94 matches
Mail list logo
