On Fri, May 26, 2017 at 09:29:04PM -0400, Micah Galizia wrote:
> On Sat, May 20, 2017 at 9:36 PM, Micah Galizia wrote:
> > On 2017-05-17 05:23 AM, wm4 wrote:
> >>
> >> On Sat, 6 May 2017 14:28:10 -0400
> >> Micah Galizia wrote:
> >>
> >>> On 2017-05-05 09:28 PM, wm4 wrote:
>
> On Fri,
On Sun, May 28, 2017 at 08:35:25PM +0100, Rostislav Pehlivanov wrote:
> On 28 May 2017 at 20:19, Michael Niedermayer wrote:
>
> > Fixes: 1882/clusterfuzz-testcase-minimized-5539735650959360
> >
> > Found-by: continuous fuzzing process https://github.com/google/oss-
> > fuzz/tree/master/projects/f
On Fri, May 26, 2017 at 09:19:09AM +0800, Jun Zhao wrote:
> golomb.h |5 -
> 1 file changed, 4 insertions(+), 1 deletion(-)
> 228c7180856b65d095dd0b8d59f3d3ff4f65774a
> 0001-lavc-golomb-Fix-UE-golomb-overwrite-issue.patch
> From eabcbf3d41e83f24623e6195d4a0ff86e4d95a80 Mon Sep 17 00:00:0
On 5/28/17, Rostislav Pehlivanov wrote:
> The library has stopped being developed and Debian has removed it
> from its repositories citing security issues.
> The native Dirac decoder supports everything the library has and encoding
> support is still provided via the native vc2 (Dirac Pro) encoder
The library has stopped being developed and Debian has removed it
from its repositories citing security issues.
The native Dirac decoder supports everything the library has and encoding
support is still provided via the native vc2 (Dirac Pro) encoder. Hence,
there's no reason to still support linki
Signed-off-by: James Almer
---
libavformat/aiffenc.c | 45 +
1 file changed, 29 insertions(+), 16 deletions(-)
diff --git a/libavformat/aiffenc.c b/libavformat/aiffenc.c
index fcadf149a0..1e0c5b11a0 100644
--- a/libavformat/aiffenc.c
+++ b/libavformat/
Signed-off-by: James Almer
---
libavformat/oggenc.c | 32
1 file changed, 28 insertions(+), 4 deletions(-)
diff --git a/libavformat/oggenc.c b/libavformat/oggenc.c
index 0713a13a70..7c1115afd6 100644
--- a/libavformat/oggenc.c
+++ b/libavformat/oggenc.c
@@ -483,7
On 28 May 2017 at 20:19, Michael Niedermayer wrote:
> Fixes: 1882/clusterfuzz-testcase-minimized-5539735650959360
>
> Found-by: continuous fuzzing process https://github.com/google/oss-
> fuzz/tree/master/projects/ffmpeg
> Signed-off-by: Michael Niedermayer
> ---
> libavcodec/aacsbr.c | 1 +
>
On 5/28/2017 4:28 PM, Rostislav Pehlivanov wrote:
> libnut is outdated and not developed anymore, all nut developments
> happens in this repo, so users are getting mislead
> ---
> Changelog| 1 +
> MAINTAINERS | 1 -
> configure| 6 -
> libavforma
libnut is outdated and not developed anymore, all nut developments
happens in this repo, so users are getting mislead
---
Changelog| 1 +
MAINTAINERS | 1 -
configure| 6 -
libavformat/Makefile | 2 -
libavformat/allformats.c | 1 -
libavf
Le sextidi 6 prairial, an CCXXV, Daniel Kučera a écrit :
> If we return 0, then it is considered as EOF by calling functions
> (e.g. avio_read). So returning 0 means: "this is end of stream" and
> not: "we received zero length packet, but more data may be coming" and
> thus the stream processing en
Fixes: 1882/clusterfuzz-testcase-minimized-5539735650959360
Found-by: continuous fuzzing process
https://github.com/google/oss-fuzz/tree/master/projects/ffmpeg
Signed-off-by: Michael Niedermayer
---
libavcodec/aacsbr.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/libavcodec/aacsbr.c b/li
2017-05-23 20:44 GMT+02:00 Daniel Kucera :
> Time to time some devices send UDP packets without payload.
> ffmpeg previously exited on receiving such packet, this patch
> fixes this behaviour.
>
> Signed-off-by: Daniel Kucera
> ---
> libavformat/udp.c | 6 +-
> 1 file changed, 5 insertions(+)
On Sun, May 28, 2017 at 8:06 PM, Kevin Mark wrote:
> Any thoughts on creating shorthand variables? I don't
> see a particular need for them but it would put these new variables in
> line with the others. mw for main_w, mh for main_h. Potentially ma for
> main_a. I don't have a strong feeling on
On Sat, May 27, 2017 at 8:29 PM, Michael Niedermayer
wrote:
> main_*
> and
> ref_*
>
> are maybe prefixes that would work without conflicting with the
> existing ones
I'm partial to main_* since when I think of ref_* that makes me think
of the input being used "as basis" (in the words of the docu
On Sat, May 27, 2017 at 1:36 PM, Gyan wrote:
> It's weird, given those uses cases - overlays - to override the operand's
> native aspect ratio. I'd say, a design oversight, at least.
I agree. I'm not aware of any common workflow that you would have
subtitles (transparent PNGs or something) that w
On Sat, May 27, 2017 at 8:30 PM, Michael Niedermayer
wrote:
> should be merged with the patch that adds these constants
>
> thx
I'll include this with the other updated patch.
Thanks,
Kevin
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://f
17 matches
Mail list logo
