Subject:Glitch Correction Bug

Posted by: Spheris

Date:5/8/2003 9:37:57 PM

Seems the glitch corrector has been broken in 6.0e

strange but true, try doing a scan for peak and see if forge doesn't disappear altogether leaving some really large temp files behind

Subject:RE: Glitch Correction Bug

Reply by: Sonic

Date:5/9/2003 8:56:49 AM

Assuming you mean the Find tool, I'm not seeing any problems. More details please, including file length, format, parameters, and repro steps.

J.

Subject:RE: Glitch Correction Bug

Reply by: Spheris

Date:5/9/2003 10:43:04 AM

seems to occure with any bit depth size of file of wav or raw type

if the peak ratio exceeds 4096/8192

the guy in our office uses a default of 1,38X,XXX or whatever that rediculous ratio is

but I can only imagine the find tool was meant to work with it. he asked me what I thought. I have no clue. But I'm the only one with a net connection here so I seem to get stuck with asking questions. He's afraid of my MAC :)

Thanks for any ideas suggestions, or at least let me know if those lower ratios are what he needs to stick too for the find to not blank the app.

Second question, does the default peak file have anything to do with the resolution of the plugin and process quality. I'm not sure if I see where it would apply but he was asking me and we have no options like that in final cut or peak that I've ever had to deal with.

Subject:RE: Glitch Correction Bug

Reply by: Sonic

Date:5/9/2003 12:42:48 PM

Find should never 'blank' the app, regardless of the length of the file. At the worst, it should go into progress mode while scanning.

How long a file are we talking, here...hours? Perhaps the file is extremely long and the settings are such that the Find is taking a while. The progress bar may move slowly enough or sit on 0% long enough to appear frozen.

I say extremely long because a peak ratio that high would require it, zooming in (lowering the peak ratio) wouldn't change the processing time. The peak file and peak ratio have nothing to do with processing. They affect only visualization.

For the impatient, my best suggestion is to select smaller areas to scan, rather than the entire file, then the Find will bound itself to the selection length.

If the app really is crashing repeatedly and exiting, please provide precise file information (format/size/length/type), a word or two on the content of the media, and the Find settings to reproduce.

J.

Subject:RE: Glitch Correction Bug

Reply by: Spheris

Date:5/9/2003 1:18:18 PM

the app crashes, disappears without a trace, not a waiting/patience issue

average size of file is roughly 5:50 min of 24 bit audio
find peak is the setting and the peak ratio default is set to the maximum

as soon as you press okay, the app disappears with no error shown but does disappear, even from the task manager so it is quitting.

Hope this info helps

Subject:RE: Glitch Correction Bug

Reply by: Sonic

Date:5/9/2003 7:50:30 PM

Try as I might, I can't reproduce in 6.0e. Anybody else out there?

Perhaps a re-install is in order. Probably worth shooting an email to SF tech support, as well, though I'm hard pressed to think of anything internal that could actually kill the entire process without getting caught by the exception handling first.

J.