Comments

Steve Grisetti wrote on 8/29/2013, 9:18 AM

YOu've got plenty of power, RAM and video graphics umph.
First I'd try matching the project properties to the video specs. That will make everything run more efficiently.

Since MOVs are very non-specific in their format, you may need to open one of your videos in Media Info or G Spot in order to see the resolution, frame rate and codecs used by the file.

You can probably use the Match Video Properties to Video tool to match your project to this video, assuming it makes up most of your video.

And, since you're mixing formats, you may want to Selectively Prerender Video (under the Tools menu) so the program isn't having to create so much of your video preview on the fly.

videoITguy wrote on 8/29/2013, 1:57 PM

Just a word of caution to the OP. Projects with lots of clips be they integrated on a very long runtime timeline, or bunched up into complex compositing in a real short timeline- are ALWAYS better handled by segmenting the project into one or more parts.

Segmenting can come thru techniques of nesting, rendering sections to intermediates, or simply dividing the whole project into manageable regions that will contain their own NLE workflow/actions.

TheRhino wrote on 8/30/2013, 5:09 AM

We keep all of our source video on fast 4 or 8 drive RAIDs. Although there are lots of folks on this forum who dismiss the benefit of RAIDs, one key benefit is that our clips & audio peaks load significantly faster. Although SSDs are getting larger, our hardware RAIDs have been very reliable. We keep a backup of the source video elsewhere, so we load the source video onto a RAID0. The target renders go to a RAID10 which also holds our VEG files. All drives are in hot-swap bays & properly cooled. We've only had (2) drive failures in 6 years. After a quick hot-swap of the bad drive, we were back editing in minutes vs. hours... Just something to think about if you have a lot of source video & your timeline is fairly complex...

OldSmoke wrote on 8/30/2013, 7:51 AM

Aside from the already very good comments made, VP10 doesn't benefit from your GPU at all. VP11 and 12 are more stable on my systems then any other version before and take full advantage of the GPU; almost all FX are GPU accelerated, many render codec are too and since you have a GTX560 it will be well utilized. I would at least upgrade to VP11 if you have it or go with VP12 build 563; 670 seems to have more issues. Install the trial version of VP12 and give it a try. I also would change to Win7Pro-64bit as it is faster then Vista; that was my experience back in 2010. Another way to improve playback is to convert all files to a "lighter" format, VP works very well with Sony MXF format.

I am with TheRhino, RAID makes a difference, especially loading a project. I use a RAID 0 with two 512GB SSDs just for projects and it is backed up at the end of the day to a RAID10.

A good system with GPU acceleration should work like this: http://www.sonycreativesoftware.com/forums/ShowMessage.asp?Forum=4&MessageID=859391

wilvan wrote on 8/30/2013, 10:15 AM

Vegas Pro 12 is the only one USING the preview RAM in my workstations .

The HPZ820 station , I dedicate 48 Gigabytes to preview RAM and vegas pro 12 really uses it when previewing and that is WAY faster than the quadro 4000 GPU stuff ( when it would work ) .
Which is normal .

Am talking preview only since that makes me gain ( lots of ) time .
Rendering goes fast anyway with 32 cores

PS : have to change max RAM and max cores each time in internal prefs since vegas pro seems to be limited standard to 32 GB RAM and 16 cores ( unlike adobe and avid which like the more the better )