Running 64 Bit Vegas (Pro9). When selecting "open copy in sound forge"(v9) - get error message "unsupported bit depth". This never happened on prior Vegas or XP systems. Any ideas? - or am I S.O.L.?
I'm thinking that it's coming from soundforge. While in Vegas, I right click on the audio track and select "open copy in soundforge". Soundforge then opens up and I get the error message.
VegasPro9b opens files fine in SoundForge9 or SoundForgePro10, and they play fine in either application here; however the 24bit files are definitely converted to 32bit (IEEE float) which I don't understand - for sure this is inconvenient, as user has to remember to save as 24bit should the processed files subsequently be needed in applications which do not support 32bit.
I'd suggest buying a better soundcard. Either 1) your motherboard soundcard doesn't like having both Vegas and Sound Forge open at the same time. Or 2) the soundcard doesn't support playing 32bit files.
1) Check to see that you have the option in Vegas preferences selected for "Close all media files when application loses focus"
If that is selected, then it's a problem with your audio card.
2) Echo Audio products seem to work very well with Vegas / Sound forge.
www.echoaudio.com
I've sent in a support ticket about being forced to open files as 32 bit float. Apparently they are working on a solution to fix this.
There may also be a possible workaround for you. Typically the error you say is coming up will display only when you try to play the file in sound forge.
If it lets you open the file, you could select -> process -> bit depth converter - then change the bit depth back to 16 bit - then you can probably play the file.
> I've sent in a support ticket about being forced to open files as 32 bit float. Apparently they are working on a solution to fix this.
I also reported same (I have no problem playing 32bit, it's just inconvenient & makes no sense); response I received from support was this is perfectly normal!!
Obviously Support are confused.
As the problem is introduced in VegasPro9, it must be a bug....