diff options
author | wm4 <wm4@nowhere> | 2019-10-20 23:22:21 +0200 |
---|---|---|
committer | wm4 <wm4@nowhere> | 2019-10-21 01:38:25 +0200 |
commit | 8a4e9d5c180157684546db4c1235d8c958172ca9 (patch) | |
tree | fca0975bd57849b387b1367d2757eeb76dc27624 /video/sws_utils.c | |
parent | 579b9eb8dec1f9d5708bb163ac13090f3af3bf76 (diff) | |
download | mpv-8a4e9d5c180157684546db4c1235d8c958172ca9.tar.bz2 mpv-8a4e9d5c180157684546db4c1235d8c958172ca9.tar.xz |
sws_utils: improve zimg fallback messages
This could log:
[swscale] falling back to swscale
And that's a WTF, even if you're aware of the fucky way zimg was hacked
into the filter chain.
Diffstat (limited to 'video/sws_utils.c')
-rw-r--r-- | video/sws_utils.c | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/video/sws_utils.c b/video/sws_utils.c index 9f1d0fd950..b667390eca 100644 --- a/video/sws_utils.c +++ b/video/sws_utils.c @@ -215,10 +215,10 @@ int mp_sws_reinit(struct mp_sws_context *ctx) ctx->zimg->dst = *dst; if (mp_zimg_config(ctx->zimg)) { ctx->zimg_ok = true; - MP_VERBOSE(ctx, "using zimg\n"); + MP_VERBOSE(ctx, "Using zimg.\n"); goto success; } - MP_WARN(ctx, "falling back to swscale\n"); + MP_WARN(ctx, "Not using zimg, falling back to swscale.\n"); } #endif |