Can record 24-bit in Sound Forge but not Vegas

Jason_Abbott wrote on 11/14/2002, 4:35 PM
There's a lot of noise in the audio group right now so maybe I'll try my luck over here. By "not" in Vegas I mean that if I set the project properties to 24-bit audio then recordings are completely silent--the meter doesn't move above -Inf. I don't get any errors, just no sound. If I set it to 16-bit then everything works fine.

In Sound Forge I can record at 24-bit without trouble. The playback and record devices are set the same in both applications. I'm running Windows XP with a WamiRack 192X and all the latest drivers, patches, etc.

Why the different results?

- Jason

Comments

salad wrote on 11/14/2002, 6:31 PM
Jason,

"There's a lot of noise in the audio group right now"

Yeah, what the heck is up with that anyway? SF has even had to pull a few posts.
You might get some good feedback with the Acid group.

OK, I've got this older PC online right now with a Creative SC, so I won't be getting TRUE 24 bit, but it does seem to be recording @ any setting using WinClassicWave or MS SoundMapper @ 16 or 24 bit.

Try...closing all sound apps, and check your Wami's Ctrl panel for WDM/MME drivers and other routing and settings(monitoring/MIX/ and bring up all the faders for the testing).
Leave SForge closed, as well as any other app that uses the sound card.
Open a blank instance of Vegas, set your properties to 24 bit. Insert an audio track, and ARM it for record. Start playing something on external sound device (keys, microphone...)bring the tracks record level slider up, and there should be activity in the meter, but maybe not in the MASTER meter below. Try this with both MS Sound mapper and ClassicWaveDriver. It should record something.

May have to go to WinXP CtrlPanel/Sounds&AudioDevices/Sound recording/click the Volume tab and check XP's mixer for a check in the correct box for the input and adjust the slider there too.

HTH
Jason_Abbott wrote on 11/15/2002, 10:34 AM
Thank you for the suggestions. I've gone through those and others with no better luck. I'll probably try to get some tech support from ESI (Wami maker) but I'm guessing that if I say it works fine in an application closely related to the one with problems, they'll blame the application (Vegas).

It would be nice if someone from SF could say that Vegas records via method X while Sound Forge does Y so that I would have somewhere to start with ESI tech. As it is, the settings I have in those applications appear to be identical, yet one works with 24-bit recording and the other doesn't.

- Jason
salad wrote on 11/15/2002, 2:55 PM
That's frustrating I know.
I was able to play with a ESI WavTermnl.192M for about a week, and it did record 24 bit in AP4 with WDM, but I never got around to trying it in VV.
It would not record 24 bit w/ASIO2 in AP4, and I am having the same prob. with this M-Audio Quattro, which DOES work with ASIO2 in Cubase SX @ 24/48.
So, you're not alone, but I would give ESI a call and post same in Acid forum, cuz a lot of those folks have VV & SF....and Wami's.

Good luck!
Webster wrote on 11/16/2002, 9:58 PM
I too have troubles with my Audigy Sound card and Vegas 3.0. I've learned to go into Options/Preferences and set the Audio for "Classic Wave Driver" with my ADAT card as the record default. This allows me to record at 24 bit in Vegas, but the cursor doesn't move and the time display doesn't work. When I play back, I go back to Preferences and set the Audio for Sound Mapper. Then the cursor and time display work and I see where I am in the track. It's a big pain to have to reset these options all the time! Hint, the reason you're up and running in Sound Forge is because there's an option box in Preference/WAVE that says: "Interpolate play position for inaccurate devices" I couldn't find a similar box in Vegas 3.0. The implication here is that Audigy is not "accurate" Anybody out know what's going on?