Renders just recently slowed down & became glitchy

otter wrote on 2/14/2015, 5:44 PM
Have been rendering for almost a year now with Vegas Pro 13... And haven't had too many issues. But I have noticed an inconsistency in rendering the same projects. What use to render in five minutes started taking 20 minutes. What use to render flawlessly, now started having occasional glitches. Now the glitches have increased the last few days and become constant.

On the audio side, noticed some odd dropout in sound. Also noticed that sometimes the audio would appear to be normal in the waveform, but I would hear occasional glitches to different audio from a completely different spot and a completely different track while previewing in spots. Would even hear a few little random noise glitches as well… Yet when I rendered just the audio as an MP3 or.WAV file...everything would be fine.

It seems that problems just continued to compound on the video side the last few days until it became unbearable.

I did notice that my C Drive which has all my programs on it was getting pretty full a few days ago as well and figured that maybe this was causing a problem. I went through and cleaned up a bunch of extraneous files and had windows to a disk cleanup. Still was having issues and after doing research… Was worried about RAM, so followed other suggestions and went into virtual memory and changed it from automatic to custom size. Initial size 32 768 maximum size 40,000. That's didn't seem to do the trick either. I got the most recent drivers for my M audio M box Pro. That didn't seem to change anything. I also played the game of holding ctrl shift down while starting Vegas and deleting all cach. That didn't help.............. Held shift while restarting the machine to see if there is any RAM leaks........... Didn't help............... tried to restore the computer to all the previous dates that it had listed. It wouldn't allow me... Now I'm COMPLETELY at my wits end ;(

So, I uninstalled Vegas 13 (build 428) and re installed it. Now the renders say they will take 24 hours for what used to take a minute. AARGH! :-(

Please somebody help me!

Greg

Comments

winrockpost wrote on 2/14/2015, 6:25 PM
........tried to restore the computer to all the previous dates that it had listed. It wouldn't allow me......
uh oh,,, do not want to sound like a fan boy...but doubt its a Vegas issue
edit system hooked up to internet. If so virus check?
maybe roll back audio drivers..., see what you get
good luck, wish I could be more helpful ..
PeterDuke wrote on 2/14/2015, 10:57 PM
This is the time I restore my system to the days when things worked properly.

Make sure that you make an image of your system for safety's sake before you do, and so that you can restore any data. You will need to re-install any subsequent programs, but watch out in case one of them causes a conflict and re-introduces your problem.

You do have system image backups, don't you?
dxdy wrote on 2/15/2015, 8:10 AM
When was the last time you vacuumed out your machine? Rendering is often the biggest load your machine will see, and you may be having temperature issues.
pilsburypie wrote on 2/15/2015, 10:48 AM
Can I just say NOT TO vacuum out your machine. I agree that a years worth of dust and crap over the fans and cooler could reduce their ability to cool the CPU etc and this could have an effect on the stability of the machine.

The way to clear the dust is compressed air, either from a compressor or a can. A vacuum cleaner builds up a load of static energy which can fry circuits very easily. I personally blame exactly this for bricking a machine I had a good few years back.

PeterDuke wrote on 2/15/2015, 5:07 PM
A vacuum cleaner builds up a load of static energy

Why would a vacuum cleaner do that but an air compressor wouldn't? It is just a flow of air in both cases. Also, the maximum pressure you could exert with a vacuum cleaner is 1 atmosphere (and likely much less than that), but an air compressor could be much greater, with a greater risk of damage. And further more, the vacuum cleaner collects the dust whereas the air compressor disperses it to who knows where.
riredale wrote on 2/15/2015, 10:25 PM
This cleaning business is something that has been discussed multiple times over the years.

I can't imagine using compressed air unless I moved my box outside--it would truly create a fog in my office that would settle on everything.

But I vacuum out my PC case maybe twice a year, and with dramatic results on CPU temps. I guess it's possible that static electricity could be generated, but so far no issues.
pilsburypie wrote on 2/16/2015, 6:42 AM
Just something I have read many times on computer forums. Fully agree that cleaning in situ with compressed air will blast dust over your office and other stuff and that it needs to be done outside. Feel free to vacuum at will but after my experience (which could have just been coincidence) and from info I have found, I most certainly wouldn't vacuum.

Not that this article is the word of God, just the first that comes up in "should I vacuum my PC" in Google. Many more where that came from.

http://www.pcgamer.com/should-i-vacuum-my-pc-ask-pc-gamer/
otter wrote on 2/16/2015, 4:17 PM
Tried to restore several times... and it appeared there were several images available from the times when it was working great,yet, every date I chose... the computer either rejected immediately... or went through the who process and said that it wasn't able to return to that date after all.

Also ran several antivirus checks and a malware test and cleaned anything that looked suspicious... still no change.


PeterDuke wrote on 2/16/2015, 11:12 PM
I didn't mean windows system restore. I have never found it useful in time of trouble. It is a sick joke.

What I meant was a system restore from an image you created of your C: drive using backup software such as Acronis. If you haven't been in the habit of doing system image backups, then slap yourself on the wrist and start today.
otter wrote on 2/20/2015, 7:38 PM
So here's what I found. Talked to my IT friend and he said to open task manager (ctrl-shift-esc).
Then to click on the performance tab… Then to go to the bottom and click the resource monitor… Then click the disc tab of that and look at the queue length on the far right next to the green graphs. He said that a typical running disk drive should have a queue length of .01 normally… Up to .05 when it's working hard.

He said if the numbers are much above that your hard drive has issues. Well... it was running at 100 times the hard working level at 50.00. It looked like there was plenty of space left on the drive and when I did a defrag test… It said it was only 3% fragmented.

He said to go ahead and do a disk defrag anyway. That made all the difference in the world. Well at least a lot. I've been able to render without hiccups and the computer seems to be running much smoother. I also just ordered an SSD drive which he said should work better with video editing and never needs to be defragged. We will see…

Thank you for all your suggestion's!

Greg