Vegas 4 playback click, my statistics.

Geoff_Wood wrote on 2/28/2003, 5:30 PM
Am posting this to SF tech support, and on Vegas forum , hopefully to garner some other peoples' statistics.

My experience with V4 so far. In VV3 I had moderate CPU load when playing back 28 track project. Clearly I have some issues with ASIO .....

Playback 16 tracks 24/44k1 WinXP Home, Celeron 1G1, MOTU 2408/2 latest (26/03/2002 ) MOTU WDM/ASIO drivers, 7200 rpm, 256MB RAM.

V4 (ASIO)

MOTU buffer Clicks/10sec CPU %
64 ****** 100%
128 ***** 81%
256 **** 76%
512 *** 59% (after re-start due to app crash
1024 ** 60% when changing buffers from
2048 * 48% within V4)
* (enabling even one 'rec' track sends CPU usage soaring, with 16 tracks PB)

** (Muting PB tracks reduces CPU load)


V4 (MME) (Bad clicking on all buffers other than minimum = 64)

Buffer = 64 PB OK. Occasional dropped 45%
samples on rec.

VV3 (MME) (Bad clicking on all buffers other than minimum = 64)

Buffer = 64 PB no clicks, 47%
rec not tested

Any thoughts/tips/comparisons appreciated

geoff

Comments

Rednroll wrote on 2/28/2003, 5:36 PM
I'm not for certain, but I think some people where having troubles with the MOTU stuff due to the drivers. Have you tried the Classic Wave driver? Do a search on this forum and you might be able to dig something up about the MOTU stuff.
Cold wrote on 2/28/2003, 6:02 PM
unless my buffers are set at 256 in the cuemix console I have all sorts of issues.No success with asio as of yet. This 256 issue only came about after I upgraded to XP pro. Also running a via chipset which I know the motu does not like. Oh well, live and learn, I'll be much more carefull with compatability issues next system and this system does perform well with vv3 as long as I'm aware of the issues. Bought vv4 but I won't use it with clients yet as I haven't got it stable enough yet.

Win xp
Athlon 1gig
512 ram
via chipset
motu 2408
If there is any testing I can do for you Geoff, just let me know.
Steve S
Geoff_Wood wrote on 2/28/2003, 7:45 PM
Red, that thread never came to any conclusion.

Cold, Likewise wrt V4 and clients. I had a slight issue with V3 and MME drivers with occasional dropped samples. OH pretty much same with V4/MME - will try out recording in that mode tonight.

Oddly, the accasional dropped sample in V3 gave a result preety much like the SF symbol - a sine wave with an 'inversion/split' in the middle ! I guess there may be others that cropped up in inaaudible sections or at low level program/zero-crossings...

geoff