summaryrefslogtreecommitdiff
path: root/src/lib/ffmpeg.cc
diff options
context:
space:
mode:
authorCarl Hetherington <cth@carlh.net>2019-12-19 22:56:49 +0000
committerCarl Hetherington <cth@carlh.net>2019-12-19 22:56:49 +0000
commit715d87a4cf9e4697a2f67881776c19c4ce8af581 (patch)
tree0fe261b4b1f1a2daf94a6836959cd969895fec6a /src/lib/ffmpeg.cc
parent1229de2042c785a9e851e5fc53922a75bfbf195d (diff)
Remove our forcing of analyzeduration and probesize as they seem tov2.14.20
cause weird problems when scanning some files. The unit test case added here is a case in point: before this patch one stream reported an incorrect channel count and sample rate. It's a bit worrying as these parameters have been in DoM for many years, but perhaps they have become unnecessary / harmful with changes to FFmpeg.
Diffstat (limited to 'src/lib/ffmpeg.cc')
-rw-r--r--src/lib/ffmpeg.cc5
1 files changed, 0 insertions, 5 deletions
diff --git a/src/lib/ffmpeg.cc b/src/lib/ffmpeg.cc
index f26d1d2cf..2deaf6953 100644
--- a/src/lib/ffmpeg.cc
+++ b/src/lib/ffmpeg.cc
@@ -117,11 +117,6 @@ FFmpeg::setup_general ()
_format_context->pb = _avio_context;
AVDictionary* options = 0;
- /* These durations are in microseconds, and represent how far into the content file
- we will look for streams.
- */
- av_dict_set (&options, "analyzeduration", raw_convert<string> (5 * 60 * 1000000).c_str(), 0);
- av_dict_set (&options, "probesize", raw_convert<string> (5 * 60 * 1000000).c_str(), 0);
if (_ffmpeg_content->decryption_key()) {
av_dict_set (&options, "decryption_key", _ffmpeg_content->decryption_key()->c_str(), 0);
}