I use a separate nVidia GPU. How would I determine if my Intel CPU was involved? Is it possible that the two have conspired against me? Could they work in tandem?
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
Because your system is win7
Because your system is win7
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.
I mean that build424 + win7 will cause that.
The problem is that I need to know that VP16 B424 has closed down saving all my work. Seeing it’s presence still in TM doesn’t reassure me.
I cannot reproduce, Vegas 16 build 424 always goes away after closing it.
Windows 10 PRO version 1809 (*), os build 17763.475, NVIDEA driver: creator ready driver 419.67 (03/20/2019).
I tried with NVIDEA and even tried with Intel UHD 630 selected as GPU acceleration 25.20.100.6444, driver date 19/11/2018
(*) mentioning win 10 is not enough info, as win 10 has many builds over the years which can be significant different in contend and behavior.
I tried also Vegas 15 build 416, but it also does not leave a trace in the TM
Ah-haaaa .. . .
Just to confirm or deny, I decided to open VegasPro15 the most recent build and after closing down the VP15 Project Vegas is completely removed from Task Manager.
To repeat:
VegasPro 15 is removed from Task Manager
VegasPro 16 Build424 is NOT removed from Task Manager.
So, my system is working for VP15 but VP16 B424 is not compliant with whatever makes VP15 compliant. ALSO, using VP15, there is none of those PESKY FireFox files left in my VP15 Temp folder see my link: https://www.vegascreativesoftware.info/us/forum/why-pesky-firefox-files-in-my-vegaspro-temp-directory--115653/
Is this a convergent ERROR with the FireFox unfinished business in my VP TEMP Directory which keeps VP16 B424 still showing as present in Task Manager?
Anybody from MAGIX want/wish to throw me a bone?
This is a long shot. But as you have those "PESKY html" files associated with Firefox do you perhaps have Firefox running in the background and this is stopping VegasPro 16 closing?
This is a long shot . . . do you perhaps have Firefox running in the background and this is stopping VegasPro 16 closing?
@EricLNZ - Good call, but no. I'm starting to consider that this latest build B424, for whatever reason, wished to provide an OPEN FF Link in my Temp Directory.
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?
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.
VP reset ... https://www.vegascreativesoftware.info/us/forum/faq-how-can-i-reset-vegas-pro-to-default-settings--104646/
Agreed, nothing to clap about, but at least your not alone!
Hmm...
I . . . . probably uninstalling and reinstalling.
Yup, done that.
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.
Yup, done that too.
Have you the latest .NET Framework installed?
I have 4.7 - This from July last year.
It may be some combination of your PC system and VP.
Sorry to be boring, but, the previous Build was fine.
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.
This would not prove much. And no I don't have that option.
VP reset ... https://www.vegascreativesoftware.info/us/forum/faq-how-can-i-reset-vegas-pro-to-default-settings--104646/
I've uninstalled and reinstalled? Wouldn't that cover it?
I've uninstalled and reinstalled? Wouldn't that cover it?
Not necessarily, read Chienworks way back.
(Probably won't help here, so just a reminder regarding the good old Factory Reset.)
@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 ) .
Well.....