If your macros do NOT contain any Nyquist effects (they are listed “below the line” in the Effect menu), then you could create a Nyquist script to call each macro in turn and then use “Export2:” to export each version with a different name.
Actually I have been using a Nyquist effect macro, also a VST which is “below the line”.
Here’s my current chain…
CHANGE SPEED BY SEMITONES (nyquist)
GULLFOSS (VST)
EXPORT AS WAV
reckon there is a way to implement another Nyquist script here? your answer seemed to imply that there is a clash between Nyquist scripts, or there can only be one in a macro at a time.
oh, thought i replied but it slipped thru… apologies
Thanks for that steve.
So i have been using Nyquist scripts as one of my macros actually. as well as a VST which is also “below the line”… Here is what I have in that example.
CHANGE SPEED BY SEMITONES (Nyquist)
GULLFOSS (VST)
EXPORT AS WAV
Your post seems to imply there can only be one Nyquist macro involved in a chain…?
Will have a fiddle anyway. Haven’t used export2 yet.
I’d be interested in the order of such things too, if I say script together two chains then will it not apply the two chains on top of each other, and not as separate processes on the source files? This is my current understanding of macros.
Posts from new forum accounts go into a “moderation queue”, so they don’t appear immediately. Unfortunately this has become necessary to combat spam. This restriction goes away in due course. Sorry about the inconvenience.
The limitation is that a Nyquist script cannot call a Nyquist script - only one Nyquist script can run at a time, so when running a “Nyquist Macro” it is not possible to include “Nyquist effects”.
yes, maybe it’s good to look at that again. i did do some tests and for whatever reason changing speed by a percentage was not as accurate in changing semitones as much as the Nyquist SPEED BY SEMITONE
(Missing features - Audacity Support)
one of yours by the look of it… props!
Have been having a look at Export2, and am a bit lost. I can’t seem to find a reference to it on the reference pages for Nyquist programming.
Seems there’s only a way to export the track to a fixed location with a fixed name using export2 in the macros setup area, and not dynamically assign it using the original file name…
“Export2” is a macro scripting command, so it’s on this page: Scripting Reference - Audacity Manual
(most web browsers use “Ctrl + F” to search for text on a page)
Note that “Filename” must be the full path+filename
Example:
C:/User/fred/Documents/test1.wav