WIll we also get a fix for older versions? I use Video Deluxe Premium 2024 and didn't got any fix.

@RealymanLP

WIll we also get a fix for older versions? I use Video Deluxe Premium 2024 and didn't got any fix.

I very much doubt it, sorry!

VdL 2024 is now two full versions behind the latest release so it is considered a Legacy product.

Jeff
Forum Moderator

@emmrecs

Hmm,, I wonder if 2025 is a good year for VDL (MS)?

AndyW

Ps - It's not looking good so far though.

edit - out of curiosity, do the new Nvidia drivers actually work correctly with this patch?

@me_again

Hi Andy,

I suspect VdL 2025 is viewed in the same light as 2024 by Magix developers.

I would be delighted to be proved wrong!

Jeff

@emmrecs

I'm sure you're correct Jeff. If they're true to form with past versions, if you want bugs fixed, buy the new version.

Great for sales but not so great for customer loyalty although, to be fair, this problem isn't a bug it's something forced on Magix by a 3rd party.

Ho hum - AndyW

Doesn't look like it's been fixed "to our satisfaction."

Who has already rendered in AVCHD 1920 x 1080p ???

Does the exported video stutter ???

@Marc-Goder

Hi Marc

. . . . Who has already rendered in AVCHD 1920 x 1080p ??? . . . .

Correction:

Since the update - no problems with AVCHD interlaced for BluRay disc - 17 movies of varying length no issues with any of them, 2 BD discs of the 17 movies also no issue.

Both UHD 630 and RTX 2060 GPUs sharing the processing load, and decoding as the RTX series of GPUs do not support AVCHD interlaced encoding.

HTH

John EB

Greetings all,

It's official! MS2025 is now officially abandoned, forsaken, cast out, discarded and other synonyms for forgotten.

To paraphrase the hit parade song "I'm a Believer" by The Monkees, a well known beat combo of the 1960s - "disappointment's haunting all my dreams" 😀

This is on the webpage https://www.magix.info/us/support/?question=466428&category=0&title=why-is-there-suddenly-a-fallback-to-the-cpu-for-hardware-accelerated-exports-via-the-nvidia-graphics-card

"For Photostory deluxe 2026, Movie Edit Pro 2026 Plus/Premium and Video ProX 17, updates have now been put online which fix the problem. Carry out the online update via the Help menu.

No updates are planned for older program versions."

@emmrecs

I would be delighted to be proved wrong!

Bad luck Jeff 😇

It's interesting to note that Magix still use Movie Edit Pro as the name. Hasn't anyone told support yet? 🤓

AndyW

Doesn't look like it's been fixed "to our satisfaction."

Who has already rendered in AVCHD 1920 x 1080p ???

Does the exported video stutter ???

@Marc-Goder,

HEVC does not seem to be affected, but AVC (H.264) exports with Nvidia do not seem to be OK after update 25.0.1.316 (Video deluxe 2026) with Nvidia driver 591.74. When played with Nvidia ICAT, it is very noticeable, but it is also noticeable with other players.

https://app.box.com/s/tfu28gm4pzfr7dzb9cdqrsza2m2fjdu3

I am using latest version of Video Deluxe 2026 20.0.1.316, and I get jerky MPEG-4 exports when using the NVIDIA GeForce RTX 5060 GPU (with the Gamer or latest Studio drivers).  Its much better using the Intel UHD Graphics option (on the i7 14700K CPU), so what is the point of getting an expensive dedicated Graphics card?  
The export works better without NVIDIA and only slightly (ca.15%) slower.  Is there a fix coming to be able to get smooth MPEG-4 exports with the graphics card? It appears to be a compatibility issue!

@john-m33

Have you tried resetting the program to its default settings ?

@john-m33

Hi

. . . . jerky MPEG-4 exports when using the NVIDIA GeForce RTX 5060 GPU . . . . much better using the Intel UHD Graphics option . . .

This difference between the 2 GPU's performance and the jerkiness would suggest that Interlaced video is involved in your projects, either importing and/or exporting. The Intel GPU's do support hardware acceleration for decoding/encoding of/to interlaced video

