SoundForge7:Someone over there at Sony/SoFo is asleep at the wheel

Bill Ravens wrote on 11/4/2003, 8:48 AM
Sony/Sofo has pulled a fast one on us. I installed Sound Forge 7 to its own folder but put the common plugins in the SoFo folder. Lo and behold, my MPEG and MP3 codecs were gone!! Doing an uninstall didn't help either, because the install software for SF7 had quit asking what folder I wanted things installed to, it assumed my frst choices!! I finally went into the registry and deleted the Sony entries, which, by the way, were NOT uninstalled by uninstalling Sound Forge 7. Now, after reinstalling everything, it asked me what directories I wanted and everything is right with the world. Turns out SF7 uses UNICODE for the MPEG and MP3 files, while the older SoFo files use DBCS...and the two are NOT COMPATIBLE.

So, SONY, next time give us a warning or don't give us the choice to change default directories. Nice little trap, eh? I'm not pleased with your oversight. I hope this isn't a sign of the QUALITY you're bringing to SoFo products or I will quit using SONY products.

Comments

TheHappyFriar wrote on 11/4/2003, 9:29 AM
They DID give a warning. It's been on the forums about 3-4 threads already. Most programs don't remove their registry entries when they are uninstalled anyway. That's why if you uninstall Vegas and then re-install it, you don't have to re-register the mpeg codec's (usually).

What REALLY sucks that noone has mentioned yet is that Sony/SoFo said that they aways had newer versions of the encoders/codec's in the new versions of the software, so to update the mpeg encoder you just had to download the DEMO of the newest program, install, then uninstall. But now we can't do that!

I have a feeling when they release an update to change all the "sofo" to "sony" names in Vegas they will rename the folders too. Then maybe there won't be any problems, but only if they make the encoders compatible!
Bill Ravens wrote on 11/4/2003, 9:51 AM
well, some people never read these forums anyway, and I never read those threads 'til it was too late. Obviously, neither did the thread posters, else they wouldn't have the problem. I think it's pretty brain dead to build in an option into the installer that causes a problem like this, without FIRST providing a warning. This is the kind of behavior that drove me away from Adobe, in the first place.

So, I don't consider an "after the fact" warning to be suitable.

If you look in the registry for SF7, you'll see placeholders for DVDA..hehehehe.
vitalforces wrote on 11/4/2003, 1:49 PM
Did you make a complaint to the tech support page?