I have a Layla 24 and it records fine in 24 bit using Vegas 3.0
I am running WinXP professional

Funny, I'm running WinXP-Home and am having the same problem with the WaveCenter PCI and the 3.0 driver. I didn't have the problem with the beta driver and SF records 24bit fine as well. However Vegas 3.0c will not record or even show input signal with 24bit selected. 16bit works and sounds perfect. I'm puzzled.

Don

I had a similar problem recording 24 bit from Apogee Mini-Me XPHome SP1, and the problem turned out to be that I hadn't completely installed the latest XP driver from Apogee. Under Win2k installation on same machine, the driver installed automatically, 24 bit recording worked. With XP's signing, I think the auto install didn't finish. At any rate, I received a detailed installation procedure from Apogee tech support that fixed the problem.

Don't know if this applies to other hardware, but the symptoms sound similar . .

Rick Z

I have *no* problem recording 24 bit from my MOTU 2408/2 in Vegas, or SF, or Acid.

I wasn't able to do this in 98SE (just 16 bit).

geoff

Try this...file/properties/audio/bit depth
Randy

Yeah, it's that bit-depth change that reveals the problem. Changing it from 16 to 24-bit results, for some of us, in no audio being recorded.

I have the exact same problem with the same setup. Have You found an answer yet?

With RME HDSP 9652 a few builds back it would crash if you armed a track in 24 bit in MME, but not in ASIO. That problem seemed to have gone away, but just recently returned on the last build ( sometimes )

This is caused by WDM based audio drivers that don't support 24 bit packed audio format.

What happens is that Vegas attempts to open the driver in 24 bit packed mode using what is called WAVEFORMATEXTENSIBLE. This request goes to the WDM driver. If it says to Windows "Nope, can't do that" Windows will then try other formats. Windows does not try 24 bit unpacked - 24 bits in a 32 bit word. Instead, Windows opens the driver at 16 bits. Vegas is told everything is fine. It assumes it will get 24 bit data and Windows just feeds it 16 bit data.

This problem effects all versions of ACID and Vegas. We will be addressing this issue only for Vegas 4.0 and ACID 4.0.

For previous versions of our products, you will have to get the driver vendors to support 24 bit packed audio.

Peter

<<This is caused by WDM based audio drivers that don't support 24 bit packed audio format.>>

Peter: Could you list which specific WDM drivers that don't support 24 bit packed audio format that Vegas users would most likely encounter? Thanks!

drbam

The two that I have specific results on are:

MOTU drivers.
mLan based

I will check with our tech support and QA and see if we can compile a list and post to the FAQ.

Peter

great... that means the only soundcard I was interested in, the Firestation, wont work.

I can't record 24 bit with my ESI Wamirack 192L Interface, so I guess it's the same problem...

Peter,

Are you suggesting that my 2408/2 with WDM drivers is only effectively giving 16 bits in VV3 ? Maybe that's why I'm less than stunned with the difference bewtween 16 and 24 .

What 24 bit format do these drivers feed, and why was that format not accomodated by SF apps ? Or did MOTU miss the boat again, and supply a 24 bit WDM format that noboy uses ?

geoff

Yes. The WDM based drivers when used through the Wave Classic driver mode of Vegas will only provide you with 16 bit resolution.

The driver only supports 24 bit unpacked audio. That is 24 bit worth of data in a 32 bit word. Vegas (and ACID) by default attempt to open the driver at 24 bit packed first. Since the driver does not support this it fails the request and then Windows opens the driver at 16 bits.

Win2000 and WinXP only support 24 bit through WDM drivers using WaveFormatExtensible (vs standard WaveFormat).

Windows audio subsystem does not report an error to Vegas. I just maps what the driver can do to the request made. It remaps the audio to a format the driver does support - in this case 16 bit.

Because of the different ways different drivers support 24 bit, Vegas attempts 24 bit in the following order:

24 bit packed using WaveFormatExtensible
24 bit unpacked using WaveFormatExtensible
24 bit packed using WaveFormat
24 bit unpacked using WaveFormat

The latter two formats are typically of Native Wave drivers - i.e. RME or CardDeluxe.

This will be corrected in the first update release of Vegas 4.0 by forcing Vegas to open first in the unpacked formats and then the packed formats.

Peter

So what cards did Vegas , Acid, (and Sound Forge ?) ever actually work in 24 bits/WDM with then ?

geoff

Mixstreme, MAudio cards, Echo cards, EGO Sys, CardDeluxe, many more. There are more that handle it correctly than those that don't.

Peter

so wait, so the RME isnt doing 24 ?

Is there an industry liason that gets these things sorted, or is it up to individual comapanies/users to lobby the others ?

geoff

Well, the Egosys card won't even record 24 bit with Vegas.... A guy that had a wamirack 192x had the problem and I have it also with a wamirack 192l...
If you choose 24 bit the program doesn't receive any audio, only a silent signal...

"so wait, so the RME isnt doing 24 ?"

Yeah, where's all those know it all wankers now, who where jumping on my "Echo" cards, and boasting how much of a "Professional" card the RME's are over the Echo's? Where are ya JoeD(Angelica) and company? Eat crow, die and talk out your ars some more!!! LOL!!!

RME is not WDM based. It has Native Wave drivers.

It records 24 bits correctly - at least in my tests.

Try it yourself and make sure in your own mind.

Peter