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.
I first thought also that it was an Intell AMD driver, because the error message I got sometimes also said something about an nvami.inf_amd64....... driver. With my solution for older Nvidia drivers as told here before resetted those files by this ones of dec 2018 and it turnes out to be Nvidia drivers
Oh?! - So it mustn't have been working thru VP16 up to this last build? No? Well wrong. It's only been since this last Build424 of VP16 that this residual has happened. Oh yeah, Marco has this and he's on WIN10.
@lan-mLMC - So, and until I hear it from MAGIX directly, the Build424 has placed me in this position.
@bitman - Thanks for your feedback. And no, whatever I had in the previous Build, which worked, remains the same here, now in B424. In fact I’ve been using NewBlue Titler Pro, which is a Plug, and after “closing” VP16 B424, NBTP can be seen going away.
If you are win7 and you are using build424, vegas pro build424 will remain in background of your system even if you have closed vegas pro buled424. This maybe a bug or that the vegas' developor want to do something in background of your system.
@Former user - Cheers for the Link, which I had read previously and unless I’ve missed something there’s nothing there to make me clap?
wrote on 5/8/2019, 5:42 AM
Agreed, nothing to clap about, but at least your not alone! I had the issue a good while ago, gone now, can’t remember what I did to get rid of, probably uninstalling and reinstalling.
Does it still stay in task manager if you close using file/exit or Alt F4 instead of the 'x' in the top right of form. Also try disabling AV software temporarily, obviously stay off line, while opening then closing VP.
Have you the latest .NET Framework installed?
It may be some combination of your PC system and VP. Can you try VP 16 on a different machine? Its not necessarily the latest build thats at fault as on my PC and laptop, no issue.
@vkmast - Yeah, in the last 1.5 hours repeated the 2-Finger Salute and I updated my .NET to 8. However, the 2-Finger Salute DID find a VST that was AWOL when loading, so I needed to ZAP that and VP loads much faster than before, but VP still remains in TM. And those PESKY FFs are still created and remain.
Exactly same here , Grazie , 424 remains in memory . Just opening and closing without loading any media and vegas pro 16 and errorreportlauncher remain in memory . Opening and closing 5 times and there is 5 times vegas pro 16 still there ( and one time errorreportlauncher ) and waiting 20 minutes , still there .
Shutting down results in still program in use ( vegas pro 16 ) , then win7 closes it , and only then shuts down .
Does NOT happen wih version 307 ( on same workstations ) which (at least here ) performs much better in regards of realtime previewing .( the vegas pro 16 sample project and others ) .