I had a disk crash about a month ago and had to use a system image backup that was about 6 months old. Since then I haven’t been able to get MCEB to use my
nVidia RTX 3060 for anything. I have the paid version and also the donator version of comskip. I also remember using the extra command in “–cuvid”. So, what else has to be enabled/checked/paid for to get this working?
profiles.conf (101.5 KB)
mcebuddy.log (8.6 MB)
mcebuddy.conf (4.0 KB)
comskip.ini (6.2 KB)
Action News 11 PM 2026_02_15_23_00_00.ts-Convert&Remove Ads-2026-02-16T11-17-12.log (2.4 MB)
It sounds like your system image restore might have rolled back your NVIDIA drivers or messed up the hardware acceleration registration. Since you’re using an RTX 3060, here is a checklist to get GPU acceleration back up and running:
1. Update/Reinstall NVIDIA Drivers
Restoring an old image likely reverted your drivers to a version that doesn’t support the latest NVENC features or lacks the necessary DLLs for MCEBuddy’s version of FFmpeg/Handbrake.
- Action: Download the latest Game Ready or Studio Driver from NVIDIA’s website. Choose “Perform a clean installation” if prompted.
2. Check the “Hardware Encoding” Toggle
Ensure that hardware encoding is still enabled in your specific conversion profile settings.
- Go to Settings → Conversion Task → Expert Settings.
- Make sure Enable Hardware Encoding is checked.
3. Re-Verify Comskip Donator Version
You mentioned using the donator version of Comskip. If the system image was old, the comskip.exe might have been overwritten by the free version included in the base installer.
- Action: Ensure your Donator
comskip.exe is in the C:\Program Files\MCEBuddy2x\comskip folder. The donator version is required for GPU (CUVID) support in Comskip.
4. Codec/Filter Check (--cuvid)
You mentioned using the --cuvid command. Depending on the profile you are using (FFmpeg or Handbrake), the syntax matters.
- In your
profiles.conf, ensure the parameters are correctly passing to the encoder.
- Note: Recent versions of MCEBuddy handle many of these flags automatically when “Hardware Encoding” is checked. You might try removing the manual
--cuvid flag temporarily to see if the auto-detection picks up the RTX 3060.
5. Reviewing your Logs
I noticed you attached your logs. I’ll take a look at the Action News...log. Usually, if the GPU fails, the log will show an error like:
Device creation failed: -1313558101 or No NVENC capable devices found.
Quick Fix Tip: Try switching your Profile to an “MKV NVIDIA” or “MP4 NVIDIA” specific profile to see if it triggers the GPU immediately.
If you’d like me to look for specific error codes in that log file, let me know!
I wanted to follow on with some more information. Looks like the GPU is being used for part of the process. It’s the conversion part that seems to be using Handbrake CLI that is using the CPU instead of the GPU to do the conversion to .MKV from .TS. Hope this helps in someone here having an answer for me.