-
Rending Issues / how to stabilze your system
Background: When I transitioned from SD to HD after a 1-year sabbatical from editing the arm-wrestling required was staggering. Heck version 8.0 wouldn’t even recognize my HF10 files! Below I highlight the steps required to get an XP HOME 32-bit, service Pack 3, dual core 3.2ghz with 2GB of memory stable. It was a long strange trip.
1) Split your paging file over multiple drives. Ensure it’s custom, with a 1.5X memory size for initial and 2.0x memory size for maximum. Use the same setting on each drive,
https://support.microsoft.com/kb/307886
2) End any and all unnecessary processes particularly firewalls. When I’m in this mode I use enditall to ensure I’m at the baseline I want.
https://enditall.en.softonic.com/
3) Defrag your drive using diskeeper 2010 till there are no issues on any source, target or operating system drives.This was the last step that allowed me to stabilize my system. Months prior I defragged the drive to healthy and it didn’t solve my problem. Alas after a 1/2 dozen fixes in between, including an upgrade to 10.0, it was time to revisit this. Don’t get complacent figuring your-good rending and sourcing from external drive(s) that are defragged and in good health, C-Drive still needs care and feeding. I’m pleased to say I can render highly compressed (AVCHD) to highly compressed (WMV) with no issues in two separate three-hour renders.
The latest version of diskeeper is leaps-and-bounds above the last version I used on my prior editing system in 2007. Two huge improvements make this a must have for my editing bay.
a) Invisitasking – Defrags system even during heavy traffic using active system resources. When you run manual scans you can see diskeeper pausing and starting as Vegas renders to disk. This isn’t a typo I was running manual scans during rending while copying large files to my c:drive and destination drive for testing purposes.
b) IntelliWrite – Prevents 85% of fragmentation before it’s written to disk.
They have a fully functioning 7-day trial you can use to flush your system clean.
https://www.diskeeper.com/Diskeeper/professional/professional.aspx
4) Check your system logs whenever you have a hang or crash. You must resolve any issues that are occurring. When your in this mode it takes time and effort, so keep plugging away. Common issues are memory, disk and services related. So help me God I had an issue with Media manager where I could see in the system log that it was overclocking my Dual Core CPUs just before my render hung! Had to completely uninstall it from Vegas and kill several services to move forward. Good news, media manager in 10.0 is fine.
Every issue I found and resolved was using the steps above, including but not limited to netframe work revision, bad HD, Windows service issues and virtual memory (VM) errors -including system hangs at the exact time the system bumped up VM!)
Cheers
~Just because you can doesn’t mean you should~
-
1 Reply
-
Crazy man… Never needed to do any of that. I suggest 2 gigs ram per core. Then Vegas will not run into the Swap file… That is the most stable possible. Vegas only uses 5 to 10 megs a second while rendering. HD’s are not the sourse of issues. Perhaps you have bad codecs installed… Many generic aps like FFDSHOW can mess up rendering stability.
Reply to this Discussion! Login or Sign Up