From 2a2dc1dd417a78650675f327f6db832e58e229a8 Mon Sep 17 00:00:00 2001
From: wxf
Date: Fri, 15 Feb 2019 09:41:29 +0800
Subject: [PATCH] lavf/mpeg: fix indent
Signed-off-by: wxf
---
libavformat/mpeg.c | 56 +++---
1 file changed, 28 insertions(+),
>
> 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-
>On Fri, Feb 15, 2019 at 12:13:43AM +0100, Michael Niedermayer wrote:
> > On Wed, Feb 13, 2019 at 05:56:50PM +0800, Shiyou Yin wrote:
> > > >-Original Message-
> > > >From: ffmpeg-devel-boun...@ffmpeg.org
> > > >[mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf Of gxw
> > > >Sent: Tuesday
Fixes: Out of array access
Fixes:
13090/clusterfuzz-testcase-minimized-ffmpeg_AV_CODEC_ID_MPEG4_fuzzer-5408668986638336
Found-by: continuous fuzzing process
https://github.com/google/oss-fuzz/tree/master/projects/ffmpeg
Signed-off-by: Michael Niedermayer
---
libavcodec/mpeg4videodec.c | 1 +
1
On 15.02.2019 01:01, Carl Eugen Hoyos wrote:
2019-02-14 23:36 GMT+01:00, Carl Eugen Hoyos :
please mention ticket #7735.
Ping!
I remembered the moment i pushed the patch, sorry.
smime.p7s
Description: S/MIME Cryptographic Signature
___
ffmpeg-d
2019-02-15 1:12 GMT+01:00, Carl Eugen Hoyos :
> 2019-02-15 0:23 GMT+01:00, Hendrik Leppkes :
>> On Thu, Feb 14, 2019 at 8:11 PM Carl Eugen Hoyos
>> wrote:
>>>
>>> Hi!
>>>
>>> I created attached patch with a lot of help from Hendrik, fixes ticket
>>> #7731.
>>>
>>
>> Som general comments, since I c
2019-02-15 0:23 GMT+01:00, Hendrik Leppkes :
> On Thu, Feb 14, 2019 at 8:11 PM Carl Eugen Hoyos wrote:
>>
>> Hi!
>>
>> I created attached patch with a lot of help from Hendrik, fixes ticket
>> #7731.
>>
>
> Som general comments, since I can't replay inline in this mail client:
>
> - The pseudo-tim
2019-02-14 23:36 GMT+01:00, Carl Eugen Hoyos :
> please mention ticket #7735.
Ping!
Carl Eugen
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
You changed libavfilter but didn't commit (I guess), please mention
ticket #7735.
(I didn't test myself, sorry if there is no issue!)
I just completely missed the parts in libavfilter.
I am thoroughly confused why this did not break compilation for me.
Will push the missing part asap.
smime.p
On Fri, Feb 15, 2019 at 12:13:43AM +0100, Michael Niedermayer wrote:
> On Wed, Feb 13, 2019 at 05:56:50PM +0800, Shiyou Yin wrote:
> > >-Original Message-
> > >From: ffmpeg-devel-boun...@ffmpeg.org
> > >[mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf Of gxw
> > >Sent: Tuesday, February
On Thu, Feb 14, 2019 at 8:11 PM Carl Eugen Hoyos wrote:
>
> Hi!
>
> I created attached patch with a lot of help from Hendrik, fixes ticket #7731.
>
Som general comments, since I can't replay inline in this mail client:
- The pseudo-timestamps are unsigned 16-bit, personally I would make
all type
2019-02-15 0:13 GMT+01:00, Hendrik Leppkes :
> On Thu, Feb 14, 2019 at 11:36 PM Carl Eugen Hoyos
> wrote:
>> >>> No, this entire mess with duplicated ff_ symbols is specifically to
>> >>> avoid having to include it in the ABI.
>> >>
>> >> But old libavcodec does not work with new libavutil now or
On Thu, Feb 14, 2019 at 11:36 PM Carl Eugen Hoyos wrote:
> >>> No, this entire mess with duplicated ff_ symbols is specifically to
> >>> avoid having to include it in the ABI.
> >>
> >> But old libavcodec does not work with new libavutil now or am I wrong?
> >
> > Is that really a thing we expect
On Thu, Feb 14, 2019 at 8:14 PM Carl Eugen Hoyos wrote:
>
> 2019-02-14 20:11 GMT+01:00, Carl Eugen Hoyos :
>
> > I created attached patch with a lot of help from Hendrik, fixes
> > ticket #7731.
>
> I forgot: I still need help to fix the frame distance calculation,
> how is the frame rate supposed
On Wed, Feb 13, 2019 at 05:56:50PM +0800, Shiyou Yin wrote:
> >-Original Message-
> >From: ffmpeg-devel-boun...@ffmpeg.org
> >[mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf Of gxw
> >Sent: Tuesday, February 12, 2019 6:56 PM
> >To: ffmpeg-devel@ffmpeg.org
> >Cc: gxw
> >Subject: [FFmpeg-
2019-02-14 23:17 GMT+01:00, Timo Rothenpieler :
> On 14.02.2019 19:59, Carl Eugen Hoyos wrote:
>> 2019-02-14 18:21 GMT+01:00, Hendrik Leppkes :
>>> On Thu, Feb 14, 2019 at 4:51 PM Carl Eugen Hoyos
>>> wrote:
> Am 14.02.2019 um 13:39 schrieb Timo Rothenpieler :
>
> ffmpeg
On 14.02.2019 19:59, Carl Eugen Hoyos wrote:
2019-02-14 18:21 GMT+01:00, Hendrik Leppkes :
On Thu, Feb 14, 2019 at 4:51 PM Carl Eugen Hoyos wrote:
Am 14.02.2019 um 13:39 schrieb Timo Rothenpieler :
ffmpeg | branch: master | Timo Rothenpieler |
Fri Feb 8 22:47:01 2019 +0100|
[15c63901390
2019-02-14 22:08 GMT+01:00, James Almer :
> On 2/14/2019 5:59 PM, Carl Eugen Hoyos wrote:
>> 2019-02-12 12:58 GMT+01:00, Carl Eugen Hoyos :
>>> Hi!
>>>
>>> The output of truehd_core is currently undeterministic, the last bytes
>>> are uninitialized, valgrind protests if less than 8 bytes are
>>> in
On Wed, Feb 13, 2019 at 08:03:36PM -0800, Philip Langdale wrote:
> We need all the flags to be exposed to be able to pass them on to
> HW decoders. I did not attempt to nuance any of the warnings about
> flags being unsupported as there's no way, at the point we extract
> flags, to say whether an H
On 2/14/2019 5:59 PM, Carl Eugen Hoyos wrote:
> 2019-02-12 12:58 GMT+01:00, Carl Eugen Hoyos :
>> Hi!
>>
>> The output of truehd_core is currently undeterministic, the last bytes
>> are uninitialized, valgrind protests if less than 8 bytes are
>> initialized.
>> I believe attached patch is simpler
On Wed, Feb 13, 2019 at 11:49:21PM +0100, Mathieu Duponchelle wrote:
> So, should this go in? :)
if someone checks it against some spec and or tests it against some
decoders, probably yes,
also might be a good idea to bump the micro version of libavcodec
thanks
[...]
--
Michael GnuPG finge
2019-01-27 15:18 GMT+01:00, Carl Eugen Hoyos :
> Hi!
>
> Minimal simplification attached.
Ping.
Carl Eugen
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
2019-02-07 20:07 GMT+01:00, Carl Eugen Hoyos :
> Hi!
>
> Attached patch fixes ticket #7675.
Ping.
Carl Eugen
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
2019-02-12 12:58 GMT+01:00, Carl Eugen Hoyos :
> Hi!
>
> The output of truehd_core is currently undeterministic, the last bytes
> are uninitialized, valgrind protests if less than 8 bytes are
> initialized.
> I believe attached patch is simpler than calculating the necessary
> write size at the bot
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
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 :
>> Hi!
>>
>> Attached patch constifies a few pointers at the next version bump.
>
> And the patch.
Ping.
Carl Eugen
___
ffmpeg-devel mailing list
ffmpeg-deve
Hi!
Currently, when muxing TrueHD in spdif, the buffer is always overwritten.
Typical 64bit operating systems do not care, but this should definitely be
fixed before the new buffering model can get committed.
Please comment, Carl Eugen
From 3858971376f97241d29d4f7d3b261009af3c87a9 Mon Sep 17 00:0
2019-02-14 20:11 GMT+01:00, Carl Eugen Hoyos :
> I created attached patch with a lot of help from Hendrik, fixes
> ticket #7731.
I forgot: I still need help to fix the frame distance calculation,
how is the frame rate supposed to be used?
Iiuc, the current code only works for 48kHz audio.
Thank
2019-02-13 8:10 GMT+01:00, Hendrik Leppkes :
> On Wed, Feb 13, 2019 at 2:57 AM Carl Eugen Hoyos wrote:
>>
>> 2019-02-13 0:47 GMT+01:00, Hendrik Leppkes :
>> > On Tue, Feb 12, 2019 at 12:54 PM Carl Eugen Hoyos
>> > wrote:
>> >>
>> >> 2019-02-12 12:37 GMT+01:00, Hendrik Leppkes :
>> >> > On Tue, Fe
Hi!
I created attached patch with a lot of help from Hendrik, fixes ticket #7731.
Please review, Carl Eugen
From ce97425171b06b353cf9ec71e9ff6c7e7ec49422 Mon Sep 17 00:00:00 2001
From: Carl Eugen Hoyos
Date: Thu, 14 Feb 2019 20:07:53 +0100
Subject: [PATCH] lavf/spdifenc: Use a more flexible buff
2019-02-14 18:21 GMT+01:00, Hendrik Leppkes :
> On Thu, Feb 14, 2019 at 4:51 PM Carl Eugen Hoyos wrote:
>>
>>
>>
>> > Am 14.02.2019 um 13:39 schrieb Timo Rothenpieler :
>> >
>> > ffmpeg | branch: master | Timo Rothenpieler |
>> > Fri Feb 8 22:47:01 2019 +0100|
>> > [15c6390139096b7e7634bf0f6aaab
Hi,
this will add support for b_adapt for HEVC encoder, now Turing HEVC
NVENC with SDK 9.0 also supports B-frames and this option is in default
mode disabled. Enable it by default, because it could add around 0.02
PSNR for free.
--
Miroslav Slugeň
+420 724 825 885
diff --git a/libavcodec/nv
On Thu, Feb 14, 2019 at 4:51 PM Carl Eugen Hoyos wrote:
>
>
>
> > Am 14.02.2019 um 13:39 schrieb Timo Rothenpieler :
> >
> > ffmpeg | branch: master | Timo Rothenpieler | Fri
> > Feb 8 22:47:01 2019 +0100| [15c6390139096b7e7634bf0f6aaab1cd8b3aa509] |
> > committer: Timo Rothenpieler
> >
> > av
> Am 14.02.2019 um 16:41 schrieb Dominik 'Rathann' Mierzejewski
> :
>
>> On Sunday, 03 February 2019 at 22:24, Dominik 'Rathann' Mierzejewski wrote:
>>> On Monday, 28 January 2019 at 04:54, James Almer wrote:
>>> On 1/27/2019 3:43 PM, Dominik 'Rathann' Mierzejewski wrote:
>> [...]
If you'
> Am 14.02.2019 um 13:39 schrieb Timo Rothenpieler :
>
> ffmpeg | branch: master | Timo Rothenpieler | Fri Feb
> 8 22:47:01 2019 +0100| [15c6390139096b7e7634bf0f6aaab1cd8b3aa509] |
> committer: Timo Rothenpieler
>
> avutil/cuda_check: avoid pointlessly exporting same symbol from two librari
On Sunday, 03 February 2019 at 22:24, Dominik 'Rathann' Mierzejewski wrote:
> On Monday, 28 January 2019 at 04:54, James Almer wrote:
> > On 1/27/2019 3:43 PM, Dominik 'Rathann' Mierzejewski wrote:
> [...]
> > > If you're trying to say we can upgrade 4.0.x to 4.1.x without
> > > recompiling any dep
Hi, can this be merged or is more rigourous testing necessary?
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
On Thu, 14 Feb 2019 13:52:45 +0100
Timo Rothenpieler wrote:
>
> First patch needs ACK by the respective maintainer. Which I believe
> was already done last time it was sent?
>
Actually not. Without the real headers, I didn't know there were new
HEVC fields to set, so this part is new for this
On Wed, Feb 13, 2019 at 12:16:36PM +, Derek Buitenhuis wrote:
> On 12/02/2019 22:28, Michael Niedermayer wrote:
> > @@ -5048,7 +5048,7 @@ static int mov_read_sidx(MOVContext *c, AVIOContext
> > *pb, MOVAtom atom)
> > for (i = 0; i < c->fc->nb_streams; i++) {
> > st = c->f
On 14.02.2019 05:03, Philip Langdale wrote:
This is the equivalent change for cuviddec after the previous change
for nvdec. I made similar changes to the copying routines to handle
pixel formats in a more generic way.
Note that unlike with nvdec, there is no confusion about the ability
of a code
On 13.02.2019 20:18, Timo Rothenpieler wrote:
On 13.02.2019 09:52, Roman Arzumanyan wrote:
Hello,
Please find attached patch, it adds HEVC B-frames support to nvenc_hevc.
This feature requires Video Codec SDK 9 + Turing card.
Will it cause issues if set on an older card, or just plain get i
42 matches
Mail list logo
