Movie Edit Pro 2022: Hardware Encoding broke

Simply_Simon wrote on 10/17/2026, 3:07 AM

Hello everybody,

after a few months break, I wanted to make a video yesterday, and dutifully updated the program to its latest version. I edited the video as normal, but noticed when exporting it as an MPEG-4 that the "Mixing down" window said (no hardware encoding).

I had this issue previously, but some change of settings was able to fix it, and I could export my videos using my graphics card. However, none of my attempted fixes worked this time.

Some basics:

Windows computer with:
- Windows 10 Education, 64-Bit
- AMD Ryzen 9 5900X 12-Core Processor (no on-board graphics card)
- NVidia GeForce RTX 2060 Super
- 32689 MB RAM

Here's the program settings to show that Magix sees my graphics card:

And here's my export settings:

Fairly demanding, but again, nothing that was an issue previously.

I've tried a lot of things, a selection:

- update all drivers (NVidia studio, Windows Update)
- reinstall the program
- force windows to assign the correct graphics card to the program
- attempt an export on an old project I knew worked
- set Hardware encoding to CPU and back again (fiddling with these settings was what helped me last time)
- changing the program settings to various other processing/export modules
- lowering the quality of the export, basically changing every single dropdown menu to see if that would do anything

To confirm that the issue is coming from within the program, I exported the raw video with Handbrake, which used the hardware acceleration fine.

Using hardware acceleration, this video should encode in about 5 minutes based on my previous experience; without, it's taking about 2 hours. Is there something I can do to re-enable this? One thing I'd be happy to try is if using a previous version of Magix would fix the issue. Where could I find one that is about half a year old (last time it worked)?

Happy to give more details (video settings, details of original footage...) but I don't want to bloat this post. Thanks for the help!

Comments

johnebaker wrote on 10/17/2026, 3:47 AM

@Simply_Simon

Hi

. . . . update all drivers . . . .

There was a known issue with the Nvidia driver and Movie Studio caused partly by a Nvidia driver update, if you want a long read see this topic.

TLDR - try rolling rolling back the RTX 2060 drivers to the version that worked previously, preferably version 581.80 from here - this is the Game ready driver, AFAICS the equivalent Studio driver is not avaialble.

John EB
Forum Moderator

 

VPX 17, Video deluxe 2026, and earlier versions MEP 2015 and 2016, Music Maker Premium 2026.

PC - running Windows 11 25H2 Professional on Intel i7-8700K 3.2 GHz, 16GB RAM, RTX 2060 6GB 192-bit GDDR6, 1 x 1Tb Sabrent NVME SSD (OS and programs), 2 x 4TB (Data) internal HDD + 1TB internal SSD (Work disc), + ext backup HDDs.

Laptop - Lenovo Legion 5i Phantom - running Windows 11 25H2 on Intel Core i7-10750H, 16GB DDR4-SDRAM, 512GB SSD, 43.9 cm screen Full HD 1920 x 1080, Intel UHD 630 iGPU and NVIDIA GeForce RTX 2060 (6GB GDDR6)

Sony FDR-AX53e Video camera, DJI Osmo Action 3 and Sony HDR-AS30V Sports cams.

Simply_Simon wrote on 10/17/2026, 4:45 AM

@Simply_Simon

Hi

. . . . update all drivers . . . .

There was a known issue with the Nvidia driver and Movie Studio caused partly by a Nvidia driver update, if you want a long read see this topic.

TLDR - try rolling rolling back the RTX 2060 drivers to the version that worked previously, preferably version 581.80 from here - this is the Game ready driver, AFAICS the equivalent Studio driver is not avaialble.

John EB
Forum Moderator

 

Oh wow, this immediately fixed it, without even needing a computer restart. I don't update my NVidia drivers automatically - there have been issues previously - so it's likely that when I last edited a video, around April this year, that I was still on a version like the November 2025 one you linked me. This was also the GameReady driver, I didn't even know they had a Studio one until yesterday. Bizarre that this hasn't been fixed almost a year later, but that is not your fault, obviously.

I'll keep everything on this version for now. Thanks a lot!