From your logs, if you look a little above your NVidia hardware query, it looks for Intel QuickSync:
INFORMATION> 2019-01-01T12:31:44 MCEBuddy.AppWrapper.Handbrake → QuickSync encoding support available → True
INFORMATION> 2019-01-01T12:31:44 MCEBuddy.AppWrapper.Handbrake → H.264 encoding support available → True
INFORMATION> 2019-01-01T12:31:44 MCEBuddy.AppWrapper.Handbrake → H.265 encoding support available → True
It find that your graphics driver is reporting that it supports Intel QuickSync hardware acceleration.
It also finds that your graphics driver is reporting that it supports NVidia CUDA:
2019-01-01T12:31:45 MCEBuddy.AppWrapper.NVidiaQuery → Result = PASS
→ Process exited with code 0
→ NVidia H.264 Hardware Encoder Detected : True
→ NVidia H.265 Hardware Encoder Detected : False
Do you’ve got a setup that supports both QuickSync and CUDA, hence MCEBuddy doesn’t change the encoder order and it uses the encoders as defined in the profile (preserves the encoder order).
→ New encoder tool order → handbrake,ffmpeg,mencoder
That’s why it using handbrake to convert your video; and handbrake is using your Intel graphics hardware encoder and achieving a speed of 145fps
2019-01-01T12:31:55 MCEBuddy.AppWrapper.Handbrake → [12:31:55] qsv_enc_init: using ‘hardware (1)’ implementation, API: 1.19
2019-01-01T12:31:55 MCEBuddy.AppWrapper.Handbrake → [12:31:55] compute_init_delay: 6006 (2 frames)
2019-01-01T12:31:58 MCEBuddy.AppWrapper.Handbrake → Encoding: task 1 of 2, 0.56 %
2019-01-01T12:32:00 MCEBuddy.AppWrapper.Handbrake → Encoding: task 1 of 2, 1.24 %
2019-01-01T12:32:02 MCEBuddy.AppWrapper.Handbrake → Encoding: task 1 of 2, 1.89 % (148.02 fps, avg 143.78 fps, ETA 00h05m04s)
So technically it’s using hardware encoding but just not the encoder you want.
If you want it to use NVIDIA instead of QuickSync then change your encoder order in the profile:
from:
order=handbrake,ffmpeg,mencoder
to
order=ffmpeg,handbrake,mencoder