[Ffmpeg-devel] ffmpeg help going to both stdout and stderr.

[eo rojas]

I guess, after looking at the code I agree.  There is one other hack that
could be made to work, and that is add a parameter to the log-callback
function that is a FILE *.  We could then add another interface which
av_log_stdout, and av_log_stderr, which call the static av_vlog with with
appropriate file pointer, and finally, av_log would could either call
av_vlog with stderr, or one could create a static that is initialized to
stderr, but has an external setter.  This would allow writing a log to a
file without overloading the call back, which might have other advantages.

thoughts?

On 6/13/06, Michael Niedermayer <michaelni at gmx.at> wrote:
>
> Hi
>
> On Mon, Jun 12, 2006 at 01:37:06PM -0700, Emil Rojas wrote:
> > I   understand that one can do this.  I understand now that changing the
> > logging system  to go the stdout would be a bad idea, so maybe the
> problem
> > is that usage information is dumped via the logging system instead of
> > printf.    Thoughts?  Note that only part of the usage is dumped this
> way.
>
> a AV_LOG_STDOUT flag might help, patches and alternative ideas are welcome
> like always ...
>
> [...]
> --
> Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
>
> In the past you could go to a library and read, borrow or copy any book
> Today you'd get arrested for mere telling someone where the library is
> _______________________________________________
> ffmpeg-devel mailing list
> ffmpeg-devel at mplayerhq.hu
> http://lists.mplayerhq.hu/mailman/listinfo/ffmpeg-devel
>



-- 
eo rojas