BIG problems recording using V5

sstillwell wrote on 5/1/2004, 6:05 PM

Went and recorded a live all-ages show Saturday night. I have recently upgraded to Vegas 5 on a P4 2.8GHz/800FSB machine (Intel D875PBZ mobo). 1GB DDR400 dual-channel RAM, EIDE OS drive, SATA audio drive. Using a Delta 1010 and a Delta 44 with latest drivers (5.10.00.00036)

Setup for recording the first band using ASIO, 512-byte buffers. Recording ran smooth as silk, pressed "Stop"....Vegas hung (became non-responsive). I did not get the "Delete/Delete All/Done" dialog, and the rest of the computer remained responsive. After rebooting, the wave files were there, but only 512 bytes...OUCH.

Rebooted and set the next project up to use Windows Classic Wave Drivers. Stopped recording at several points during the set to see if it was going to work, and it did. Went on the the next band/project and recorded it straight through...no problems.

During a long band change, I pulled up one of the projects to listen to it...it was HORRIBLE...everything sounds like it was recorded at a slower speed and played back too fast...maybe like the difference between 44.1 and 48, except I recorded AT 44.1, and was playing back at 44.1. Also, there is a periodic pop or gap in all the wave files. I confirmed by using Sound Forge that this information is printed to the file, not just occurring during playback.

At this point, I set up a new project using Vegas 4...same machine, same cards, same drivers, using Windows Classic Wave...I didn't even reboot. Recorded the next two bands, and their recordings came out just fine.

Here's one possible source for the problem, although why it would affect Vegas 5 and not Vegas 4 is beyond me.

In an effort to get more inputs and tracks to disk, I used one of the client's Presonus Firestations on my machine. I had downloaded the latest drivers and programs from Presonus' website before heading to the venue. I could NOT get the device to show up in Vegas, so I canned it and went back to my Deltas. Since then I have gone into System Restore and removed all traces of that evil driver...it blue-screened on me several times. The thing was a pain to set up, anyway...

Can anybody suggest a cause? It's totally my fault for using Vegas 5 for recording before I had checked it out sufficiently, but I had zero problems mixing down V4 projects in V5, so be gentle on me. What I don't want to happen now is to have Vegas 5 choke on me when I'm doing a higher-profile gig.

Was it Vegas or was it drivers?

Regards,

Scott Stillwell

Comments

planders wrote on 5/1/2004, 6:53 PM

I'm just finishing up a similar recording job as I type this, half way through the second act at the moment.

For your rate problem, is your clock source set correctly? If you're recording analog you probably want to use internal clock. I got caught by that a couple of times right after I bought my Layla24 (my old Audigy protects you from all that by doing its own thing internally). If you need to sync to a digital source, make sure all of your other inputs are recording at the same rate as the digital source or you'll have the same problem.

As for the crashes, sounds like you're using M-Audio stuff, and there have been lots of driver issues reported on this forum. Might want to try rolling back to an older version (4.27 was mentioned recently as working properly).

I've been using V5 very heavily over the past two weeks on two computers with Echo hardware; not a single crash, freeze, or awkward moment, whether working with audio or video.

sstillwell wrote on 5/1/2004, 7:50 PM

Well, I'm sure that could cause a big problem (clock source and/or sync), but recall that I switched from V5 to V4 without ANY other changes and it worked just fine. That's the part that's freaking me out. If it weren't for that, I'd write it off to the stupid Presonus/Yamaha mLan drivers. The M-Audio cards have never caused me any real problems...just a couple of weeks ago I did a live recording of a local community symphony; 5 tracks at 48/24...55 minutes, intermission, another 30 minutes...no hitches at all.

THAT recording was gorgeous, by the way. I know that some people have had problems with M-Audio drivers, but that 1010 is just plain DEAD silent...important for classical. Put an M-Audio DMP-3 in front of it, and you've got a killer neutral "straight-wire-with-gain" setup for relatively low dollars.

I know that the Echo stuff is supposed to work really well with Vegas. If I didn't already have the money tied up in my Deltas, I might consider it. The big problem there is if you switch to ASIO...I really wish the spec would support more than one flavor of card at a time....

Scott

sstillwell wrote on 5/2/2004, 8:59 AM

Oh, in case I wasn't clear about it, yes, I did check the clock, but it was set to internal. The Firestation that I had hooked up temporarily was the one that was set to external clock, which was being provided by S/PDIF. When I pulled the Firestation, I disconnected the S/PDIF coax cable. That left the M-Audio cards left STILL set to internal clock, multiple-card sync.

Scott

sstillwell wrote on 5/7/2004, 4:33 PM

Sorry 'bout this...bump.

Rednroll wrote on 5/8/2004, 7:32 AM

I mentioned this in your other similar thread. I would buy a MOTU interface from Guitar Center. Install it, record enable 24 tracks,using all the inputs, let it roll for an hour and see if you get any problems. If that's successful, then hammer on it some more with other things you do frequently using Vegas. If you run into any problems, guitar center has a nice 30 day no questions asked return policy.

stakeoutstudios wrote on 5/8/2004, 1:05 PM

See if you can get hold of an Echo Layla 24. I doubt very much you'll have the same problems.