|
Subject:How about just OPENING THE FREAKIN WAV FILE??!!
Posted by: sk
Date:3/22/2003 10:34:02 PM
Well, against my own better judgment, I decided to update to 6.0 e. (Fortunately, I did a full image back up first, from past experience with Sound Forge updates.) Good thing. After opening up a couple thousand wav files with 6.0 No Letter next to the 6.0, the first time I clicked on a wav file I got an error message. Hmmmmm...I spent the entire afternoon opening up wav files in/with 6.0 prior to the 'update', I don't think THIS is a good sign. So I right clicked on the wav file, selected Sound Forge, and got the same error message. So I tried "other", selected Sound Forge, and got the same error message. So then I remembered seeing something in the options about "Associations". So I went into that, selected ".wav", closed out, tried to open a wav file by clicking on it in Windows Explorer, and gee...guess what? THE SAME FREAKIN ERROR MESSAGE! You know, it's no wonder people just get fed up with this crap. One day, I WILL find a program that works properly; consistently; etc. (The files DO open at least THROUGH Sound Forge, just not clicking on the file itself in Windows Explorer. And YES, I DID go through Tools/Folder Options etc. to double check that Sound Forge IS the associated program, which it IS. And yes, of COURSE I did the ceremonial REBOOT, and NO, it still does not work.) Now I'd love to hear somebody tell me how this couldn't POSSIBLY have anything to do with the freakin update! sk |
|
Subject:RE: How about just OPENING THE FREAKIN WAV FILE??!!
Reply by: MyST
Date:3/22/2003 10:44:09 PM
Well, I can not only open wav files in SF, but I can also preview with no probs. So, I guess that means that "this couldn't POSSIBLY have anything to do with the freakin update!" :) Did you try re-downloading? Did you download the patch, or the complete program? M |
|
Subject:RE: How about just OPENING THE FREAKIN WAV FILE??!!
Reply by: sk
Date:3/22/2003 10:54:33 PM
Complete program. |
|
Subject:RE: How about just OPENING THE FREAKIN WAV FILE??!!
Reply by: sk
Date:3/22/2003 11:04:59 PM
Oh...but WAIT...it GETS EVEN BETTER! Yeah, I can open the files in Sound Forge 6.0e, and I THOUGHT it even let me SAVE IT. Until I checked in the folder it was supposed to be SAVED TO, and GUESS WHAT? IT was GONE. POOF! Just GONE! LOVELY! Again, fortunately I had an intact back up file. This is just unbelievable! Maybe if they charged even MORE money for their buggy program(s) they could afford to put out something that WORKS! sk |
|
Subject:RE: How about just OPENING THE FREAKIN WAV FILE??!!
Reply by: Iacobus
Date:3/23/2003 10:24:36 AM
Whoa. Calm down. Take a breather. Have you tried completely uninstalling Sound Forge and then reinstall using the full 6.0e update? (It's actually the full version that can also act as a demo.) Keep your Sound Forge serial key handy if you do this. HTH, Iacobus |
|
Subject:RE: How about just OPENING THE FREAKIN WAV FILE??!!
Reply by: sk
Date:3/23/2003 11:58:44 AM
Uh, duh. Yes, I COMPLETELY uninstalled 6.0. And yes, I DID need my handy dandy serial number. (I often get the feeling that a lot of these update problems, especially with Sonic Foundry products, arise more out of the company's attempts at security measures than from actual real world-program related ones.) And, NO, I don't think I need to 'calm down'; what I think I need to do is find a better audio editing program. This company has shown time and again that it is deaf dumb and blind to the problems encountered by its users. And it's just a matter of time now before other companies knock Sonic Foundry down a peg or two or more. Customers should NOT have to put up with this kind of nonsense simply doing an 'update' to fix bugs that were inherent in the program to begin with. It simply adds insult to injury. Maybe you relish in wasting hours upon hours of your time, but I don't. And if it weren't for the fact that I had not only an intact system back up image, but a full data back up image as well, then it wouldn't even only have been a matter of losing the time wasted putzing around with the buggy update; I would have lost the file and all the work I'd put into it over the past few weeks as well. Again, maybe you relish in that sort of torture; I certainly do not. And if somehow the human emotion of justifiable outrage bothers you, then most respectfully that's your problem, not mine. You deal with your tech issues the way you choose and give others that same courtesy. I'm not asking for your opinion(s) on how I express myself; I did not use any profanity and posted what I consider to be an appropriate gripe under the circumstances. If you have something constructive to contribute to the actual issue, fine; if not, kindly keep your opinions on anything not related to the issue(s) to yourself. sk |
|
Subject:RE: How about just OPENING THE FREAKIN WAV FILE??!!
Reply by: Geoff_Wood
Date:3/23/2003 10:25:27 PM
Have you considered the possibility that you may just have something a little rooted in you system ? Like, the 6.0e update was not created especially to annoy *you*, and others don't seem to be having your problem ..... geoff |
|
Subject:RE: How about just OPENING THE FREAKIN WAV FILE??!!
Reply by: musicvid10
Date:3/24/2003 12:42:49 AM
And I, for one, have never had a "FREAKIN ERROR MESSAGE" on my computer, even after several years with different versions of Sound Forge on my computer. Could you please enlighten us, or do these only show up if one is a fan of phish? |
|
Subject:RE: How about just OPENING THE FREAKIN WAV FILE??!!
Reply by: sk
Date:3/24/2003 12:57:31 AM
The general gist of the error message was that it could not open the .wav file I was clicking on because there was no program associated with it. It then suggested that I associate a program with it manually via Windows Explorer/Tools/Folder Options, etc. The 'problem' was that it was ALREADY ASSOCIATED, CLEARLY, WITH a PROGRAM in Windows Explorer - Sound Forge! Logo icon and all. Right clicking and trying the option of "Open With", a nice feature of W2K, did not work either; it generated the same error message. Although every other program listed in the "Open With" feature did work - Winamp, Media Player, etc. And after reinstalling the Drive Image snapshot of my exact hard drive just prior to installing 6.0e, everything worked exactly as it was supposed to; the way it did before the wonderful 6.0e update. The only thing that did not work after the 6.0e update was Sound Forge. And as I stated above, when it came to actually LOSING the file, rather than saving it and/or not being able to open it in the first place, that was the last straw. I don't have a clue what your reference to phish is about; obviously, it has nothing to do with this issue. And as is always the case with wonderful posts stating: "Well, I don't have that problem, so I don't know why you do", it doesn't even merit a response. sk |
|
Subject:RE: How about just OPENING THE FREAKIN WAV FILE??!!
Reply by: ATP
Date:3/24/2003 4:53:30 AM
SF is obviously not for you. try Goldwave, it might suit your needs better. seriously, your ACCENTUATED words and EMOTIONAL replies are NOT helping you in getting your PROBLEM solved. take it easy, relax, calm the f* down! got it? good. first, post the *exact* error message here. we can't do squat with info like "an error message appeared". be more specific. what does it say precisely? second, list your system specs. if you're running a 486DX with 8 mb EDO RAM, to give an example, you're going to get funny messages no matter what. |
|
Subject:RE: How about just OPENING THE FREAKIN WAV FILE??!!
Reply by: SonySteveS
Date:3/24/2003 1:10:39 PM
SK, you do seem to have uncovered a legitimate bug. It only occurs under certain conditions, which is why other people aren't seeing your problem. Luckily, there is a very simple workaround which doesn't even involve reinstalling. Please try this and let me know how it works for you. In Windows Explorer, associate wave files with another application (like Windows Media Player). Now open Sound Forge, go to the File tab of the Properties dialog and click on the Associate Sound File Extensions button. Check the box next to wav and hit OK. Hope that helps! Steve |
|
Subject:RE: How about just OPENING THE FREAKIN WAV FILE??!!
Reply by: sk
Date:3/24/2003 7:01:24 PM
Well, Steve, thanks for your response. Unfortunately, I tried what you suggested, after having to first reinstall the full update again, and it did not work. Now my system is screwed up, and I was just getting ready to work on some more files. So if you'll excuse me, I need to re-install the Drive Image I did before installing 6.0e the first time. At some point, if/when you get this thing worked out, I'll try whatever you suggest. As far as feedback, the setting to associate .wav files with SoFo 6.0e, either from within SoFo itself (which is the only thing I tried this time), or via Windows Explorer (which I tried the first time) simply would not take. I tried it a number of different ways; rebooting in between; not rebooting; it made no difference. The wav files are simply not recognized as being associated in any way, shape, or form with SoFo. And as I stated in one of my posts above in this thread, the inability to associate the files is bad enough; outright losing the files is another matter entirely. I trust you are making every possible effort to warn SoFo users of that possibility. sk |
|
Subject:RE: How about just OPENING THE FREAKIN WAV FILE??!!
Reply by: SonySteveS
Date:3/25/2003 11:57:53 AM
SK, please try again using the steps I described above. Disassociate wave files from Sound Forge through Windows Explorer, and then associate them through the Sound Forge preferences. If that doesn't work, go back and associate them with Forge through Windows Explorer. It may give you an error message on the first try, but should work fine after that. As far as saved files disappearing, we haven't come across any problem like this in our testing, nor am I aware of any other users reporting such behavior. Can you reproduce the problem, or was this a one time occurence? Thanks, Steve |
|
Subject:RE: How about just OPENING THE FREAKIN WAV FILE??!!
Reply by: sk
Date:3/25/2003 11:26:18 PM
Well, I must report that despite the fact that I did everything exactly the way I did last time, with the exception of this time choosing Media Player, rather than Winamp, as the program with which to initially associate .wav files in lieu of Sound Forge, before switching back to Sound Forge from inside Sound Forge's options section, the problem I was experiencing before does now appear to be solved. Thanks for your input, Steve. sk |
|
Subject:RE: How about just OPENING THE FREAKIN WAV FILE??!!
Reply by: sk
Date:3/26/2003 8:38:45 PM
And here's a bit of a related update. While 6.0e is now functioning on my system (at least with regard to the file-association/recognition problem) , I've noticed, dating back to 6.0 "no letters", that frequently when I choose a decibel level at which to normalize (which is never above -22dB, so clipping or any other such compensation action is not necessary; I'm just using it as a volume/gain control and not as a typical normalization control), the level that gets established is .01db less than the one I chose. I verify this by running just the scan function of the Normalization process/tool on the file after the transform. However, when I run the full normalize - not just the scan - a second time, then it correctly changes the level in accord with the exact setting I chose; not .01 off. Maybe you still have a few bugs to still work out. I can tell you this - it certainly does not inspire confidence when a program doesn't properly execute basic functions such as DC Offset and Normalize/Volume Control, etc. sk |
|
Subject:RE: How about just OPENING THE FREAKIN WAV FILE??!!
Reply by: MJhig
Date:3/26/2003 9:13:45 PM
SK, if you and stusy aren't buds already, you two should get together for a beer and discuss the manor of things such as updates and presets pertaining to daily life. MJ |