On Sun, Apr 05, 2015 at 10:26:15AM +0200, Nicolas George wrote:
> Le tridi 13 germinal, an CCXXIII, Stephan Holljes a écrit :
> > From c01ec773448a76485895171cbfb296657d56da97 Mon Sep 17 00:00:00 2001
> > From: Stephan Holljes
> > Date: Thu, 2 Apr 2015 22:49:07 +0200
> > Subject: [PATCH] libavform
Le tridi 13 germinal, an CCXXIII, Stephan Holljes a écrit :
> From c01ec773448a76485895171cbfb296657d56da97 Mon Sep 17 00:00:00 2001
> From: Stephan Holljes
> Date: Thu, 2 Apr 2015 22:49:07 +0200
> Subject: [PATCH] libavformat/http.c: Add proof-of-concept http server.
>
> Signed-off-by: Stephan H
Le tridi 13 germinal, an CCXXIII, Stephan Holljes a écrit :
> How would http listening work as an input option?
I do not see any particular problem.
With your current patch, you can do:
ffmpeg $input $output_options -listen 1 http://0:1234
ffmpeg -i http://host:1234/ $remote_output
It would wor
On Mon, Mar 30, 2015 at 5:19 PM, Nicolas George wrote:
> Le nonidi 9 germinal, an CCXXIII, Stephan Holljes a écrit :
>> I hope this addresses the issues mentioned.
>> I added a new label in case of failure in http_open() in favor of
>> duplicated code (i.e. calling av_dict_free() multiple times).
Le nonidi 9 germinal, an CCXXIII, Stephan Holljes a écrit :
> I hope this addresses the issues mentioned.
> I added a new label in case of failure in http_open() in favor of
> duplicated code (i.e. calling av_dict_free() multiple times). I copied
> the style from the other functions.
>
> Signed-of
On Sun, 29 Mar 2015 04:13:18 +0200
Stephan Holljes wrote:
> I hope this addresses the issues mentioned.
> I added a new label in case of failure in http_open() in favor of
> duplicated code (i.e. calling av_dict_free() multiple times). I copied
> the style from the other functions.
>
> Signed-of
I hope this addresses the issues mentioned.
I added a new label in case of failure in http_open() in favor of
duplicated code (i.e. calling av_dict_free() multiple times). I copied
the style from the other functions.
Signed-off-by: Stephan Holljes
---
doc/protocols.texi | 3 +++
libavformat/htt
Le septidi 7 germinal, an CCXXIII, Stephan Holljes a écrit :
> I just copied that from the line above, I was not aware of the meaning
> of the letter at all. Changed to "E".
D and E are short-cuts for AV_OPT_FLAG_DECODING_PARAM and
AV_OPT_FLAG_ENCODING_PARAM, that allows front-ends to filter optio
On Thu, 26 Mar 2015 10:15:41 +0100
Nicolas George wrote:
> Le sextidi 6 germinal, an CCXXIII, Stephan Holljes a écrit :
> > I hope this time the patch is formatted correctly. I also attached
> > it in case it is corrupted again.
>
> Sorry, still wrapped. See there:
> http://ffmpeg.org/pipermail/
Le sextidi 6 germinal, an CCXXIII, Stephan Holljes a écrit :
> I hope this time the patch is formatted correctly. I also attached it
> in case it is corrupted again.
Sorry, still wrapped. See there:
http://ffmpeg.org/pipermail/ffmpeg-devel/2015-March/170768.html
Especially the lines with the opti
I hope this time the patch is formatted correctly. I also attached it
in case it is corrupted again.
I changed the indentation of the code and used ffurl_open() instead of
creating my own listening socket.
I am still having some trouble with the Content-Type header. I would
guess creating function
Le primidi 1er germinal, an CCXXIII, Stephan Holljes a écrit :
> Please comment.
As Michael pointed out, the patch was mangled at sending. That happens with
mail user agent that rely on "rich" text editor and do not let users control
the formatting finely. Using git send-email or attaching the fil
On Sun, Mar 22, 2015 at 2:34 AM, Michael Niedermayer
wrote:
> On Sun, Mar 22, 2015 at 12:33:57AM +0100, Stephan Holljes wrote:
> > Hi,
> >
> > what would be the correct way to create patches that won't be corrupted?
> I
> > merely tried to copy what I have seen on the mailing-list before,
> > app
On Sun, Mar 22, 2015 at 12:33:57AM +0100, Stephan Holljes wrote:
> Hi,
>
> what would be the correct way to create patches that won't be corrupted? I
> merely tried to copy what I have seen on the mailing-list before,
> apparently I didn't do a very good job ;)
git send-email -1
would send the mo
Hi,
what would be the correct way to create patches that won't be corrupted? I
merely tried to copy what I have seen on the mailing-list before,
apparently I didn't do a very good job ;)
Regards,
Stephan Holljes
On Sun, Mar 22, 2015 at 12:24 AM, Michael Niedermayer
wrote:
> On Sat, Mar 21, 201
On Sat, Mar 21, 2015 at 11:00:09PM +0100, Stephan Holljes wrote:
> Hi,
>
> this is a patch for a proof-of-concept for an http server.
>
> Usage on the server side:
>
> ffmpeg -i test.mp3 -c copy -listen 1 -f mp3 http://0.0.0.0
>
> Usage on the client side:
>
> ffplay http://localhost:8080
>
>
Hi,
this is a patch for a proof-of-concept for an http server.
Usage on the server side:
ffmpeg -i test.mp3 -c copy -listen 1 -f mp3 http://0.0.0.0
Usage on the client side:
ffplay http://localhost:8080
I looked at tls.c and tcp.c and copied parts of the code.
Please comment.
Regards,
Stepha
17 matches
Mail list logo
