On Sat, Oct 16, 2021 at 10:06:35AM -0300, James Almer wrote:
> On 10/14/2021 10:08 AM, lance.lmw...@gmail.com wrote:
> > From: Limin Wang
> >
> > Signed-off-by: Limin Wang
> > ---
> > libavfilter/af_replaygain.c | 4 ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git
Fixes: Timeout
Fixes:
39971/clusterfuzz-testcase-minimized-ffmpeg_IO_DEMUXER_fuzzer-5756969890217984
Fixes:
39977/clusterfuzz-testcase-minimized-ffmpeg_dem_DHAV_fuzzer-5327123053674496
Found-by: continuous fuzzing process
https://github.com/google/oss-fuzz/tree/master/projects/ffmpeg
Signed-off
It seems no actively maintained distribution is using 4.0 anymore
Signed-off-by: Michael Niedermayer
---
src/download| 37 -
src/olddownload | 37 +
2 files changed, 37 insertions(+), 37 deletions(-)
diff --git a/src/do
On 10/17/2021 5:03 PM, Michael Niedermayer wrote:
It seems no actively maintained distribution is using 4.0 anymore
Signed-off-by: Michael Niedermayer
---
src/download| 37 -
src/olddownload | 37 +
2 files changed,
Hi folks -
Just wanted to follow up on this patch. Is it obviously wrong, it
doesn't scratch a common itch, or... ? I've tested the camera
connection and ran the patched code through FATE. The frigate
container I'm using has audio disabled entirely since it's unreliable on
many devices and this
On Fri, Oct 01, 2021 at 06:53:23PM -0400, Jeff Mahoney wrote:
> When SDP specifies a decoder config, there may not be any AU headers
> provided by the sender. This can result in rtp_parse_mp4_au failing
> and aac_parse_packet reporting "Error parsing AU headers." and no audio
> is recovered from t
On Mon, 2021-10-11 at 04:19 +, Soft Works wrote:
> The test /libavutil/tests/hwdevice checks that when deriving a device
> from a source device and then deriving back to the type of the source
> device, the result is matching the original source device, i.e. the
> derivation mechanism doesn't c
If possible, I'd like a review on
https://patchwork.ffmpeg.org/project/ffmpeg/patch/20210806091633.2083-1-br...@frogmouth.net/[1]
Its been a couple of months, and I haven't got any feedback.
The patch isn't very invasive, and is closely based on previous nv and x265
patches.
Brad
[
