Open copy in SF from 9b now converts file to 32bit

gwailo wrote on 9/5/2009, 7:42 AM
Does anyone know why opening a "copy in sound forge" of any audio in Vegas 9.0b results in sound forge opening the file as 32bit floating point instead of the original bit depth?

This did not happen in 9.0

I suppose more resolution can't be a bad thing.

But after the text bug, I'm worried that they may have broken something to do with the audio now.

I haven't noticed any repercussions yet in my testing. I'm still using 8.0c and waiting for an all clear to start using 9 when 9c comes out

Comments

megabit wrote on 9/5/2009, 7:58 AM
I don't know for sure, of course, but I [b]strongly suspect[b] this new "default" is SCS trying to impose using the full Sound Forge system (now having the new v. 10), rather than the Soundforge Audio Studio (which has been pushed as a "freebie" when upgrading to Vegas 9).

I first noticed it trying to use Audio Studio with my MXF audio - no joy, enforced conversion to 32bit prevents them from even opening in Audio Studio. From what you say, now it affects other formats, as well.

Pity - the user should have choice of precision he wants his audio file opened with in a sound editor.

AMD TR 2990WX CPU | MSI X399 CARBON AC | 64GB RAM@XMP2933  | 2x RTX 2080Ti GPU | 4x 3TB WD Black RAID0 media drive | 3x 1TB NVMe RAID0 cache drive | SSD SATA system drive | AX1600i PSU | Decklink 12G Extreme | Samsung UHD reference monitor (calibrated)

gwailo wrote on 9/5/2009, 8:21 AM
What you say makes sense.

I knew it was either a feature, fix or a f*ck up.

I'm glad Sony is back to being evil instead of just being incompetent.
megabit wrote on 9/5/2009, 8:36 AM
What you consider "evil" is just Sony trying to make us use their PRO solutions only:)

AMD TR 2990WX CPU | MSI X399 CARBON AC | 64GB RAM@XMP2933  | 2x RTX 2080Ti GPU | 4x 3TB WD Black RAID0 media drive | 3x 1TB NVMe RAID0 cache drive | SSD SATA system drive | AX1600i PSU | Decklink 12G Extreme | Samsung UHD reference monitor (calibrated)