Gotcha...

This is what is happening.

When Vegas opens hardware for recording at 24 bit, we attempt to
opent the hardware in the following order:

32 bit PCM
24 bit unpacked PCM (24 bits in 32 bit container)
24 bit packed

Why? Most hardware is more effeicent at 32 bit or 24 bit. Some 24 bit
hardware (DPSFactory comes to mind) doesn't even support 24 bit
unpacked or packed.)

We the save to the format that the hardware provides us. (This is
going to change in a future update.)

So, you are not loosing anything, but you are using more disk space
to store the recorded material. There is no truncation of any kind
happening.

I just tried the windows explorer thing. It seems that - at least
under NT 4 - that 24 bit and 32 bit PCM files are not recognized by
in the details tab of the properties for wave files. Hmmm.

Peter




Pops Pops wrote:
>>peter:
>>thanks for your response
>>i'm dumping tracks into vegas
>>from my 20 bit/48k ADAT
>>via my Frotier Design Dakota ADAT optical connection
>>so the files are 20 bit before they hit vegas
>>i want to record them to vegas at 24 bit
>>so i've got all my vegas defaults set to 24 bit
>>and, indeed, the little message bar next to the tape controls
>>says "24bit, 48k"
>>BUT
>>when i right click (properties) on a track in vegas it says 32bit
>>
>>in windows explorer, right click (properties)doesn't give info
>>regarding bit depth
>>should it? i wish it would
>>i always have to check in wavelab to find the bit depth of my wav
>>files
>>
>>it seems like something funky is going on with these bits
>>i truly suspet that truncation is happening
>>it seems like my tracks are less robust, less crisp and less
defined
>>after i mixdown
>>am i simply imagining that?
>>
>>maybe i'm missing something somewhere in my vegas set up
>>what are all the settings in vegas that i need to check
>>to insure that i'm loading in tracks at 24 bits?
>>
>>-pops
>>
>>ps. i've been using vegas about 10 hours a day lately, trying to
>>complete a big project. there are minor gliches (as mentioned
above)
>>but overall, i am creating mixes that far surpass anything i could
do
>>within my measly analog outboard setup. my xfx123, tc native
>>essential, and steinberg multi band compressor plug-ins are great.
so
>>i give two BIG cheers for vegas, and i save the third one
>>for the near future which sees a more vibrant (thing) vegas.
>>
>>
>>
>>Peter Haller wrote:
>>>>The files you are loading into tracks, where did the come from?
If
>>>>Vegas reports them as 32 bit, then the original material is 32
bit.
>>>>
>>>>Try this. Right click on one of these files in the Windows
Explorer
>>>>and select the Properties option. What does Windows tell you
about
>>>>the file?
>>>>
>>>>When we mix to new, we use the properties of the project.
>>>>
>>>>We are not truncating the upper 8 bits - this would be very
yucky.
>>We
>>>>always process internally in floating point and then convert to
the
>>>>desired rendering format.
>>>>
>>>>Peter
>>>>
>>>>
>>>>Pops Pops wrote:
>>>>>>when i enter tracks into vegas
>>>>>>they are listed as 32 bit tracks(right click, properties)
>>>>>>however all of my default settings are at 24 bits.
>>>>>>what is happening?
>>>>>>
>>>>>>after i mixdown tracks those same tracks within vegas
>>>>>>they are listed as 24 bit tracks.
>>>>>>
>>>>>>am i truncating the top 8 bits??!!
>>>>>>
>>>>>>that is yucky, i don't want to do that.
>>>>>>i'd rather dither down.
>>>>>>
>>>>>>ideally though, i'd rather have my tracks
>>>>>>enter into vegas at 24 bits and stay
>>>>>>at 24 bits.
>>>>>>
>>>>>>what is up?
>>>>>>
>>>>>>-pops