[FFmpeg-devel] [PATCH 1/2] lavf: make max_analyze_duration warning an information log.
Clément Bœsch
ubitux at gmail.com
Thu Jan 26 13:53:43 CET 2012
This avoids the confusion of having a warning almost everytime we are
probing a mp3. It may suppose the file is not muxed correctly while it
is actually a normal behaviour.
---
libavformat/utils.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/libavformat/utils.c b/libavformat/utils.c
index 005704c..08cadd1 100644
--- a/libavformat/utils.c
+++ b/libavformat/utils.c
@@ -2520,7 +2520,7 @@ int avformat_find_stream_info(AVFormatContext *ic, AVDictionary **options)
t = FFMAX(t, av_rescale_q(st->codec_info_nb_frames, (AVRational){st->avg_frame_rate.den, st->avg_frame_rate.num}, AV_TIME_BASE_Q));
if (t >= ic->max_analyze_duration) {
- av_log(ic, AV_LOG_WARNING, "max_analyze_duration %d reached at %"PRId64"\n", ic->max_analyze_duration, t);
+ av_log(ic, AV_LOG_INFO, "max_analyze_duration %d reached at %"PRId64"\n", ic->max_analyze_duration, t);
break;
}
st->info->codec_info_duration += pkt->duration;
--
1.7.8.4
More information about the ffmpeg-devel
mailing list