My Vegas11 doesn't slow down my computer anymore

Paul Fierlinger wrote on 1/5/2012, 7:04 PM

I know a few people were having this problem with Vegas11's build 511 and at one point updating my Nvidia driver seemed to have fixed it, but eventually the mollases dripped back. I had my IT finally take a look at my computer and he decided that it might be Vegas 10 which I still kept in my computer that's conflicting with 11 so he uninstalled it.

Once he did that, none of my graphics programs (TVPaint etc.) would open anymore showing a pop-up that the msvcr.71.dll was missing. My IT downloaded a new one and all my programs leaped to a new life I don't remember them ever having. I e-mailed my IT asking to describe what he had done so that I could share this with others here:

"it's highly possible the new vegas installed the dll which may have caused the problem and when I uninstalled the old vegas it removed that dll which made tvp cry.
so have those having the same problem uninstall the old vegas, and download the msvcr71.dll and copy it to the system32 and syswow64)
I checked my windows 7 pc's one doesn't have a syswow64, my theater pc does."

I hope this might help others.
__________________

Comments

Jøran Toresen wrote on 1/5/2012, 7:11 PM

And where can wheredownload msvcr71.dll? And why is it needed?

Jøran

Paul Fierlinger wrote on 1/6/2012, 4:23 AM

I'll ask my IT and get back to you.

ritsmer wrote on 1/6/2012, 4:46 AM

Your post gave me the idea to run the Windows system file checker:

go to Start, All programs, Accessories

start Command Prompt as administrator

type sfc /SCANNOW

it runs for some time and if faulty system files are found it (tries to) recover them and gives a resulting message at last asking you to reboot.

On my machine it found several faulty system files - and would probably also have found your mentioned file it it were faulty/missing on my machine.

Maybe some faulty Windows system files are partly the reason for some of the Vegas problems.

For people who are not very familiar to Windows internals I would advise to run the system file checker instead of trying to download and replace some of the extremely sensitive dll's from more or less original internet sites.

More about it from Microsoft here: http://support.microsoft.com/kb/929833

Former user wrote on 1/6/2012, 7:53 AM

Ritsmer,

Interesing. I ran this on one of my computers and no faultts. I also have not having the problems that others are having runnning Vegas 11. The only bug I have confirmed is the effect keyframe bug.

How would these files get corrupted?

edit: I have now run it on both of my computers, no issues and both run Vegas 11 fine.

Dave T2

ritsmer wrote on 1/6/2012, 8:50 AM

Dave T2 - sorry I can not explain this precisely - but some programs seem to come with their own more or less modified versions of the internal Windows dll's - because using such dll's may grant other or faster functions than obtainable using the standard ways of Windows APIs.

When these special versions are not quite what Windows or other programs expect - then we have the so called "dll h_ell".

Interesting, however, that on your machine the dll's are healthy - and - Vegas runs...

Paul Fierlinger wrote on 1/6/2012, 9:45 AM

I got the reply from my IT :
http://www.addictivetips.com/windows-tips/fix-msvcp71-dll-and-msvcr71-dll-missing-error-in-windows-7/

you needed it because tvp said it was missing after we uninstalled vegas 10.

be aware this worked for you and may not work for them.

For your info on this forum, TVPaint is an animation program specializing in 2D animation. It has many functions similar to an NLE -- namely, a Preview window and timelines for audio and video.

dxdy wrote on 1/6/2012, 11:23 AM

This is kind of rambly, but ...

Back in the day (late 1980's) I had a contract to write a program for a consumer software company. It used primitive graphics - just simple line drawings. The program was written in Clipper (!) and my customer insisted it run on TRS80s, as well as all the clones that were floating around back then.

The graphics portion of the application used a 3rd party module, and performed well on CGA, EGA and some monochrome cards. Except for the TRS80. The TRS80 was a nightmare.

I finally wrote a hardware and software sniffer, that poked all the bits and pieces that seemed important, and made a nice printout of what it found. With this information, our support issues diminshed greatly.

Perhaps SCS will come up with a similar utility: Memory, GPU model and its memory, Windows patch level, critical DLL versions, etc., etc., I suspect they are dredging a lot of that information out and shipping it in the crash reports.

I know this won't kill all the problems people are having. But Vegas is obviously drifting away from the "runs on whatever hardware gets thrown at it" model. Obviously the extreme example is FCP, which can only run on parent-company's Macs, but Adobe does it, too (in fact the reason I dumped Premiere and moved to Vegas 6 years ago was something on my machine was incompatible - but they couldn't tell me what - HDD, video card, whatever... and I got sick of trying to figure it out). Now I buy new computers and accessories with the knowledge I glean here on the forum, it has made my life so much easier.