Subject:Who is going to finally fix this long standing bug! This is rediculous.

Posted by: sreams

Date:1/30/2002 5:48:01 PM

Recipe:

Open a .wav file in Sound Forge 5.0. Select a portion of the audio. Open the plugin chainer. Add two different Waves plugins. Press Preview. During the preview, right-click in the lower right blank area of the chainer, and choose "Select All Data". This always results in either an excessively long pause or a crash. SF4.5 never had this issue. -Every- version of SF5.0 has. I've been vocal about it since 5.0's initial release, and it is -still- being ignored. Why?

-S

Subject:RE: Who is going to finally fix this long standing bug! This is rediculous.

Reply by: Rednroll

Date:1/30/2002 11:37:18 PM

Reminds me of that Rodney Dangerfield skit:

"I went to the Doc and I say to him, 'doc it hurts when I do this'...doc says well stop doing that then.."

Subject:RE: Who is going to finally fix this long standing bug! This is rediculous.

Reply by: rraud

Date:1/31/2002 2:47:12 PM

Red,
I think that was Henny Youngman, who also said, "take my wife.. Please!" or was it Buddy Hackett?
Anyway, thanks for the LOL.

Subject:RE: Who is going to finally fix this long standing bug! This is rediculous.

Reply by: sreams

Date:1/31/2002 4:11:22 PM

Nice... except that it is a serious hinderance to have to work around this. SF4.5 is more efficient. It's a nasty crash bug and should be fixed, not ignored.

Subject:RE: Who is going to finally fix this long standing bug! This is rediculous.

Reply by: sreams

Date:1/31/2002 4:14:52 PM

BTW... this crash occurs when simply changing the order of the plugins during a preview. It's a hinderance to work flow. Don't ask me to avoid working in an intuitive and efficient manner to get around an obvious flaw that should have been fixed with the very first patch.

Subject:RE: Who is going to finally fix this long standing bug! This is rediculous.

Reply by: Rednroll

Date:2/1/2002 9:02:16 AM

"Don't ask me to avoid working in an intuitive and efficient manner to get around an obvious flaw..."

I don't believe anyone on this forum is asking you to do anything. If you would like other users to re-create the bug you've found, then please describe in detail what plugins you where using and the version, and what the order was in the plugin chainer and the settings in the plugin. Maybe then other users will say they are having the same problem or it might be a problem specific to your system. In any case, this forum is NOT the place to be whining about bugs, this is a "User Forum" and us "Users" don't write any of the code to fix your bug. If you find you can't work in an intuitive manor with Sound Forge and feel you're not getting the support you deserve, then I would suggest you move onto another piece of software that gives you what you need. Maybe you should try a more professional PC piece of software, like Cakewalk....lol. I'm really not defending Sonic Foundry on this issue, if it indeed is an issue, but if you're as vague and bitchy, in describing the problem as you are in this forum, then they're probably having a hard time recreating your problem to address it correctly and is therefore easily understood why it hasn't been fixed. Every bug that I've ever reported to SF I have given them details on what I was doing and what I was using when the bug appeared, and everyone of my bugs has been fixed. You also mention "Waves" plugins, have you ever thought it might be "Waves" is where the bug is? I know you mentioned it works on v4.5, but v4.5 didn't support 24bit or 32 bit processing, so maybe your waves plugin doesn't work well with the newer architecture of v5.0.

Good luck,
red

Subject:RE: Who is going to finally fix this long standing bug! This is rediculous.

Reply by: sreams

Date:2/1/2002 4:13:14 PM

This is a User's forum and is a place where users can talk about how "useable" the software is... and it is frequented by SF staff who address these very issues. There is no need for anyone here to filter their commentary on the app because you don't like it. I have posted detailed recipes in the past, and the results have been 100% that this is happening. It occurs with all Waves plugins, regardless of order or type. I have considered that Waves is to blame... I speak with them regularly and they point the finger at SF. Personally, I don't care who is to blame. I want someone to really look into it and fix it. This is not about whining. Would you be silent if every time you clicked on the record button the app crashed? I am frustrated because the response on this particular issue from SF has always been utter silence. If they think it's Waves, they should say so. I have had plenty of other issues directly addressed by SF on this board. This one should not be an exception.

Bottom line... if my post bugs you, ignore it. It wasn't intended for you anyway.

-S

Subject:RE: Who is going to finally fix this long standing bug! This is rediculous.

Reply by: Rednroll

Date:2/2/2002 1:00:33 AM

Sorry, this was the first time I seen any mention of this and I reread your original post and was able to recreate the crash on 1 occassion, other times it hesitated for 2 seconds and then continued. BTW the crash, does not happen if you hit the "stop" button before clicking on the "selection> all sample data", which should not slow down your intuitive work method until SF fixes the bug. I'm sure their resources were probably focused in other areas, like getting Vegas Video 3 released and dealing with initial release bugs, which probably effects MANY users and it made a "1 user" bug with a simple work around a lower priority. Oh, sorry once again, forgot your post was not intended for me, must have been intended for ALL the OTHER "users" on this forum.

Subject:RE: Who is going to finally fix this long standing bug! This is rediculous.

Reply by: sreams

Date:2/3/2002 6:35:26 PM

My point was that the post wasn't intended for people who are bugged by it and don't want to give a helpful reply. I appreciate your second post here. It is an issue for me because I regularly change plugin order during the mastering process. Any stop in playback hinders the creative process... especially when it results in a crash every few times. It frustrates me because I've seen a number of very minor bugs fixed in 6 revisions so far.

Subject:RE: Who is going to finally fix this long standing bug! This is rediculous.

Reply by: MacMoney

Date:2/3/2002 11:59:05 PM

Hi Screams
I opened a stereo 44.1@16bit in SF 5.0f. I selected a section of about 6sec.
I opened the plugin Chainer added Waves C4 and L1 v3.2, I previewed and while playing I selected All Sample Data, Yes I did get about a 6 sec pause and It played fine I did this about 10 times without a crash. This was on my P3 800, Win98se with a Darla 20. I even tried it with my P4 1.7,Win2k with MOTU-1296. Its no big deal to me because I stop the preview when I select All Sample Data.

Good Luck, George Ware

Subject:RE: Who is going to finally fix this long standing bug! This is rediculous.

Reply by: SonicCaveDan

Date:2/4/2002 9:48:38 PM

I, too, have encountered silence in response to specific questions regarding Batch Converter - namely that a script, when executed manually in SF5.0, creates a different result through batch converter, which, unfortunately added clipping. I even sent them example scripts and the A/B sound files and I never heard back. I've addressed other inconsistencies with that product - as well as the drop in usability and functionality due to the fact that the sound previewer was removed from the batch converter (SF4.5 had it right), so you have to used Windows Media Player to preview the before or after files. Does anyone know to whom at SF I could address these thoughts? Thanks for listening ...

dan forden

Subject:RE: Who is going to finally fix this long standing bug! This is rediculous.

Reply by: sreams

Date:2/7/2002 4:01:31 AM

Yes... sometimes it's a pause... but it also occurs when simply re-ordering plugins.