I like the new widgets. Duration is now a time button.
The read/write commands have me wondering: is it already possible for a LADSPA or LV2 plugin, or possibly a malicious version of the FFMpeg library to execute arbitrary code, or is there some kind of limitation on what they can do if Audacity calls them? Are there any restrictions on what files a Nyquist plugin could read from or write to?
Right, I just noticed the Run Benchmark… tool and it told me my computer could play a couple dozen 44.1kHz tracks at once, in real time. I suppose a big round number like 2048 spooked me a bit, but it makes sense that most computers that can play sound should be able to crush this.
I’m struggling a bit trying to figure out how to time how fast Nyquist runs something, since I can’t get any information on the system time when code executes. I’m guessing the general idea is to write a loop in Nyquist to run the same code some large, fixed number of times, time that with a stopwatch or something, and use that to calculate the average time. I’m unsure how to account for the extra time it takes to interpret and execute the loop itself.
Totally right, my bad! I’ve changed validate-coefs to your suggestion, but this has me wondering whether it was a good idea to require the top level items to be lists. I guess I wanted the syntax to differentiate between top level items and deeper ones, since they mean different things, but I’m wondering if it makes sense to just silently convert that 4 to a (4) and keep going.
ADDITIVE3.ny (5.19 KB)