Nothing I do fixes the issue. Is there a way to back out of / uninstall this update?

@Wayne-McIlvaine

Hi,

In Program Settings, Device options, what do you have set for Hardware Acceleration(Import, Processing, Export)?

What options do you have?

I had to change mine for Processing to Intel Graphics to get VPX13 to playback smoothly.

John CB

@Wayne-McIlvaine @browj2

Hi John.

I don't think Wayne has an inboard Intel GPU and I am not having as much (but some) trouble in MEP with the update running and purely selecting nvidia for all processing requirements on a much lower end nvidia card.

There could be differences between the effect of the update between VPX 13 and MEP 2022 but I hope not. An RTX 3080 should be more than able to cope.

Hi Wayne.

Try playing the whole project through once without stopping or restarting it and see if the second play through is steady. (You need to have loop playback enabled) If the second play through is steady then close the program. Wait a minute or two and restart VPX and load the project again. This time open Task manager before playing back. Watch the NVMe drives to see if either maxes out while the programs stutters or momentarily freezes.

If that is the case then yes, I'm having the same issue but it settles down after the first initial play through but I've had this with MEP 2022 since it's release on more demanding projects.

Ray.

@Wayne-McIlvaine

Hi,

In Program Settings, Device options, what do you have set for Hardware Acceleration(Import, Processing, Export)?

What options do you have?

I had to change mine for Processing to Intel Graphics to get VPX13 to playback smoothly.

John CB

Hi John, here is what my settings look like. The only other options I have are "CPU" and "Microsoft WARP Device." As I mentioned, this all worked perfectly smoothly minutes before the update, and now is super choppy, especially so during video clip transitions, such as crossfade. Nothing I do makes the chop and stutter go away.

@Wayne-McIlvaine @browj2

Try playing the whole project through once without stopping or restarting it and see if the second play through is steady. (You need to have loop playback enabled) If the second play through is steady then close the program. Wait a minute or two and restart VPX and load the project again. This time open Task manager before playing back. Watch the NVMe drives to see if either maxes out while the programs stutters or momentarily freezes.

If that is the case then yes, I'm having the same issue but it settles down after the first initial play through but I've had this with MEP 2022 since it's release on more demanding projects.

Ray.

Thanks Ray, I tried that, but no change: it's still, and always super stutter-y. My SSD drives remain at 1%, but my GPU spikes heavily at each crossfade transition, and is much higher overall than it was before this update.

Note the spikes on the GPU; each of those is a crossfade.

Do you know of a way to uninstall this update?

Thanks.

@Wayne-McIlvaine

Hi Wayne.

I notice you are not using proxy files and are not bothering to reduce resolution of the monitor.

You should try that first. In the Movie Settings tick the use / create proxy files box and allow the program to create them. Then make sure the lightning symbol in the monitor panel is turned on. It should turn blue. To check which features are on within that blue lightning box right mouse click it and tick each one you need.

Ray.

@Wayne-McIlvaine

Hi Wayne.

I notice you are not using proxy files and are not bothering to reduce resolution of the monitor.

You should try that first. In the Movie Settings tick the use / create proxy files box and allow the program to create them. Then make sure the lightning symbol in the monitor panel is turned on. It should turn blue. To check which features are on within that blue lightning box right mouse click it and tick each one you need.

Ray.

 

Thanks Ray.

As I have said, this was not happening before the update, so I'm not sure why it would be required to achieve acceptable performance / behavior now, but I followed you advice and spent over 90 minutes letting VPX create proxies for the clips in this project, and reduced the resolution of the monitor, and they had absolutely no positive effect. The preview still stutters like crazy, and the monitor preview quality is now unacceptable for the type of video I am making. It also now take 4 times longer to export the video. I'll reach out to Magix support and let you know what they say.

Thanks.

@Wayne-McIlvaine

Hi Wayne

What's with all the activity 76.2Mbps on your ethernet graph in TM and none on any of the SSD's? Are your source files on a connected NAS or a disc on another computer?

@CubeAce @browj2

John - I find setting processing to the Intel GPU gives me a better result in MEP2022 when playing back that 5 way trapezoidal collage with UHD25P H.264 clips.

With the GTX1060 for processing I am also getting the preview of some clips in the collage, and after the collage, going black, with some thumbnails in the timeline showing black - requiring restarting the program to bring back the images. Seems to happen quite randomly mainly with the Nvidia selected although I think I have seen an improvement with the .116 patch which says it has improved memory allocation with lower end video cards.

Ray - I see a lot of activity (400MB/s) on my C: SSD drive for some minutes after loading a project or sometimes even just starting the program even though only the program is on C:\ and the files are on an HDD. Resource Monitor shows it is writing to a cache but what, I am not sure. Seems odd!

Peter

Hi Wayne

What's with all the activity 76.2Mbps on your ethernet graph in TM and none on any of the SSD's? Are your source files on a connected NAS or a disc on another computer?

That was just iCloud Photos momentarily downloading a couple pictures. All the source files are local on my SSDs.

