Noise Reduction in SF 9 - Capture Noise Print? -Sound Forge - Scripting

Subject:Noise Reduction in SF 9 - Capture Noise Print? Posted by: ChrisFontenot13 Date:10/25/2007 8:56:44 AM Is it possible to use a script to 1) Activate the Noise Reduction Plug-in, then 2) Capture a noise print based on the location of a marker, and finally 3) Use one specific preset to reduce the noise in a file. I can figure out how to do 1 & 3, but each tape we have to process has different levels of noise and without #2 being able to script the other two is useless to me.
Subject:RE: Noise Reduction in SF 9 - Capture Noise P Reply by: _TJ Date:10/30/2007 2:34:07 PM Unfortunately, the way noise reduction communicates the noiseprint from pass 1 to pass 2 is to store it in a preset. There is no way for a script to get a preset with a valid noiseprint back from Noise Reduction without showing the Noise Reduction dialog box. And once the dialog is showing, the script stalls until the users hits the OK button. So you can script step 2, but your script will require that someone sits at the computer and hits OK on the dialog. (Actually it's worse than that. They have to check capture noiseprint, then preview, then uncheck capture noiseprint, then hit OK. ) About the best you could do would be to have someone sit at the PC for a while running a script that captures all of the noiseprints and remembering which one goes with which file. Since you would only be capturing noiseprints, that would go pretty fast. Then once all of the noiseprints are captured, you can batch up all of the processing using the correct pre-recorded noiseprint for each file. tj

Unfortunately, the way noise reduction communicates the noiseprint from pass 1 to pass 2 is to store it in a preset.

There is no way for a script to get a preset with a valid noiseprint back from Noise Reduction without showing the Noise Reduction dialog box. And once the dialog is showing, the script stalls until the users hits the OK button.

So you can script step 2, but your script will require that someone sits at the computer and hits OK on the dialog. (Actually it's worse than that. They have to
check capture noiseprint, then preview, then uncheck capture noiseprint, then hit OK. )

About the best you could do would be to have someone sit at the PC for a while running a script that captures all of the noiseprints and remembering which one goes with which file. Since you would only be capturing noiseprints, that would go pretty fast.

Then once all of the noiseprints are captured, you can batch up all of the processing using the correct pre-recorded noiseprint for each file.

tj