Thank you so much for the helpful suggestions!

Gale Andrews wrote: So I think the answer is no, unless you are skilled at

AutoHotkey or similar and wrote some kind of macro that iterated the curve to be used and the file name to be written to.

Gale – I’ll need to learn the syntax, but AutoHotKey looks like it could help me automate this and various other aspects of my research. It’s definitely worth exploring!

Trebor – this wouldn’t quite accomplish my goal, but I might be able to make it work if I can use the Nyquist prompt to apply a filter that changes in

*discrete *steps.

For a simple case, let’s say I have two examples of birdsong that I want to simulate at 20m, 40m, and 60m. My current method is to string the examples of birdsong together into one audio file, then apply each filter independently:

[song1…song2…] -- apply curve20m --> all songs at 20m

[song1…song2…] -- apply curve40m --> all songs at 40m

[song1…song2…] -- apply curve60m --> all songs at 60m

If I could use the Nyquist prompt to apply filters in discrete steps, I could change my methods such that the filter changes over time rather than the example song:

[song 1…song1…song1…] -- apply curve20m…curve40m…curve60m --> song1 at all distances

[song 2…song2…song2…] -- apply curve20m…curve40m…curve60m --> song2 at all distances

Would it be possible to specify different curves to be applied every X seconds using the Nyquist prompt? The equalization curves themselves are fairly complex – our model for attenuation takes into account atmospheric absorption and ground reflection. As a result, the change in dB depends on the frequency of the sound (see attached example). I have 400+ of these curves to apply, so assuming this is possible using the Nyquist prompt, would it be nightmarish to code?

Thanks again for the help!

Christina