It is Diamond Cut Audio Restoration Tools but it won't play 32-bit .wav files.

I mainly shoot outdoors football (soccer to USA friends) in an exposed location and, even though I use a deadcat, the wind noise is usually pretty bad. DCart offers the best, easy to use wind noise reduction filter I have found at an affordable price.

Prior to my re-build I used to be able to right click audio events, select Open Copy in Audio Editor, do the wind noise reduction in DCart and then save as a new audio take in Vegas. Now, I have a workaround by using Sound Forge Pro V12 as the preferred editor to manually change the bit depth of the . wav file to 16-bit, save and then manually open in DCart for wind noise reduction.

I'm just trying to work out how I used to be able to open the audio in DCart directly without issues.

Thanks,

MCFC-Fan

To change your preferred audio editor in Vegas Pro, go to Options/Preferences/Audio (tab) and in the 'Preferred Audio Editor' field, seek out the .exe file for your preferred audio editor in the C drive.

Sorry, I know how to change the audio editor, my query is the format of the .wav file that Vegas creates - it is currently 32-bit IEEE float, can this be changed so when I click Open Copy in Audio Editor I get a 16-bit .wav file created?

Try changing the VP audio bit depth to 16 or 24 in the "File> Properties> Audio" menu.

I only use Sound Forge 9 and 15, I see a difference in the file format that Vegas 15 exports:

Open in Sound Forge

Open Copy in Sound Forge

Likely Open in Sound Forge shows the properties of the actual camera file, While Open Copy in Sound Forge renders the audio from the timeline for export to the outside editor.

I haven't found a way to control the behavior in an Internal setting or Project Properties.

It was already set to 16-bit but changing it to 24 doesn't seem to have any effect - the .wav file Vegas creates always seems to be 32-bit. I haven't been using Vegas V15 for that long and not done any editing since before lockdown last year so I think I'll reinstall V14 tomorrow and see if that is the same.

@MCFC-Fan
Try a reset first - follow the instructions exactly
https://www.vegascreativesoftware.info/us/forum/faq-how-can-i-reset-vegas-pro-to-default-settings--104646/

Update: Reinstalled V14 today, used the same source file as with V15, clicked on Open Copy in Audio Editor and the .wav file created is 16-bit:

I also have a copy of V16 that has never been used yet, tried it here and the same results as for V15 - 32-bit IEEE float .wav file created.

At least this solves my query as to why it used to work as I must have used V14 for the whole of football season 2019/20 before lockdown hit us, but it does raise a few queries:

1. why is there no control over the format of the .wav file created in V15 & V16?

2. why doesn't the .wav file created use the Project Audio setting File -> Properties -> Audio?

3. in the Project Audio settings there is no 32-bit option in either V15 or V16, so why create the .wav file as 32-bit?

4. is 32-bit common now in the audio world and do most applications now handle it?

I do have a workaround using Sound Forge to convert the .wav file to 16- or 24-bit but this adds many extra steps to fix something that used to work so well for me in V14.

A new take (16 or 24 bit) could be created in VP and use "Open in Audio Editor", which opens the file directly. Unfortunately it is still an additional step.

"is 32-bit common now in the audio world and do most applications now handle it?"

32 bit is still not all that 'common' in the acquisition world. 24 bit is the most"common" bit depth for most. Most 'Pro' DAWs and editors support floating point 32 bit PCM files. Many NLE do not.