> On 2016 Jan 9, at 9:02 AM, Moritz Barsnick <[email protected]> wrote: > > On Sat, Jan 09, 2016 at 07:11:16 -0700, Jim Worrall wrote: > >> This is great, but with libx265, none of the x265 info gets into the >> report - it is missing. With libx264, the libx264 output DOES get >> into the report - it works fine. > > It appears - from looking at the sources - that ffmpeg's libx264 > integration lets libx264 use ffmpeg's logging functions (by a so-called > callback). Therefore, libx264's log outputs land in ffmpeg's log. > > This does not seem to be the case for libx265 - either because the > library does not supply these hooks, or ffmpeg doesn't use them. So > libx265 probably outputs that information to stdout/stderr by its own > means.
If I’m understanding right, that would mean that redirecting ffmpeg’s stderr and stdout would not capture libx265’s output? _______________________________________________ ffmpeg-user mailing list [email protected] http://ffmpeg.org/mailman/listinfo/ffmpeg-user