@Wayne-McIlvaine

Hi Wayne.

I know this will not help you at the moment but on some previous update notes and on this page there is a warning not to update the program until you have completed any projects you may be working on. There is a danger of them corrupting or not working correctly.

Why this is could be anyone's guess. Magix test systems use both Intel GPUs and nvidia, and there may even be a Ryzen / Matrox combination somewhere but they are always trying to spread the workload as much as possible.

One thing I have noticed about transitions having both GPUs is that during a transition the Intel GPU does more 3D rendering and the corresponding amount of nvidia 3D rendering drops.

Now,none of us know what tweaks Magix does to each update or how it will effect or not effect a given system. That page I link to above also has a link you can report problems to that they will periodically have a look at. So you could mention your problem there. Not that doing that will help you short term.

So if they are playing around with memory that could involve storage as well. They also don't mention which memory, ram or vram. We are left with a guessing and observation game.

So everything I now write below has sometimes helped me or hindered me or made absolutely no difference.

It could be the program can't now access the files as quickly from the reported positions the data is said to be located at. One way around that could be to export the project to a new location including a copy of all the source files so there is little doubt the program now knows which blocks of storage to read and might be able to access them faster from the new folder. Especially if you defragment the drive prior to exporting the project as the files will be written to contiguous data blocks on the drive. Then open the project from its new location. If it does you may be able to delete the old location to free up disk space.

Or

It could be the resources of the program are being used in a different way and putting too much data through one part of a particular system so it may be worth changing the import setting from nvidia to CPU (as you have quite a strong CPU) That will make your CPU work much harder but it is hardly ticking over at the moment and may relieve some of the workload on your nvidia card. Changing the import setting to CPU will increase the amount of preloaded data to the motherboard ram though. That may or may not become a problem.

Your nvidia readout though was nowhere near maxing out . It will flat-line against the top of the graph for some distance when that happens.

Other times I have deleted all H0 and HDP files from a project using windows explorer and then reloaded the project. New files are then made by the program and replace the old ones. Sometimes that clears up problems.

Lowering the audio buffers sometimes helps reduce stuttering on playback but you may have to increase the amount of sample blocks to compensate if the audio playback is not clear. Sometimes the price of doing that will be a delay between pressing the start or stop buttons and a response from the program.

You could also remove the program and reload it and not update the last update package. That doesn't always work either.

Using proxy files or reducing the resolution for playback is no real hardship. It doesn't stop you from doing anything but can be inconvenient. If you wish to say adjust sharpening or colour saturation just turn the lightning symbol off while you make the adjustments. I don't think I adjust anything with the video playing but when it is static. I'm assuming you are making such adjustments or there would be little to complain about using it.

The programs monitor size if expanded or shrunk from the default setting can produce problems. Possibly the calculations to draw the video frames when not displayed as say a quarter or half the actual screen image size may need additional calculating. I don't know for sure but have noticed it can have a detrimental effect at certain sizes. If you have the monitor on a second screen then try it in its default position and size, within the main program on one screen. I personally find on my system that keeping the monitor within the main program and placing the timeline editor on the second screen less stressful on my system. Results could vary from system to system.

Sometimes, as a project increases in size and complexity I force a pre-render across the whole length of the timeline just to get a smooth play-through but alter one little thing and the whole timeline has to be pre-rendered all over again so can be time consuming and tedious. You can change the timeline view to show a half waveform or less individual frames in the video objects to reduce the project workload.

The main thing for me though is learning that each update or upgrade may at any time render the program less effective than the last one due to the increased demand on a component that may not have been previously stressed or skip an update that has caused additional problems and wait to see if the next offering cures that.

That the warnings on the specification page are explicit even if the language tries to tone down the drawbacks of failing to fully comply.

That if other people can use the program without your specific problem then the problem is probably more hardware related than program related or possibly you are missing a driver update or relevant Windows update, or your source files may be more demanding than theirs. Even possibly a potential hardware failure like a failing drive. Even background tasks running can have an effect.

This is why fault finding and solutions can vary or be difficult to resolve. One solution may not be successful on the same problem on a different system.

@Scenestealer

Hi Peter.

Yes. When loading a project I can see ram usage still creeping up after the project seems to have fully loaded.

Spikes in the relevant drives and CPU as a project starts to play and also at specific point on the timeline.

Expanding the timeline or shrinking /expanding the track views so than more of less frames come into being have little effect on addition ram being loaded or dropped.

Disc reads or writes don't always start or stop in sync with use of the playback controls. Sometimes activity can go beyond the project loading times. I wonder if there has been a refresh of the offerings on shop site? That has been know to continue loading for some time in the past. Maybe that goes to a disk cache?

One thing I have noticed is that I don't get the images of files if I look at a new import destination after the program has been running for a while. Icons don't always load properly when switching views in the effects section. All I get is a generic icon to represent all the files.

All I can say is the good Magix development team giveth, and the Good Magix development Team taketh away. 🙏.

Ray.