Time Stretch - doesn't work for me either! -Sound Forge - PC

Subject:Time Stretch - doesn't work for me either! Posted by: rdwhitehill Date:5/15/2004 10:11:22 AM Hi all, Read other posts about timestretch not working in v7.0a (I use SBSF)... Sony, it just doesn't work in v7.0a!!! Help! Need to do tempo adjusts! I don't have v7.0 to fall back to... sure hope that I don't have to drop back to v5! Sony tech support, can you help here? Thanks! Doug Whitehill
Subject:AhHa! TimeStretch problem glitch found!!! Reply by: rdwhitehill Date:5/15/2004 10:33:49 AM Hi again, Found out something significant here... Out of frustration, I re-installed v5.0f (the ol' Sonic Foundry reliable...) Guess what showed up in v7.0a? Yup, the TimeStretch ExpressFX! Well... so when I previously uninstalled v5.0f, and then installed v7.0a after I bought it, something didn't work right... Now the question is --- Is it that the uninstall of v5.0f screwed things up, or is v7.0a buggy and adding back v5.0f fixed the glitch? Seems like the install/uninstall routines aren't doing proper housekeeping of the ExpressFX plugins... ... Hmmm... Please, Sony folks, take a look at this problem. Others have the same concern that TimeStretch doesn't work. But for now, with two different versions installed on my PC, I have all of my effects. A definite kludge, but it works... Doug Whitehill
Subject:RE: AhHa! TimeStretch problem glitch found!!! Reply by: Rednroll Date:5/16/2004 7:30:36 AM I don't have Sound Forge 5 or SF6, installed on one of my PC's and just have v7.0a. They where installed at one time and I uninstalled them. The Express FX Timestretch appears in my DX folders, so I'm not seeing the samething you are. Another thing is that the Timestretch option also appears under the Process menu within Sound Forge 7.0a. The other thing is that v5.0 is Sonic Foundry branded and uninstalling this, will remove the Sonic Foundry plugins. Installing SF7.0, will install those plugins but will be located under the "Sony" plugin folder, because they are Sony branded for 7.0. Is it possible you where looking for the plugin, under the Sonic Foundry folder, where you should have been looking is under the Sony folder?
Subject:Problem with uninstall/install routines, I think... Reply by: rdwhitehill Date:5/16/2004 1:30:27 PM Hi Rednroll, I'm thinking the same type of things that you are... After I uninstalled both versions of SoundForge, and I manually scrubbed Registry of all hive keys associated with both the SonicFoundry and Sony versions of SF, and then reinstalled only v7.0a... All is just fine. Obviously (at least to me!) the uninstall routine for v5.0f goofed up Registry hooks for the v7.0a effects plugins, even though the affects plugins are physically stored in different locations on the HD. Anyway, I'm fine now with all ExpressFX working in SBSF v7.0a.. Moral of story: Sony folks: There are a lot of us veteran SonicFoundry folks out there that are upgrading from SF to Sony versions of things. Maybe it would be worth it to take a look at the uninstall/install routines to be sure that they don't cause this type of problem from occurring. Thanks for considering this... Doug

Subject:Time Stretch - doesn't work for me either!

Posted by: rdwhitehill

Date:5/15/2004 10:11:22 AM

Hi all,
Read other posts about timestretch not working in v7.0a (I use SBSF)...
Sony, it just doesn't work in v7.0a!!! Help! Need to do tempo adjusts!
I don't have v7.0 to fall back to... sure hope that I don't have to drop back to v5!
Sony tech support, can you help here? Thanks!
Doug Whitehill

Subject:AhHa! TimeStretch problem glitch found!!!

Reply by: rdwhitehill

Date:5/15/2004 10:33:49 AM

Hi again,
Found out something significant here...
Out of frustration, I re-installed v5.0f (the ol' Sonic Foundry reliable...)
Guess what showed up in v7.0a? Yup, the TimeStretch ExpressFX!
Well... so when I previously uninstalled v5.0f, and then installed v7.0a after I bought it, something didn't work right...
Now the question is ---
Is it that the uninstall of v5.0f screwed things up, or is v7.0a buggy and *adding back* v5.0f fixed the glitch?
Seems like the install/uninstall routines aren't doing proper housekeeping of the ExpressFX plugins... ... Hmmm...
Please, Sony folks, take a look at this problem. Others have the same concern that TimeStretch doesn't work.
But for now, with two different versions installed on my PC, I have all of my effects. A definite kludge, but it works...
Doug Whitehill

Subject:RE: AhHa! TimeStretch problem glitch found!!!

Reply by: Rednroll

Date:5/16/2004 7:30:36 AM

I don't have Sound Forge 5 or SF6, installed on one of my PC's and just have v7.0a. They where installed at one time and I uninstalled them. The Express FX Timestretch appears in my DX folders, so I'm not seeing the samething you are. Another thing is that the Timestretch option also appears under the Process menu within Sound Forge 7.0a. The other thing is that v5.0 is Sonic Foundry branded and uninstalling this, will remove the Sonic Foundry plugins. Installing SF7.0, will install those plugins but will be located under the "Sony" plugin folder, because they are Sony branded for 7.0. Is it possible you where looking for the plugin, under the Sonic Foundry folder, where you should have been looking is under the Sony folder?

Subject:Problem with uninstall/install routines, I think...

Reply by: rdwhitehill

Date:5/16/2004 1:30:27 PM

Hi Rednroll,

I'm thinking the same type of things that you are...

After I uninstalled both versions of SoundForge, and I manually scrubbed Registry of all hive keys associated with both the SonicFoundry and Sony versions of SF, and then reinstalled only v7.0a...

All is just fine. Obviously (at least to me!) the uninstall routine for v5.0f goofed up Registry hooks for the v7.0a effects plugins, even though the affects plugins are physically stored in different locations on the HD.

Anyway, I'm fine now with all ExpressFX working in SBSF v7.0a..

Moral of story: Sony folks: There are a lot of us veteran SonicFoundry folks out there that are upgrading from SF to Sony versions of things. Maybe it would be worth it to take a look at the uninstall/install routines to be sure that they don't cause this type of problem from occurring. Thanks for considering this...

Doug