Prior to this build, VP behaved itself and "Left The Building". But now, according to Task Manager it's remaining in memory, like a bad date or bad smell that . . .. far too graphic. OK, Brethren and Sistren - what gives?
Yup, still there, well after Closing Time at Pub MAGIX.
While one (or several) VP processes remaining in the Task Manager, are you able to start a new session of VP? This does not work here and for me this is the main annoyance with it. Before I can start a new session of VP I first have to kill the remaining process in the Task Manager. And using a CMD batch file to kill that process does not work, unfortunately.
"So you’ve lived with these nonsenses, for how long?"
Don't know exactly, maybe a year. I think on my system this happened with one of the Intel driver updates. But it only happens with certain types of H.264 media, though I never found out which particular H.264 property causes the issue.
I managed to found a solution on my laptop (the only place it happened for a long time) to start the program not with the Nvidia GPU but with the Intel 630 GPU or switch to the last available updates for my Nvidia provided by Asus (driver version 399.24) and than I can start and stop again normal without any hangs of the program in memory.
VP is removed from the taskmanager. Windows 10 latest build. Looking at the posters signatures (where available), it seems that the issue as far as I can tell from the posters is limited to windows 7...
Looking at the posters signatures (where available), it seems that the issue as far as I can tell from the posters is limited to windows 7...
@bitman - Yup! Thanks confirming what I’ve been thinking. This Build and only this Build is doing this. The last Build was rock solid. Somebody from MAGIX needs to confirm or deny if the installer was Q&A for Windows 7 too. If it hasn’t been or that MAGIX is no longer supporting Windows 7 then we’d need to know.
Yes, it's been Windows 10 all the time I had/have this issue appearing. In my case it is very likely the Intel graphic driver causing the issue which is why I asked if you also use a Intel graphic system. So it seems there are similar problems triggered by different causes.