# Handbrake conversion failed with hardware encoder, retrying with default software encoder

**URL:** https://discussion.mcebuddy2x.com/t/handbrake-conversion-failed-with-hardware-encoder-retrying-with-default-software-encoder/1393
**Category:** General Support / Questions
**Tags:** hardwareencoding
**Created:** [February 6, 2018, 2:41pm UTC](https://discussion.mcebuddy2x.com/t/handbrake-conversion-failed-with-hardware-encoder-retrying-with-default-software-encoder/1393 "2018-02-06T14:41:13Z")
**Posts on this page:** 1
**Showing post:** 3

<div class="post-metadata">

### Author: ![Goose](https://discussion.mcebuddy2x.com/letter_avatar_proxy/v4/letter/g/5f9b8f/32.png) [@Goose](https://discussion.mcebuddy2x.com/u/Goose)
#### Post date: [February 6, 2018, 8:22pm UTC](https://discussion.mcebuddy2x.com/t/handbrake-conversion-failed-with-hardware-encoder-retrying-with-default-software-encoder/1393/3 "2018-02-06T20:22:07Z")

</div>

You have a really interesting setup, you have both CUDA (NVidia) and QuickSync (Intel) hardware acceleration. However it looks like your intel drivers are buggy and causing handbrake to hang when it tries to use hardware acceleration.

> 2018-02-06T07:51:46 MCEBuddy.AppWrapper.Handbrake → [07:51:46] qsv\_enc\_init: using ‘hardware (2)’ implementation, API: 1.25  
> 2018-02-06T07:51:47 MCEBuddy.AppWrapper.Handbrake → Error code -17, hb\_qsv\_wait\_on\_sync 602  
> 2018-02-06T07:51:47 MCEBuddy.AppWrapper.Handbrake → ERROR: encqsv: MFXVideoENCODE\_EncodeFrameAsync failed (-17)

So MCEBuddy switches back to software encoding using handbrake without trying to use the nvidia hardware acceleration via ffmpeg (we’ll add that optimization in future to try different hardware encoder before switch to software, primarily because it’s very uncommon to have systems with both types of hardware vendors in them).

**The solution as @Will_Tschumy pointed out is to change the order in your profile to ffmpeg and that should make it use the NVidia card first for hardware encoding and if that are no issues with the driver it should be significantly faster.**

On a side note it’s possible that your Intel card isn’t properly initialized and that your Nvidia card is your primary monitor/display card which is probably why handbrake can’t get it to initialize. If you want to Intel hardware encoding instead of Nvidia then you may want to try the fake display trick to activate your intel card.

> [@GPU/Hardware Encoding/Acceleration FAQs](https://discussion.mcebuddy2x.com/t/gpu-hardware-encoding-acceleration-faqs/63):
>
> This topic is a compilation of the FAQs related to GPU and Hardware encoding 1. What platforms and devices are supported for GPU encoding MCEBuddy supports Intel (QuickSync), NVidia (NVENC/CUDA) and AMD (VCN/VCE/AMF) which are used for decoding and encoding H.264, H.265/HEVC and AV1. See FAQ 2 for driver requirements To use Intel QuickSync H.264 hardware encoders, Intel Sandy Bridge (1st Generation Core) or newer chipsets H.265 hardware encoders, Intel Broadwell (4th Generation Core) …

---

_[View the full topic](https://discussion.mcebuddy2x.com/t/handbrake-conversion-failed-with-hardware-encoder-retrying-with-default-software-encoder/1393)._