None of the Nvidia GPUs which support NVENC, including the RTX, support interlaced hardware encoding.

MPEG-4 is the generic name for the file format, it does not tell us what the actual encoding is.

Which export preset are you using, ie the name you see in the top box of the export dialog, and did you make any changes to the default settings?

With respect to the jerkiness, this can occur when there is fast action across the screen or pan shots with Progressive video. How bad depends on the source video frame rate and the export frame rate.

It may also help to know what the actual imported and exported video encoding format/ parameters are.

Either:

• Download and install MediaInfo and analyse one of the clips and post the results, see this tutorial on how to setup MediaInfo and analyse a video clip for all the data required.
  
  OR
   
• Use the online version of Media Info here. Personally I would only use the online version for generic videos which do not contain people.

John EB

You can take any video (progressive), export it in Video deluxe 2026 .316 with Nvidia driver 591.74 as MPEG-4 H.264 with Nvidia hardware acceleration, and—as far as I have tested several times—you will get a jerky result.
It's less noticeable with VLC Player, but you can see it when you play it with other players in Windows 11.
Nvidia ICAT (https://www.nvidia.com/en-us/geforce/technologies/icat/) shows it very clearly.

Just test it out, for example with drone flight videos.

In my opinion, the latest update for Video deluxe 2026, Video Pro X17, and Photostory 2026 has the same problem with MPEG-4 H.264 export with Nvidia acceleration.
I think this needs to be fixed.

Hi everyone

I cannot reproduce any difference in the 'jerkiness' between the older NV driver 581.80 and the latest 591.86..

Test conditions:-

• Source video 50 fps HEVC (h.265) 4K UHD 3840 x 2160 px
• Video has a fast pan, right to left.
• Exporting as 4K UHD MPEG-4 H.264 with Nvidia hardware acceleration enabled first with the old 581.80 driver then repeated with the 591.86 driver.
• I also exported 4K UHD at 25 and 50 fps using the Intel iGPU for comparison
• My laptop screen refresh rate is 144 Hz, - I mention this because if there is a 'close' mismatch of refresh rate compared to the framerate, eg 60Hz cf 50 fps, you can see jerkiness on playback on pans and fast movement acrosss the screen.

NV exports at 25 fps are visibly jerkier than the original video, this what I would expect to see, however there is no visible difference between the old and new NV drivers.

NV exports at 50 fps have a significantly smaller amount of jerkiness with both the old and latest driver, again there is no visible difference between the old and new NV drivers.

Comparing the NV exports to their equivalent Intel iGPU encoded exports, the NV encoding is definitely adding jerkiness to the video using both the old and new drivers.

The 25fps Intel export has a small amount of jerkiness, this what I would expect to see, compared to the 50fps export which is the same, ie smooth, as the original HEVC source.

John EB

@johnebaker,

Thank you for your efforts to reproduce it.
I will try again later to reproduce the jerkiness and image shaking.
I haven't compared the different Nvidia drivers, but I did notice that with the Video deluxe version prior to .316, there were no visual abnormalities in the H.264 export. With update .316 and the Studio driver version 591.74 that can be used with it, the H.264 exports are no longer as smooth as the original in my opinion.

I exported this video

https://app.box.com/s/rdln3wn1ikq08vjsody5bd03p3w8qs29 (import.mp4)

as follows:

When played back, it looks shaky:

https://app.box.com/s/54fk83j8ktkrsvnas6ye0ibc3votkyfl (screenvideo.mov - recorded with OBS)

@vdl-user-v19

Hi

Using your import file I can reproduce the shaky export.

Analysing the import file it has a Long GOP structure of 250 frames, ie there is only one I frame full image every 250 frames (approx 8.33 secs). Between the I frames are B and P frames, in essence these contain the changes from the previous frame - for more detailed info see this Wiki article.

I suspect it is this that is causing the shakiness when converted, on export, to a standard GOP length on export.

A GOP length of 250 is, IMHO, too long for video containing movement and high detail as in your drone clip.

The recommended, ie 'unofficial standard' is the GOP length should be half (to the nearest whole number) or the same as the framerate.

Does the drone have a selection of recording parameters?

John EB