# Problem with files taking over 30 hours to convert **URL:** \ **Category:** Hardware Encoding\ **Created:** [May 14, 2018, 5:59pm UTC](https://discussion.mcebuddy2x.com/t/problem-with-files-taking-over-30-hours-to-convert/1767 "2018-05-14T17:59:44Z")\ **Posts on this page:** 1\ **Showing post:** 5
**Author:** ![RBoy](https://discussion.mcebuddy2x.com/letter_avatar_proxy/v4/letter/r/2bfe46/32.png) [@RBoy](https://discussion.mcebuddy2x.com/u/RBoy)\ **Post date:** [May 15, 2018, 3:43pm UTC](https://discussion.mcebuddy2x.com/t/problem-with-files-taking-over-30-hours-to-convert/1767/5 "2018-05-15T15:43:01Z")
It’s a combination of your video file (invalid FPS) and your NVidia driver is slowing it down. MCEBuddy detected hardware encoding and enabled it so the encoding is done by your video card. There’s something about your video FPS which isn’t sitting right with your video graphics driver and it’s crawling while converting it. > 2018-05-13T23:36:50 MCEBuddy.Transcode.ConvertWithFfmpeg → NVENC H.264 Hardware encoder detected, enabling h264 hardware encoder You can try to play with your profile settings to see what’s causing the graphics driver to slow down. The logs are giving a clue, something to do with your video frame rate. > 2018-05-13T23:36:50 MCEBuddy.AppWrapper.FFmpeg → [mp4 @ 00000148cf29e7e0] Frame rate very high for a muxer not efficiently supporting it. > 2018-05-13T23:36:50 MCEBuddy.AppWrapper.FFmpeg → Please consider specifying a lower framerate, a different muxer or -vsync 2 It could just a bug in the graphics driver. It would be easier to update your [graphics drivers](https://discussion.mcebuddy2x.com/t/63) or use one of the community recommended versions. If that doesn’t work, try adding `-vsync 2` to the beginning of your `ffmpeg-video=` line in your profile as the logs recommend. --- _[View the full topic](https://discussion.mcebuddy2x.com/t/problem-with-files-taking-over-30-hours-to-convert/1767)._