diff options
| author | wm4 <nfxjfg@googlemail.com> | 2017-03-18 09:49:20 +0100 |
|---|---|---|
| committer | wm4 <nfxjfg@googlemail.com> | 2017-03-21 06:17:43 +0100 |
| commit | 66963d4b8d302611553e7928063c1cb2ff0efdff (patch) | |
| tree | f2a400ae751c44dbc3ed093dd85ae7700edea524 /libavcodec | |
| parent | 2e5c52896b0a07dee714267ab5beab7ad0ae5c90 (diff) | |
avcodec: remove warning against using frame threading with hwaccels
libavcodec now automatically serializes decoding for hwaccels which
are not thread-safe. This means API users, which rely on the libavcodec
native software fallback mechanism, can now simply enable threading
without running into problems.
Diffstat (limited to 'libavcodec')
| -rw-r--r-- | libavcodec/utils.c | 5 |
1 files changed, 0 insertions, 5 deletions
diff --git a/libavcodec/utils.c b/libavcodec/utils.c index 9b055d2b3e..365ee26056 100644 --- a/libavcodec/utils.c +++ b/libavcodec/utils.c @@ -1076,11 +1076,6 @@ static int setup_hwaccel(AVCodecContext *avctx, AVHWAccel *hwa = find_hwaccel(avctx->codec_id, fmt); int ret = 0; - if (avctx->active_thread_type & FF_THREAD_FRAME) { - av_log(avctx, AV_LOG_WARNING, - "Hardware accelerated decoding with frame threading is known to be unstable and its use is discouraged.\n"); - } - if (!hwa) { av_log(avctx, AV_LOG_ERROR, "Could not find an AVHWAccel for the pixel format: %s", |