On Thu, 17 Jan 2013, Diego Elio Pettenò wrote:
On 17/01/2013 15:21, Martin Storsjö wrote:
Yes, it's not all that nice, but not actually too much of an issue for
the systems where people actually use the avconv front end AFAIK...
Good point — I guess the only place I don't know how would re
On 17/01/2013 15:21, Martin Storsjö wrote:
>>
>
> Yes, it's not all that nice, but not actually too much of an issue for
> the systems where people actually use the avconv front end AFAIK...
Good point — I guess the only place I don't know how would react for
this would be Windows.. if you feel i
On Thu, 17 Jan 2013, Diego Elio Pettenò wrote:
On 17/01/2013 15:12, Martin Storsjö wrote:
-char sdp[2048];
+char sdp[16384];
Hrm, 16KiB on stack? (theoretically)
Yes, it's not all that nice, but not actually too much of an issue for the
systems where people actually use the avconv
On 17/01/2013 15:12, Martin Storsjö wrote:
> -char sdp[2048];
> +char sdp[16384];
Hrm, 16KiB on stack? (theoretically)
--
Diego Elio Pettenò — Flameeyes
flamee...@flameeyes.eu — http://blog.flameeyes.eu/
___
libav-devel mailing list
libav-devel
---
avconv.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/avconv.c b/avconv.c
index dd998ab..f086cbb 100644
--- a/avconv.c
+++ b/avconv.c
@@ -1367,7 +1367,7 @@ static int output_packet(InputStream *ist, const AVPacket
*pkt)
static void print_sdp(void)
{
-char sdp
