CPU Pegged

murphy wrote on 3/21/2005, 1:41 PM

I have read many of the threads regarding rendering speed with Vegas. I understand that there are a variety reasons that effect rendering speed.

My rendering speed has slowed done dramatically over the last several days. For example a clip that would take 30 minutes to render now takes over 3 hours
A 6 1/2 minute clip that the only changes I made to it included 5 simple cuts no F/X at all. takes over 30 minutes to render. When I look at task manager it is steadily using 95-100% cpu during renders. It never drops below that

I know that the most likely issue is a virus or adware and I have run several anti virus and adware programs Norton, AntiVir XP, AVG, LavaSoft, Spybot, detection programs and everything in that regard looks fine.

I have an AMD Athlon XP 3000+ with 1 Gig of ram,a an 80 gig sata system drive on a Asus a7n8x-e motherboard. I'm running windows XP pro with service pack 2.

Thanks for any suggestions

Comments

FrigidNDEditing wrote on 3/21/2005, 5:17 PM

SATA's do start to slow down as the fill up - that's all I can think of, assuming it's not the afformentioned things

JJKizak wrote on 3/21/2005, 5:30 PM

My typical 30 minute project wil take from between 2.5 to 3.5 hrs. The CPU usage averages about 60% but cruises from about 55% with peaks to 98%,
.P4-800 HT 2 gig ram SATA not on OS drive.

JJK
.

Liam_Vegas wrote on 3/21/2005, 5:35 PM

I recommend check the usual things.

You mention that you did a test with 6 /1/2 min clips with just cuts only. When you render it should actually just be doing a copy of the frames (no actual rendering at all). This is usually done at faster than real-time on most systems.

If Vegas thinks that is needs to render then that could mean it believes the source format AVI is not the same as the destination format. Check the clip properties carefully and verify that what Vegas thinks it has is what you really know is there.

Have you added any 3-D track motion anywhere in the project (having it anywhere impacts the rendering of the ENTIRE timeline - even areas where there is nothing "active").

Oh... and you are checking this out in a BRAND NEW Veg file right? If you do your tests in an existing Veg maybe that is where the problem is. Just try your 6 1/2 minute cuts/only test in a new Veg (if you aren't already)