Community Forums Archive

Go Back

Subject: SoundForge Pro 10 506
Posted by: sergiob
Date: 10/31/2012 12:26:24 PM

Has been released.
Notable fixes/changes:

Updated Noise Reduction, Acoustic Mirror, Wave Hammer, and élastique Timestretch for 64-bit compatibility when used with Vegas Pro 12.0.


Message last edited on 10/31/2012 12:33:03 PM by sergiob.
Subject: RE: SoundForge Pro 10 506
Reply by: iain_m
Date: 10/31/2012 12:40:51 PM

Wait, what? Those are the *only* changes? Not a single bug fix?

Subject: RE: SoundForge Pro 10 506
Reply by: mikkie
Date: 11/1/2012 7:03:16 PM

Breaks Creative Soundblaster ASIO drivers

Haven't attempted any diagnosis or anything more in depth -- just a quick heads up.

win7 ult 64 SP1, fired up Wondershare Timefreeze did the install, fired up S/Forge, message there were no Creative ASIO devices -- same when fired up Vegas Pro. Turned Timefreeze off, system re-booted putting everything back, ASIO works fine.

Edit: here's the text I sent to tech support:

Installing over previous version, when any Sony apps started there was an error, no Creative ASIO hardware found, & Creative [Soundblaster] ASIO drivers/device was not available in preferences. Troubleshooting, found renaming existing SF folders prior to running soundforgepro10.0.506.exe everything works.

Details: Copied app folders after installing in a win7 VM. Monitoring registry etc. [regshot2], individually re-named 3 folders [for app, NR, & Shared Plug-ins] & copied new in place - worked all 3 times. Performed monitored install of NR & SF separately - both worked. Copied files from old Shared Plug-ins folder that were missing in new folder - everything worked. Believe [logically I think] that 1 or more incompatible files remain when SF 10 updated.

Perhaps you might want to verify & add to knowledge-base?

Message last edited on 11/3/2012 11:21:12 AM by mikkie.
Subject: RE: SoundForge Pro 10 506
Reply by: FTech
Date: 11/5/2012 4:29:46 PM

Hi mikkie,

I updated my Sound Forge back in April 2012 to version 10.0d, build 503. In the released notes there was no "Notable fixes/changes in Version 10.0d" section anywhere, only for 10.0c when I updated back then.

When I seen the release notes for this latest version of build 506, there is the version 10.0d fixes/changes section. I'm thinking, I already got version 10.0d several months ago. My question is... what is the latest version called... 10.0e build 506?

Like you mentioned it broke your Creative ASIO drivers. Seems like I'm going to hold off updating to this version since I have Creative ASIO drivers as well.

FTech

Subject: RE: SoundForge Pro 10 506
Reply by: iain_m
Date: 11/5/2012 5:57:04 PM

By the way, are the updated effects now also installed as 64-bit VSTs for use in Vegas? Or are they still DirectX-only?

Subject: RE: SoundForge Pro 10 506
Reply by: mikkie
Date: 11/5/2012 8:33:13 PM

> "When I seen the release notes for this latest version of build 506, there is the version 10.0d fixes/changes section. I'm thinking, I already got version 10.0d several months ago. My question is... what is the latest version called... 10.0e build 506?"

I've got the same thing, v. 10.0 d (Build 503) for the April 2012 version, & the new one is 10.0d (Build 506). Microsoft's Windiff shows 71 files being updated [out of 259], including Forge100.exe, the main app file itself.

> "Like you mentioned it broke your Creative ASIO drivers. Seems like I'm going to hold off updating to this version since I have Creative ASIO drivers as well.

Might not be a bad idea if you don't have Vegas Pro 12, at least until certain there's no further audio updates in the near-term. I've been reading in the Vegas Pro forum that Sony wasn't done yet, that there would be additional downloads to get the audio end of things working properly. That may be rumor, or flat out wrong, or the SF update may have been what people were talking about, or there may be other updates to finish the job -- I've no idea. So far I don't see any problems with other software Googling "Sound Forge 10d update breaks", but it's still pretty new.

According to the SF notes for 10.0d (Build 506):
"Updated Noise Reduction, Acoustic Mirror, Wave Hammer, and élastique Timestretch for 64-bit compatibility when used with Vegas Pro 12.0."

On the Vegas Pro 12 Pro Overview page it says:
" Vegas Pro 12 includes support for new 64-bit versions of Sony's Noise Reduction 2.0, Wave Hammer, Acoustic Mirror, and more."

On the Vegas Pro 12 Pro Audio Tools page it says:
"Vegas Pro software includes essential effects such as Wave Hammer Compression, EQ and Noise Gate, as well as Reverb, Chorus, and Delay. 5.1 DirectX® effects for the master bus include EQ, Dither, and Wave Hammer Surround compression tools"

And

"Previously, a number of Sound Forge Pro 32-bit plug-ins did not work in Vegas Pro 64-bit versions. These plug-ins have been re-written for 64-bit and are now compatible with Vegas Pro 12. The updated plug-ins include the four Noise Reduction 2.0 plug-ins (Audio Restoration, Click and Crackle Removal, Clipped Peak Restoration, and Noise Reduction), along with Acoustic Mirror, Zplane élastique Pro timestretch, and Wave Hammer."

When I monitored the Vegas Pro 12 install I saw it replaced some of the files in the Shared Plug-ins folder, & over-wrote some of the registry settings for the existing SF plug-ins, pointing to the Vegas stuff instead. A few of those changed registry entries were system-wide, effecting any software that wanted to use those plug-ins. The whole thing made me nervous enough that I decided I'd try the SF update, & if I hadn't been able to get it working, I would have put everything having to do with audio back to the way it was before I installed Vegas Pro 12. I'm still hedging my bets with backups of Sound Forge etc after last spring's update, & logs of everything Vegas Pro 12 changed in the registry so I can put things back if needed.

Subject: RE: SoundForge Pro 10 506
Reply by: mikkie
Date: 11/5/2012 8:34:24 PM

> "By the way, are the updated effects now also installed as 64-bit VSTs for use in Vegas? Or are they still DirectX-only?"

All DX.

Subject: RE: SoundForge Pro 10 506
Reply by: iain_m
Date: 11/6/2012 6:23:49 AM

Thanks for the detailed information, mikkie!

Subject: RE: SoundForge Pro 10 506
Reply by: JoeMess
Date: 11/6/2012 11:58:12 AM

I will have to look when I get home and give it a try, but Sound Forge 10 is my only app that didn't survive the upgrade to Windows 8. I have to install fresh according to MS app compat.

Subject: RE: SoundForge Pro 10 506
Reply by: rraud
Date: 11/7/2012 10:44:08 AM

FWIW, The below message was posted a month or so ago:

( PS- OT.. I survived Hurricane Sandy, but tree fell on house, luckily there is minimal structural damage, but loss of power, internet, ect. Still no power, ect. as of today. )


"A few months ago SCS issued a subsequent build for Sound Forge Pro-10.. no release notes or other info. I suspect the same thing with AS.
'SonySQAPete' kindly responded to our inquiry.

"Sometime last year we'd discovered a bug that impacted all of our applications that'd manifest in a situation where they (the applications) simply wouldn't run when launched on one certain, rare type of low-power CPU. (An AMD C-50, to be exact.)
The bug was quickly fixed and the fix was ported into all of our applications over the course of the normal update cycle, including Sound Forge.
That update was 10.0d. There were no release notes, as the bug we were fixing wasn't something that the overwhelming majority of our users would ever see. I hope this answers your questions about 10.0d.
"

Go Back