fix these strange behavior:
-af flanger=delay=10 [OK]
-af flanger=delay=1e1 [OK]
-af flanger=delay=1e+1 [Error]
-af flanger=delay=0.1 [OK]
-af flanger=delay=1e-1 [Error]
thank's
---
libavutil/opt.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/libavutil/opt.c
On Sat, 19 Jul 2014 18:16:42 -0800
Lou Logan l...@lrcd.com wrote:
On Tue, Jul 15, 2014, at 12:10 AM, Clément Bœsch wrote:
- should we restore the hall of shame page, or maybe simply add a
Violations linking to a specific query in our trac?
I prefer a link to the trac violations. Or no
On Mon, Jul 21, 2014 at 2:25 PM, compn te...@mi.rr.com wrote:
On Sun, 20 Jul 2014 09:20:30 -0800
Lou Logan l...@lrcd.com wrote:
On Sat, Jul 19, 2014, at 11:49 PM, Clément Bœsch wrote:
libx264 is not always available and not that much common (it
requires special permissions), and the avi to
On Mon, Jul 21, 2014 at 02:31:41AM -0700, Muhammad Faiz wrote:
fix these strange behavior:
-af flanger=delay=10 [OK]
-af flanger=delay=1e1 [OK]
-af flanger=delay=1e+1 [Error]
-af flanger=delay=0.1 [OK]
-af flanger=delay=1e-1 [Error]
thank's
---
libavutil/opt.c | 2 +-
1 file
Andreas Cadhalpun andreas.cadhalpun at googlemail.com writes:
This patch has a strange side effect. With it gst-libav1.0
(version 1.3.2) gets compiled incorrectly so that when the
plugin is loaded by gstreamer it segfaults:
ERROR: Caught a segmentation fault while loading plugin file:
On 22.07.2014 02:12, Andreas Cadhalpun wrote:
On 21.07.2014 23:18, Carl Eugen Hoyos wrote:
Andreas Cadhalpun andreas.cadhalpun at googlemail.com writes:
This patch has a strange side effect. With it gst-libav1.0
(version 1.3.2) gets compiled incorrectly so that when the
plugin is loaded by
On Tue, Jul 22, 2014 at 03:34:45AM +0200, Andreas Cadhalpun wrote:
On 22.07.2014 02:12, Andreas Cadhalpun wrote:
On 21.07.2014 23:18, Carl Eugen Hoyos wrote:
Andreas Cadhalpun andreas.cadhalpun at googlemail.com writes:
This patch has a strange side effect. With it gst-libav1.0
(version
