From da3489353bce9e47ab7786c4798f774b0a61340d Mon Sep 17 00:00:00 2001 From: wm4 Date: Sun, 3 Apr 2016 19:45:09 +0200 Subject: 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. --- stream/cache.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'stream') 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 } -- cgit v1.2.3