# FPS when using Hardware Encoding

**URL:** <https://discussion.mcebuddy2x.com/t/fps-when-using-hardware-encoding/4728>\
**Category:** Hardware Encoding\
**Created:** [June 5, 2022, 6:25pm UTC](https://discussion.mcebuddy2x.com/t/fps-when-using-hardware-encoding/4728 "2022-06-05T18:25:21Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![darwinbrew4242](https://discussion.mcebuddy2x.com/letter_avatar_proxy/v4/letter/d/96bed5/32.png) [@darwinbrew4242](https://discussion.mcebuddy2x.com/u/darwinbrew4242)\
**Post date:** [June 5, 2022, 6:25pm UTC](https://discussion.mcebuddy2x.com/t/fps-when-using-hardware-encoding/4728/1 "2022-06-05T18:25:21Z")

</div>

Using Intel QuickSync and ffmpeg as it seems to be much faster than handbrake. Sometimes it takes 1 to 1 1/2 hours for a 1 hour show to convert other times it takes 20 to 30 minutes. Where can I look at see what the FPS is while encoding is happening? I have an HP Z2 SFF G4 Workstation with a Intel64 Family 6 Model 158 Stepping 10 GenuineIntel ~3192 Mhz (8th Gen processor) 64Gb memory Windows 10 pro everything is fully up to date. Hardware Encoding is active. When i’m doing the encoding I always shut everything else down. Any advice/help would be appreciated as I’d really like to get this working faster. Some people it only takes 5-10 minutes to do this conversion but I’m always somewhere between 20min and 1.5 hours.

---

<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:** [June 6, 2022, 9:49pm UTC](https://discussion.mcebuddy2x.com/t/fps-when-using-hardware-encoding/4728/2 "2022-06-06T21:49:05Z")

</div>

If you open the logs you’ll be able to see the details. For quicksync we’re using a special (older) version of handbrake which is faster in our test setup.

Can you try this, open your mcebuddy installation folder, open the handbrake folder. In there rename the `HandBrakeCLI_qsv` to `HandBrakeCLI_qsvold` and then make a copy of `HandBrakeCLI` and call it `HandBrakeCLI_qsv`. Now run your handbrake profile again and let us know if you see any difference. Feel free to attach the logs from both runs (with the existing `HandBrakeCLI_qsv` and the renamed `HandBrakeCLI_qsv`).
