diff options
author | wm4 <wm4@nowhere> | 2016-04-03 19:45:09 +0200 |
---|---|---|
committer | wm4 <wm4@nowhere> | 2016-04-03 19:45:09 +0200 |
commit | da3489353bce9e47ab7786c4798f774b0a61340d (patch) | |
tree | c16e7b2992e8c02cf3c9afae0c221d81e79f8421 /stream | |
parent | 2720e60ad00ff7cce1d80724bbd4b2b981748195 (diff) | |
download | mpv-da3489353bce9e47ab7786c4798f774b0a61340d.tar.bz2 mpv-da3489353bce9e47ab7786c4798f774b0a61340d.tar.xz |
cache: disable useless "Cache is not responding" warning
Tuning it in a way to be actually useful is too much effort.
As alternative, there's the "buffering" detection, which operates on a
much higher level. The only disadvantage is that it's harder to guess
for the user whether this is a network problem, or if e.g. libavformat
is probing too much data when opening a stream. Maybe the cache-speed
property is helpful here.
For now, do not remove the associated code, but just silence the
warning.
Fixes #3019.
Diffstat (limited to 'stream')
-rw-r--r-- | stream/cache.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/stream/cache.c b/stream/cache.c index 874cdf4a8c..f8304df8b9 100644 --- a/stream/cache.c +++ b/stream/cache.c @@ -136,7 +136,7 @@ static void cache_wakeup_and_wait(struct priv *s, double *retry_time) { double start = mp_time_sec(); if (*retry_time >= CACHE_WAIT_TIME) { - MP_WARN(s, "Cache is not responding - slow/stuck network connection?\n"); + MP_VERBOSE(s, "Cache is not responding - slow/stuck network connection?\n"); *retry_time = -1; // do not warn again for this call } |