No. I am using PII 450. Is there something I should know about PIII
and vegas?

Peter sent me the fix information and all looks good.

Can anybody tell me a rough estimate on how much the 24-bit sForge
upgrade will be btw?

Thanks,
JoeD

Pops Pops wrote:
>>joe:
>>one of the problems is
>>wavelab can't read mono files
>>wavelab CAN read 32 bit files
>>in order to edit wav files from vegas you must first
>>mix the individual mono track to a stereo file:
>>1. solo the track you want to bring to wavelab and only that track.
>>2. select mix to new track (up in the menus somewhere)
>>3. set your new track settings to 24 bit stereo in the mix to new
>>track window.
>>4. open the new stereo file in wavelab
>>
>>that should do it
>>there is also an option in wavelab to 'open mono files as stereo
>>files' which may allow you to avoid the above steps. i haven't
tried
>>that yet.
>>this is another reason that i eagerly anticipate the release of a
SF
>>that will work with 24 bit files!
>>
>>secondly,
>>i was having the same thing with the 24 bit files being written as
32
>>bit files. it was driving me crazy too. peter haller sent me a
fix
>>for that which you can send him an e-mail about. or- if i can find
a
>>copy of our discussion i'll send it to you.
>>
>>my guess is that you are using a PIII, right?
>>-pops
>>
>>
>>Joe Doria wrote:
>>>>I have finally been able to use Vegas (delta 1010 driver
>>>>woes ironed out....as of yet).
>>>>I must say I am very impressed with Vegas, great job so
>>>>far!!!
>>>>
>>>>But...there are some problems. Please help if you can
>>>>
>>>>1. Why is vegas saving audio as 32-bit files...when I
>>>>specified 24-bit for the audio project?
>>>>How do I set it to only record/save as 24-bit?
>>>>I verified my project properties over and over...but it
>>>>still won't record 24-bit files only....it's recording as
>>>>32-bit, 44.1. when I set it for 24-bit.
>>>>
>>>>I must be losing my mind. There's gotta be a reason...or
>>>>maybe way and I'm just not seeing it. I've re-read the help.
>>>>
>>>>Why?: when I open up wavelab to edit each file separately,
>>>>it says it can't read the file. Wrong format.
>>>>I'm just trying to edit these files and then save a copy of
>>>>them for backup via Wavelab 2.0.
>>>>Why amI getting the file format errors (because it's 32-bit
>>>>audio is my guess)
>>>>
>>>>Even worse: To work around this, I tried re-saving the
>>>>file(s) using a diferent route....
>>>>
>>>>- using Vegas go - FILE-SAVE AS....
>>>>- speciying .wav extension...not .veg
>>>>- specifying 24-bit mono (custom)
>>>>
>>>>Now....I CAN open the projects audio files in Wavelab for
>>>>editing (24-bit files)....but IT MIXES ALL THE .WAVS IN
>>>>DOING THIS!!!!!!! arrrgh....
>>>>(PAINFULLY FOUND THIS OUT THE HARD WAY....man I was stupid.
>>>>Live and learn I guess...but wow...it's somewhat easy to
>>>>miss that copy all media checkbox)
>>>>
>>>>Meaning: if I re-saved just the drums the above way in
>>>>Vegas so I can open it in Wavelab, it saves ALL the audio
>>>>in all other tracks as well....so each track I re-saved is
>>>>now a mix of all instead of it's own separate track.
>>>>
>>>>yes - it is stated in the help file that it creates a mix
>>>>if you look closely.
>>>>Shit....oh well, we live and learn...but those were some
>>>>nice drum/perc takes
>>>>
>>>>But....IT STILL DOESN'T EXPLAIN WHY I CAN'T OPEN UP THE
>>>>FILES IN WAVELAB AFTER RECORDING IN VEGAS...or HOW DO YOU
>>>>SET VEGAS TO ONLY RECORD 24-BIT/448 mono FILES????
>>>>
>>>>After recording my 24-bit project in vegas, I can open up
>>>>the separate .wavs in COOLEDIT PRO 1.2 (it handles 32-bit
>>>>files)...but I would much rather use my wavelab for editing
>>>>24-bit audio (used to it). I can't...it won't read the
>>>>format.
>>>>
>>>>What is going on? Did I miss something?
>>>>
>>>>ALSO*************
>>>>
>>>>It would be great to make it more obvious to save a
>>>>projects wav files all in it's own folders (aside from the
>>>>temp directory). It makes for confusing audio managment.
>>>>Possibly a dialog as a reminder if you want to save each
>>>>track to it's own designtaed drive/folder?
>>>>
>>>>ALSO 2*******************
>>>>
>>>>Please test, test and re-test functionality with using ALL
>>>>direct-x plug-ins with vegas. I am getting the occasional
>>>>crash when using say even 2-3 fx busses with 1-2..maybe 3
>>>>plug-ins each, and I'm reading a lot of posts with similar
>>>>problems.
>>>>
>>>>Now I know that is a lot to ask but crashes when working
>>>>with sound/music...which sometimes happens only
>>>>once....doesn't sit well on the trust factor scale.
>>>>
>>>>Now I believe in backups...so that saved me....but when the
>>>>app just gpf'd and closed so abruptly...it makes one wonder.
>>>>Others might not be that lucky...
>>>>It's happened once every 3-4-hour session (eh...not bad I
>>>>agree...but were talking about your takes here...not a
>>>>letter with pic to grandma)
>>>>
>>>>It could turn many possible customers away....towards
>>>>hardware based units? I dunno....it just would be a smart
>>>>plan of attack.
>>>>
>>>>You are SF though.......you have an excellent track record
>>>>for creating usefull apps, fixing the problems,supporting
>>>>all hardware, and treating the customer well. I'm sure all
>>>>these little quirks will be put to rest soon.
>>>>AND I'M DEFINITELY NOT RULING OUT MIDIMANS DELTA 1010
>>>>LATEST DRIVERS - they could be the culprit as well even
>>>>though they are stated as 100% compatible.
>>>>
>>>>
>>>>I have a clean re-install of win98(updated), Midiman Delta
>>>>1010, Vegas, Wavelab, PII 450 196 ram, 4 scsi HD's (1 cuda,
>>>>and 3 cheeta) all running wide on adap-2940uw. System and
>>>>setup are tip-top.
>>>>
>>>>** can't go to NT just yet.
>>>>
>>>>Please help with this 24-bit issue though.
>>>>Thanks,
>>>>joe