Yes, the preset exists and it increases volume by 1 dB. The script works with SF15 build 64 but if I apply later updates it stops doing anything. The script runs, there is no error message but the waveform remains unchanged.

I'm trialing the latest SF16 and it is working better than v15 build 64 with iZotope RX 9. However it still doesn't process my scripts for changing volume. It works with those using built in system presets eg:

using System;
using System.IO;
using System.Windows.Forms;
using SoundForge;public class EntryPoint {
public void Begin(IScriptableApp app) {   app.CurrentFile.DoEffect("Volume",
                            "[Sys] 6 dB Cut (50 %)",   // this must be the name of a Volume preset.
                            app.ActiveWindow.EditRegion,
                            EffectOptions.EffectOnly);
   app.CurrentFile.WaitForDoneOrCancel();
}public void FromSoundForge(IScriptableApp app) {
   ForgeApp = app; //execution begins here
   app.SetStatusText(String.Format("Script '{0}' is running.", Script.Name));
   Begin(app);
   app.SetStatusText(String.Format("Script '{0}' is done.", Script.Name));
}
public static IScriptableApp ForgeApp = null;
} //EntryPoint

But for presets I've named myself nothing happens. The scripts compile OK and run without error but just don't change the volume. This problem began with SF15 later builds.

I really need a quick way to change volume. Can anyone suggest changes to my code or alternative code that will allow changes to volume by 1 to 6 decibels? Thanks.

• I deleted the custom preset and I changed EffectOptions.EffectOnly to EffectOptions.DialogFirst.
• Then I ran the script. The Volume-Dialog opened. I created the preset and saved it under a name.
• Then I canceled the process.
• Then I changed EffectOptions.DialogFirst back to EffectOptions.EffectOnly.

It now works every time without problems. Even after restarting the application.

Brilliant SP! What ever gave you the idea of recreating the scripts using DialogFirst? Initially I had some trouble as SF wouldn't let me delete the existing presets. They would reappear after I reopened the volume dialogue. So I just copied and pasted the preset names from the script and saved them afresh. I wasn't prompted to rename them so I suspect the whole dialogue is flaky. I've opened and closed Sound Forge and so far so good. The scripts work. Thank you so much.

I am experiencing the same problem, with some differences. My script, which still works in SFG13, tries to use a graphic-fade preset. Whether I use one I made myself or a factory preset, the script always applies a linear fade-in instead of the preset I request, as though I had instead used the <PROCESS - FADE - IN> menu option. It does the same if I enter a bogus preset name, which makes me think it isn't even looking at the name. Maybe it is defaulting to a linear fade-in when it sees no name? Has the way the interpreter handles arguments changed?

The work-around SP described above more-or-less works for me, although I notice the preset I save does not show up in the preset list afterwards. Also, when the script asks for a dialogue first, the drop-down list does *not* include other presets I have made. I guess it must be storing a second list elsewhere? Seems like this is the problem: User presets are stored in one place, and the scripts are looking at a different copy of the list.

@Kurt-Larson I think most effects in Sound Forge are DirectX plugins.

If I remember it correctly the user presets were stored in the Windows registry under HKEY_USERS\*long-ID-number*\DirectShow\Presets and HKEY_CURRENT_USER\SOFTWARE\DirectShow\Presets

Thanks SP, but... hm. I'm not sure how this information connects...

If you just mean it is a place to check for info, sure. But the problem seems to be that SFG16 is maintaining two separate sets of presets.

@Kurt-Larson If you search for your custom preset name and it's not in the registry it could be a bug (and maybe the cause of our scripting problem) or the developers changed something in the preset system, like you already suspected, and broke functionality. I don't know if DirectX plugins presets must be stored in the registry.

Hello everybody. I am looking for an up-to-date Sound Forge API for scripting (basically in C#). The one I possess is dated at April 2005. Is there anything newer, or I can still use the one from 2005 year  in SF Pro versions grater than 11? Thanks for your response.

@ArsDigita Everything is described in the Help file plus there are some sample scripts. Have you already installed the newest, free trial version?

The latest SDK (version 11) I have is from 2013, but a lot of included files are from 2005 or 2009. I can send it to you, if you want.

I think most effects in Sound Forge are DirectX plugins.

Most of the legacy Sonic Foundry and Sony plug-ins are DX. Track FX, Express FX plugs, delay, EQs, reverb and time stretch.. among others.

I haven't checked it out with newer versions of SF. I would greately appreciate if you could send me the 2013 SDK. It’s still better than the 2005 one. Thx in advance.

Hello there. Have just tested the 2013 SDK with the newest version of SF and Visual Studio compiling and debugging scripts in C#. It all works just fine, assuming you are using .NET Framework 4.0 and greater. In addition SF 17 provides the whole SDK description in it's help system. So, there is no need to have it open from a separate file.

Since I am relatively new to SF scripting. Can someone advise me on how to create a dockable window similar to those available from "view" menu (I mean windows such as Time Display, Channel Meters or Spectral Analysis). I want my script to be dockable within the SF's workspace. Is that possible at all with script evoked windows?

@ArsDigita If there is nothing about this in the description or the SDK then I don't think you can do this.

I've just updated to sound Forge Pro 18 and the fix by SP no longer works. The script compiles OK but doesn't run. Does any one know how to change the volume using scripting and SF18? Thanks.

@Unsounded Are you trying to use system presets or user presets?

Have you tried to save a system preset first under a new name as a user preset?

Thanks for the reply. I was mistaken. I was working with the wrong script folder. Your original method works with SF18. I have my scripts working correctly now. Your approach was and is a stroke of genius.