Comments

Gammaburst wrote on 6/29/2002, 1:59 AM
On a dual-AMD Win2k system, VV3 seems to use one processor for previewing/rendering, and the other processor for the user interface. The preview window doesn't slow down the user inteface. Very nice! I tried that on a single-CPU machine, and the user interface became sluggish.

It would be nice if Vegas used both CPUs during final rendering.
SonyDennis wrote on 6/29/2002, 9:01 AM
It does use 2 CPUs for rendering. Audio FX processing can split across processors, and for DV rendering, frame composition and DV compression can split across processors. Due to memory and I/O bandwidth issues, we're currently not seeing 100% utilization of both processors, so, like people have said, it does go faster, but not as much as faster as theoretically possible.

///d@
mbo wrote on 6/29/2002, 7:34 PM
"Due to memory and I/O bandwidth issues, we're currently not seeing 100% utilization of both processors"

Is it unique for VV or is it for all available software?

Thanks,
Michal
SHTUNOT wrote on 6/29/2002, 8:07 PM
Or maybe sofo r&d haven't figured out how to do it yet.I think I read somewhere in the forums that premier takes advantage of duals alot better. Since Vegas isn't going to support any hardware cards like premier they better learn how to use every clock cycle[for a lack of a better term]so that they narrow the gap between which app can be used in a "tight scheduled" workplace. Later.
Gammaburst wrote on 6/30/2002, 12:20 AM
I tried rendering a DV movie with various filters, transitions, and pan/crop effects on a dual 1.5GHz AMD. This is CPU intensive stuff, not much disc I/O. Win2k Task Manager indicates 35% to 57% total CPU utilization, never higher. Should it go higher?
Gammaburst wrote on 6/30/2002, 12:57 AM
Almost forgot... You can launch two instances of Vegas. Edit/preview one project while rendering another. Fully utilizes both CPUs. Nice!
Control_Z wrote on 7/2/2002, 12:11 AM
Not unless you have a ton of memory. I tried this the other night and with 512M RAM things slowed to a crawl. Oh, both instances were finished rendering in the morning, but they both tried to grab so much RAM doing it using the machine was impossible - even trying to browse the forums.
Control_Z wrote on 7/2/2002, 12:16 AM
When I first got VV3 I had dual P3's. And yes, Premiere 6 would max them out (95-100% on both). I ran some simple tests of everyday things like dissolves and P6 would render almost exactly twice as fast as MSP (uses 1 CPU) and VV3 always brought up the rear.

If fast rendering times are a really big factor for you VV3 may not be your first choice of NLE.