Yep, saving a project during playback (including auto backup) never caused me any problems in V3. But I am getting loads of stuttering in V4 (non ASIO).

No problems over here! only a playback error using asio with my motu 2408MkII.
"An error starting playback. error 0x8004e0c1(message missing)"

Dide

Im Using the PCi 324 Motu into a Motu 24i and im having huge stuttering issues with asio as well as the legacy driver.

Mostly when zooming in or out though it seems

It seems that some of my issues are also associated with screen refreshes. When the track view changes or I have a lot of FX meters showing it seems worse. However, sometimes I just hit patches of audio that always stutter. Interestingly enough I saw similar issues in earlier (VA 2.0) versions where some patches of in the timeline caused glitches/stuttering.
bgc

I have seen the same error using ASIO with my Frontier Dakota. I also had a big crash when I changed the buffer size on the Dakota and then went back to enable the record input monitor. The machine completey rebooted (which was the first time this has ever happened with this machine).

Whether in ASIO or MME Vegas 4 is causing random glitches, loops, skips, and stutters. Once I find a skip I go back and play it again to see if it happens in the same place and it doesnt.

Please do some apples-to-apples comparisons: Take a complex project that plays smoothly in V3, and open that in V4. Don't use ASIO or any else that isn't in V3- that skews the test. We're still doing benchmarks here and shaking out a few kinks...but performance in V4 should definitely not be worse than in V3, even with the beta, if you use identical settings.

We are very interested in the results-

Using an identical mix, running MME at .075 buffers (same as I would in V3 ) I am getting these same random glitches. The silly part is, it seemed to be working Ok for the last week or so, just as soon as I had a customer in ... bug city, Murphy's Law. So I had occaision to keep switching back and forth between vegas 3 and 4, cuz dammit I wanted to use those Buss Tracks!

Hi,
I've done this exacting, side by side comparison between complex Vegas 3 projects played in Vegas 4 (non-ASIO, because that doesn't work correctly with my CardDeluxe).
I am definitely seeing stuttering issues and gapping where I wasn't before in VV 3.0. The one thing that is different is that I set "Number of playback buffers" to 16. I still don't know what this parameter means for non-ASIO playback. If I set it lower, the playback cursor and audio aren't aligned.
Hoping we can fix this because I've actually had to go back to VV3 for some complex projects that I'm working on.
bgc

Peter said:
We're still doing benchmarks here and shaking out a few kinks...but performance in V4 should definitely not be worse than in V3, even with the beta, if you use identical settings.

We are very interested in the results-

Ok, I did my push my system to the limit until it dies test with Vegas 3 and Vegas 4. What I do is keep on adding audio tracks and arming all of them for record to see how many simultaneous tracks I can record before my system dies or I start to see studdering in the audio. I got pretty much the same results with Vegas 3 as I did with Vegas 4.

With Vegas 3 I was able to record 70 simultaneous tracks at once. I then bumped that up to 74 tracks, and it started to record, but now the waveforms where lagging behind where the cursor was. After 30 seconds of recording I hit stop, and my hard drive starting crunching away, and Vegas 3.0 locked up at that point.

With Vegas 4 and the exact same settings as in V3, again I was able to push the simultaneous tracks being recorded to 70. I went to 72 after that, armed it for record...and recorded away. I didn't get the lock up like in Vegas 3 this time. It started recording and Vegas just disappeared....like it was there in front of me, and then all of a sudden there was my desktop. I don't know if you can call that a bug, or a feature over Vegas 3. I guess it just depends on what you prefer, either the program locking up...or just automatically shutting down. In either case, this was an extreme test that will never happen for me in real life recording...until I get a 70 input soundcard and individually mic an orchestra.

The thing I found interesting was that I did this same test recording to the same hard drive (Seagate Cheetah 10K RPM SCSI) during the beta testing of Vegas 3 and was only able to push my system to 45 tracks being recorded simultaneously. That system only had 128Meg of PC133 ram in it at that time and was running under windows 98SE. From that time I bumped the RAM up to 1.1 Gig and changed the OS to Windows XP. Pretty impressive, because everything else stayed the same and I was able to bump the track count up +25. So I'm thinking RAM has a lot to do with track count?

I use the same settings as Vegas 3 and experience no difference in performance.

BQC Said:
"I am definitely seeing stuttering issues and gapping where I wasn't before in VV 3.0."

What OS are you running? What Video Card do you have installed?
I had a similar problem with V4 that I didn't see in V3. After further investigating my sound card driver, I actually found a problem that existed in V3, but didn't really rear it's ugly head until V4.

My solution was that I was running WindowsXP an early release. I did a "Windows Update" and installed the latest SP1 updates along with the hardware drivers that where suggested. One of those drivers was my ATI video card. So somewhere inbetween the SP1 updates and the video card driver update, my problems no longer existed in V4, and also no longer existed in V3. V4 just made the existing problem worse, but the problem was always there on my system.

Red,
I am stressing the system in a different way than you. I am doing a track mix which has
1) 24-32 tracks of audio with lots of individual events
2) Many vol, pan, fx envelopes
3) Many track and buss FX. Lots of Waves EQ, Waves Compression, Waves Reverbs.

Unlike simultaneous record my application is making intense use of the CPU for native processing. If people have some serious mixes lying around try that type of comparison.

I'm running Win2k with a G3Force card. I'm not comfortable installing Microsoft's latest spyware OS at this point.

I too am seeing what appears to be higher overhead, but interestingly, V4 seems to use less processor power, yet I'm getting huge amounts of stuttering using standard drivers on my Delta 66 (Under Win2K). If I switch to ASIO, it's even worse, with not only suttering, but some really strange mechanical sounds. V3 is perfectly fine with the same project loaded.

Also, if I "Solo" a buss, it throws the timing of that buss off from the rest of the project. Only stopping and restarting playback will get things in sync again.

I'm glad to hear that I am not the only one having these problems.

I'm using Win 2K running on a Tyan Tiger S2466N-4M M/B with dual MP-1900's, Corsair Registered DDR Ram, fast HD's, Frontier Dakota\Montana etc. This has been the most stable system I have ever owned and a real screamer as well. I have intermittently had stuttering problems with V4 and also found it impossible to send tracks out to my analog gear and back in (awful raspy garbage). I ended up using Vegas 2.0h (never bothered to upgrade to V3) to do this and had to move the track back into V4 to mix. The rendered mix from V4 was OK though the stuttering annoyed me during the mixing process.

It also appears that you cannot open Vegas 2.0 projects in V4. Is this ever supposed to work or am I screwed? Seems I'm the only one on the planet still using this version as I have yet to see any posts regarding V2 users trying out the V4 beta.

Posted by: bgc (Ignore This User)
Date: 1/23/2003 12:36:38 PM

"I'm running Win2k with a G3Force card. I'm not comfortable installing Microsoft's latest spyware OS at this point."

**************************************

Really no need to pay for it if you don't want to. There are myriad patches around to circumvent registration/authorisation.

geoff

"It also appears that you cannot open Vegas 2.0 projects in V4. Is this ever supposed to work or am I screwed?"

I've been informed that V4 will open V2 projects as well as V3.

Definitely not comfortable installing, of all things, a cracked version of the OS!
:)
bgc