Major performance issues

[badllarma]

Ok installed 5.2 update and the PC is taking forever to do anything in VTedit, so I unisntalled the VT 5.2 and reinstalled VT 5.0 and still having MAJOR issues for example I've brought in a previously made AVI file (PAL, but NOT HD, to test) tried toplay back and it just cannot play it back at all at full speed.

So I've just tried the force render filter and it's just taken 9 mins to force render 6 mins of footage!!!!!

System is Windows XP SP2
4 gig of RAM
Quad Core Q6600 2.4 GHz

any ideas? I had no proibelms at all unti I installed 5.2b :eek:

[ted]

I don't think you should be having that much difference between 5.0 and 5.2.
In fact, I'm pretty sure the code was streamlined to give better performance in 5.2.
Something is not right. Especially if you are now having issues with 5.0.

Maybe a GFX card driver update is needed, or sometimes the latest driver will create issues requiring going back to a previous version.

Your system sounds decent, but there is a lot more to computers than what you have supplied info on.
Any new software installed?

[badllarma]

Hi ted no nothing new installed at all what I am getting is bad audio issues as well (it never rains!!) because of the speed issues I've been using the render filter went and had tea and left it going so it would be ready for edit when I got back.
Arrvied back at my desk click play no sound?? and video is still pretty slow still as well. I've check back ground programs runnignand nothing is out of the ordanary??

No software been installed at all for months probelms only started after the install of 5.2 I've tried uninstall and reinstall but still having same issues?? I'll have to contact Newtek Europe on Monday good job this is not a rush job!!

[badllarma]

For anyone haveing simlar issues I did a full unistall and reinstall of Windows XP and then VT to 5.2 and the problem seems to be solved. BTW Newtek Europe told me not to up date XP to SP3 with the VT on the system.

[ted]

What a pain. But at least it's going smoothly now.
I wonder what the issue is with XP SP3?