> Why this restriction? I think all log lines should be start with
> time/date if corresponding flag is present. This makes the log to be
> easy to parse by scripts.
Initially I didn’t have this restriction, but it doesn’t work well together
with some multi-line logging.
See below for an example.
To get this nice, it would require a larger amount of changes, and probably
result in something that nobody wants to merge in.
Anyway, there’s a flag controlling this behavior and if you really want, you
can set it.
Then you’ll see something like this:
18:59:04.449 Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'file:xxxxxxx.mp4':
18:59:04.449 Metadata:
major_brand : isom18:59:04.449
minor_version : 51218:59:04.449
compatible_brands: isomiso2avc1mp4118:59:04.449
encoder : Lavf58.12.10018:59:04.449
Duration: 00:20:52.72, start: 0.000000, bitrate: 1386 kb/s18:59:04.449
Stream #0:0(und): Video: h264 (High) (avc1 / 0x31637661), yuv420p, 640x360
[SAR 1:1 DAR 16:9], 612 kb/s, Level 30, 25 fps, 25 tbr, 12800 tbn, 50 tbc
(default)18:59:04.449
18:59:04.449 Metadata:
handler_name : VideoHandler18:59:04.449
Stream #0:1(ger): Audio: aac (LC) (mp4a / 0x6134706D), 48000 Hz, 5.1, fltp,
381 kb/s (default)18:59:04.449
18:59:04.449 Metadata:
handler_name : SoundHandler18:59:04.449
Stream #0:2(eng): Audio: aac (LC) (mp4a / 0x6134706D), 48000 Hz, 5.1, fltp,
382 kb/s18:59:04.449
18:59:04.449 Metadata:
handler_name : SoundHandler18:59:04.449
18:59:04.737 Stream mapping:
Stream #0:0 (h264_cuvid) -> scale_cuda (graph 0)18:59:04.737
scale_cuda (graph 0)18:59:04.737 -> Stream #0:0 (h264_nvenc)
Stream #0:1 -> #0:1 (aac (native) -> mp3 (libmp3lame))18:59:04.737
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
