Building Peaks is HACKING ME OFF at DVinfo.net

Alastair Brown · December 27th, 2008, 03:56 AM

The length of time Vegas is taking to build peaks is just plain crazy.

I'm sitting with a new i7 Processor with 6Gb of RAM and using eSATA, and it's taking forever to build the peaks for even small projects.

Has anybody come up with an explanation as to why the most recent releases of Vegas have become so painfully slow in this respect.

Never used to be like this.

Jeff Harper · December 27th, 2008, 04:35 AM

I agree that peak-building and timeline performance is poorer with Vegas 8 than it was with 7.

This is, I believe, one of those instances where hard drive speed can influence the Vegas experience.

I use a 300MB Velociraptor for projects I'm working on, and the peak-building is much quicker when using that drive.

This peak-building issue demonstrates why I feel fast drives are advantageous when editing video. I strongly feel that the overall handling of Vegas is much improved when using a faster drive. Performance on the timeline is without a doubt much better. Rendering, etc., is not affected, of course, but the overall experience is much more pleasant.

Even the fastest processor cannot overcome sluggish hard drive performance, unfortunately.

I hope you can find a configuration with what you have that will speed things up for you. Otherwise, you might try getting a dedicated fast drive to put current video projects on.

Jason Robinson · December 28th, 2008, 02:24 PM

Even though I have a 2GHz Core 2 Duo system that I could use for editing, the drive performance of a single SATA drive for OS & data, kills me ability to multi-cam edit. So I have "regressed" back to using my 3GHz P4HT system because it now has a 500GB RAID0 for OS / video data. The striped RAID really does help projects open up faster and vegas deals much better with reading multiple DV streams simultaneously when doign multi-cam edits.

Should I be fortunate enough to still be in this business this summer, I may build a dual Opteron system and finally have a dedicated internal drive for OS and a raid for video data. But that is miles and miles away from my current situation.

Jeff Harper · December 28th, 2008, 06:13 PM

Actually Jason with the Velociraptors you don't need raid any longer. I used to run raid 0 but a single Velociraptor is better than two of the old raptors run in Raid 0. Less overhead on the system, performance overall is better and almost no heat. $229 at newegg.

Jason Robinson · December 28th, 2008, 07:00 PM

Quote:

Originally Posted by Jeff Harper

Actually Jason with the Velociraptors you don't need raid any longer. I used to run raid 0 but a single Velociraptor is better than two of the old raptors run in Raid 0. Less overhead on the system, performance overall is better and almost no heat. $229 at newegg.

are those drives the 10K RPM drives?

Jeff Harper · December 28th, 2008, 11:44 PM

Yes Jason. Newegg.com - VelociRaptor

I used to run RAID 0 for both OS and video drives. I find that for me it is truly overkill now. I still have a RAID controller (it's actually an e-SATA controller with built in RAID) but I don't even use it for RAID any longer just as an interface to run e-SATA drives.

Uli Mors · December 29th, 2008, 04:01 AM

Hi,

I found that it totaly depends on the structure of the video files.

While AVI peaks are built up "superfast" , any mpg file (m2ts or hd-mxf) take much longer to demux and build peaks. I brought in a 60 minute m2t (HDV) file and it took awfully long to build up the peaks - it seems not to depend that much on a faster harddrive (I have eSata etc.).

What I do now is to build peaks in a second instance of vegas, especially when I work with several tapes.

A) I work with tape 1 (and cancel building peaks)
B) in the background peaks are built with tape2 (bring down task manager priority for this vegas instance)

Ok, this is heavy work for the harddrive, sometimes I even split these tapes on 2 harddrives for easier work.

Regards

ULI

Tim Akin · December 29th, 2008, 09:03 AM

Yesterday was my first experience with working on an HDV project. When I was ready to work on the multi-cam edit, I starting droping the mt2 files in.....to fast apparantly.....Vegas crashed. My first time working with HDV started off bad.

Jason Robinson · December 30th, 2008, 02:36 AM

Quote:

Originally Posted by Uli Mors

While AVI peaks are built up "superfast"

I've dropped a project's worth of files (~100 clips) from explorer into the project media and had to wait for several minutes for vegas to do anything. Why isn't peak building spawned off in a dedicated thread? The business where it paralyzes Vegas until the peaks are built is a completely stupid behavior that should be a relatively easy fix.

Ron Evans · December 30th, 2008, 09:14 AM

You can of course carry on working while its building peaks, at least that is what I have found. Just don't save. That will stop everything until peaks have been built.

