Good question, and I don't have any way of testing because mine crashes right away with it turned on.

Perhaps drawing a line in the sand between preview processing and render isn't the best way to look at it, and my statement is open to revision.

Good question, and I don't have any way of testing because mine crashes right away with it turned on.

@Musicvid - Yes, indeed, but that would still not supply any empirical evidence only experiential evidence. We need major input from MAGIX.

Perhaps drawing a line in the sand between preview processing and render isn't the best way to look at it, and my statement is open to revision.

@Musicvid - Indeed. And again we’re kinda “spitballing”, seriously requiring URGENT input from them that knows. This is an ancient Crusade of mine that ALL parties involved should really Engineer-Up their advice on this GPU <> CPU fandanglement and come clean. Leaving us Grunts to hack our way through this particular Jungle is unfair. 😒

I’ve got MOCHA, Mercalli and TWIXTOR, maybe some more, that all utilise GPU to show and/or their internal render engine to Preview. Would their ability to access my GPU also be removed

@Grazie

3rd party plugins work on their own and are not affected by turning on or off GPU acceleration for previewing in Vegas preferences.

Those plugins usually have their own internal GPU on/off switch. In Mocha, it should be in preferences, in Twixtor, it's a drop down menu in the plug in parameters window.

3rd party plugins work on their own and are not affected by turning on or off GPU acceleration for previewing in Vegas preferences.

@GJeffrey - O..K... How do you know?

Those plugins usually have their own internal GPU on/off switch. In Mocha, it should be in preferences, in Twixtor, it's a drop down menu in the plug in parameters window

@GJeffrey - Sure, I know exactly how to get at them in the Plugins. And again, how do you know that switching off GPU in Vegas, then also doesn't switch them off as well in in the Plugs? You’ve proof of that?

I found the topic very strange. Instead of finding and fixing GPU related issues in VP/plugins (as Nick's article suggests) it recommends to turn off GPU in VP (so processing would be slower) and then use GPU in encoder (to speed up render but degrade rendered quality). I could not find worse advice even if I'd like to.

@Grazie sure, VP cannot prevent access plugins to GPU. You can test yourself if you like in Mercalli (turn off GPU in VP, turn ON in Mercalli, do not analyze & render -- you'll see GPU version of message) or in NeatVideo (turn off GPU in VP, add NeatVideo, configure it to use 1 CPU + no GPU, render & measure time, configure it to use 1 CPU + GPU, render & measure time)

If turning off hardware preview acceleration gets me and one other Intel owner working, when we were not before, it is not the worst advice, by definition.

The opportunity to turn it back on if it doesn't help is implicit.

Please register the fact that I don't render anything with QSV. And leaving it enabled does not crash my program, nor have I advised either way. Do refrain from putting words in my mouth again.

Seems like I accidently bumped off a scab; of course Magix owes us a fix, the most sensible being to leave it off by default, or put it in Deprecated Purgatory, until it is working for the mass of users.

And someone will benefit from the advice, sans editorials. Have a Ginger Beer and take a long Solstice nap.

There are a lot of people using GPU processing successfully with Intel chips, your case seems to be a rare one. Have you tried updating the intel onboard GPU's drivers? Or disabling it and using a discrete GPU?

I'm pleased that my suggestion does not apply to either of you. You both have been so wonderful over the past year, and are valuable contributors to the forum. Maybe after the holiday season, which has become an altered state in itself, we can pick up the discussion again under a more worthy topic.

And thanks once again for making me think, @Grazie !

I'm pleased that my suggestion does not apply to either of you. You both have been so wonderful over the past year, and are valuable contributors to the forum. Maybe after the holiday season, which has become an altered state in itself, we can pick up the discussion again under a more worthy topic.

And thanks once again for making me think, @Grazie !

The only thing I can provide is that my laptop's GPU is the weak point of my system. It's an Nvidia 940MX, where I feel my CPU is one of its stronger points, an Intel i7 8550U. I tend to work with 1080p video files. When I turn on GPU acceleration in Vegas, my preview seems to stutter often on projects with simple cuts and minor color corrections. When I turn GPU acceleration off, then the same project plays back smoothly in preview. Therefore, with my system things definitely seem to just work better with GPU acceleration set to CPU.

So my theory has been that if you have a higher performance GPU (which I don't), then maybe you benefit by having GPU acceleration turned on and if you don't, then it is best to leave it off. However, that's just based upon my personal experience with my current system and hearing others who have higher performance GPUs stating it works better for them with GPU acceleration turned on.

Continuing with my theory, I am assuming the default of having GPU acceleration turned ON is based upon most people doing professional video editing work would be working on a system with a higher performance GPU.

My favorite phrase in the compu-sphere (taken, of course, from the automotive world) is YMMV, ('your mileage may vary' for those on the other side of the planet, or too young, etc.). The hardware connection/suitability is always a huge factor in the user experience; unavoidably, I'd say.