Comments

pwppch wrote on 8/18/1999, 9:49 AM
Don't know. It is possible that the hardware prefers 32 bit vs 24
bit. By default we open hardware in the 24 bit unpacked format.

If it is a file that you record with Vegas, load it into a track and
check the properties. This will tell you what format it was recorded
in.

If you rendered a Vegas project to 24 bit, the default would be a 24
bit packed wave file.

Peter


Will Gallant wrote:
>>What is it about the 24 bit ".wav" files created in Vegas
>>that cause programs like WaveLab and Cubase to not
>>recognize the format and refuse to operate on them?
>>
>>Thanks,
>>Willg
>>
>>
>>
>>
wgallant wrote on 8/19/1999, 9:04 AM
I should have been more specific.

Recording from the DA-88 source(48Khz/16bit), through TDIF on the
MOTU 2408 (24 bit internal processing?) to the hard drive with Vegas
("24bit" enabled), results in a file with "32bit/48Khz" properties
according to the properties dialog box.

The resultant files can not be opened by any wave editor I own,
including SF.

Either I have something configured wrong (again), or am missing
something in the understanding department(highly likely).

Thanks in advance for any enlightenment.

Willg

Peter Haller wrote:
>>Don't know. It is possible that the hardware prefers 32 bit vs 24
>>bit. By default we open hardware in the 24 bit unpacked format.
>>
>>If it is a file that you record with Vegas, load it into a track
and
>>check the properties. This will tell you what format it was
recorded
>>in.
>>
>>If you rendered a Vegas project to 24 bit, the default would be a
24
>>bit packed wave file.
>>
>>Peter
>>
>>
>>Will Gallant wrote:
>>>>What is it about the 24 bit ".wav" files created in Vegas
>>>>that cause programs like WaveLab and Cubase to not
>>>>recognize the format and refuse to operate on them?
>>>>
>>>>Thanks,
>>>>Willg
>>>>
>>>>
>>>>
>>>>