Open copy in SoundForge from Vegas 9 32k bitrate?

JMacSTL wrote on 8/31/2009, 9:07 AM
Vegas 9.0 is doing something odd. When I choose "open copy in Soundforge", it opens it up as usual, but the file's bitrate is labeled (down in the bottom of the window) as 32 bit * (with the asterisk). The original file was either 16bit or 24 bit. Odd huh? After going back to Vegas it is now listed as 32 bit IEEE Float.

Anybody else seen this occur?

jmm in STL

jmm in stl

Windows10 with Vegas 11 Pro (most recent build). Intel Core i7-3770 @ 3.40GHz 3.90 GHz, 32GB ram, separate audio and video disks. Also Vegas 17 Pro on same system. GPU: NVDIA GeForce RTX 2060 SUPER. Dynamic RAM preview=OFF.

Comments

JMacSTL wrote on 9/2/2009, 12:08 PM
Update:

i still have 8.0 installed. When I choose "Open copy in Soundforge", it opens in the same exact format, sample rate, bit rate that the original file was. So it's happening on the Vegas 9.0b end, not in Soundforge. I'm using SF 9.0d.

SonyPCH have you experienced this issue?

jmm in STL

jmm in stl

Windows10 with Vegas 11 Pro (most recent build). Intel Core i7-3770 @ 3.40GHz 3.90 GHz, 32GB ram, separate audio and video disks. Also Vegas 17 Pro on same system. GPU: NVDIA GeForce RTX 2060 SUPER. Dynamic RAM preview=OFF.

chuck_et wrote on 9/3/2009, 3:55 PM
Running 64 Bit Vegas (Pro9). When selecting "open copy in sound forge"(v9) - get error message "unsupported bit depth". I can't even get sound forge to open.
gwailo wrote on 9/5/2009, 6:10 AM
I get the same thing here.

Don't know if this happened with 9.0 or 9.0a ... I may have missed it

Is this a fix, or yet another broken part?
gwailo wrote on 9/5/2009, 7:22 AM
I'm pretty sure 9.0 didn't open as 32bit floating point.

I looked back in my old projects for my noise-reduced clips that i opened in sound forge. They're all in their original format 16bit 48k.

I guess the only downside to 32bit is that it takes up more space and is harder on the processor / hard drive?

But I'm still curious to find out if this was done on purpose to fix something.
JMacSTL wrote on 9/14/2009, 8:54 AM
There is another thread that is more recent that also talks about this:

http://www.sonycreativesoftware.com/forums/ShowMessage.asp?MessageID=672574&Replies=8

I posted this issue more than a week ago, and SonyPCH never responded to it, yet he responded to the more recent one. I guess I don't have enough clout. Btw: I've been using Vegas for more than 7 years now and promote it all the time as being faster and more convenient than ProTools with no loss of clients (yet).

jmm in STL

jmm in stl

Windows10 with Vegas 11 Pro (most recent build). Intel Core i7-3770 @ 3.40GHz 3.90 GHz, 32GB ram, separate audio and video disks. Also Vegas 17 Pro on same system. GPU: NVDIA GeForce RTX 2060 SUPER. Dynamic RAM preview=OFF.