Ron Evans

December 27th, 2008, 03:56 AM	#1
Alastair Brown Major Player Join Date: Aug 2006 Location: Glasgow/Scotland Posts: 626	Building Peaks is HACKING ME OFF The length of time Vegas is taking to build peaks is just plain crazy. I'm sitting with a new i7 Processor with 6Gb of RAM and using eSATA, and it's taking forever to build the peaks for even small projects. Has anybody come up with an explanation as to why the most recent releases of Vegas have become so painfully slow in this respect. Never used to be like this.

December 27th, 2008, 04:35 AM	#2
Jeff Harper Inner Circle Join Date: Jun 2005 Location: Cincinnati, OH Posts: 8,425	I agree that peak-building and timeline performance is poorer with Vegas 8 than it was with 7. This is, I believe, one of those instances where hard drive speed can influence the Vegas experience. I use a 300MB Velociraptor for projects I'm working on, and the peak-building is much quicker when using that drive. This peak-building issue demonstrates why I feel fast drives are advantageous when editing video. I strongly feel that the overall handling of Vegas is much improved when using a faster drive. Performance on the timeline is without a doubt much better. Rendering, etc., is not affected, of course, but the overall experience is much more pleasant. Even the fastest processor cannot overcome sluggish hard drive performance, unfortunately. I hope you can find a configuration with what you have that will speed things up for you. Otherwise, you might try getting a dedicated fast drive to put current video projects on. Last edited by Jeff Harper; December 27th, 2008 at 04:51 PM.

December 28th, 2008, 02:24 PM	#3
Jason Robinson Trustee Join Date: Mar 2006 Location: Boise, Idaho Posts: 1,997	Even though I have a 2GHz Core 2 Duo system that I could use for editing, the drive performance of a single SATA drive for OS & data, kills me ability to multi-cam edit. So I have "regressed" back to using my 3GHz P4HT system because it now has a 500GB RAID0 for OS / video data. The striped RAID really does help projects open up faster and vegas deals much better with reading multiple DV streams simultaneously when doign multi-cam edits. Should I be fortunate enough to still be in this business this summer, I may build a dual Opteron system and finally have a dedicated internal drive for OS and a raid for video data. But that is miles and miles away from my current situation.

December 28th, 2008, 06:13 PM	#4
Jeff Harper Inner Circle Join Date: Jun 2005 Location: Cincinnati, OH Posts: 8,425	Actually Jason with the Velociraptors you don't need raid any longer. I used to run raid 0 but a single Velociraptor is better than two of the old raptors run in Raid 0. Less overhead on the system, performance overall is better and almost no heat. $229 at newegg.

December 28th, 2008, 11:44 PM	#6
Jeff Harper Inner Circle Join Date: Jun 2005 Location: Cincinnati, OH Posts: 8,425	Yes Jason. Newegg.com - VelociRaptor I used to run RAID 0 for both OS and video drives. I find that for me it is truly overkill now. I still have a RAID controller (it's actually an e-SATA controller with built in RAID) but I don't even use it for RAID any longer just as an interface to run e-SATA drives.

December 29th, 2008, 04:01 AM	#7
Uli Mors Major Player Join Date: May 2006 Location: Germany Posts: 565	Hi, I found that it totaly depends on the structure of the video files. While AVI peaks are built up "superfast" , any mpg file (m2ts or hd-mxf) take much longer to demux and build peaks. I brought in a 60 minute m2t (HDV) file and it took awfully long to build up the peaks - it seems not to depend that much on a faster harddrive (I have eSata etc.). What I do now is to build peaks in a second instance of vegas, especially when I work with several tapes. A) I work with tape 1 (and cancel building peaks) B) in the background peaks are built with tape2 (bring down task manager priority for this vegas instance) Ok, this is heavy work for the harddrive, sometimes I even split these tapes on 2 harddrives for easier work. Regards ULI

December 29th, 2008, 09:03 AM	#8
Tim Akin Major Player Join Date: Nov 2008 Location: Newbern, TN Posts: 414	Yesterday was my first experience with working on an HDV project. When I was ready to work on the multi-cam edit, I starting droping the mt2 files in.....to fast apparantly.....Vegas crashed. My first time working with HDV started off bad.

December 30th, 2008, 09:14 AM	#10
Ron Evans Inner Circle Join Date: Mar 2003 Location: Ottawa, Ontario, Canada Posts: 4,220	You can of course carry on working while its building peaks, at least that is what I have found. Just don't save. That will stop everything until peaks have been built. Ron Evans