I searched for the following specific objective and could not yet locate a good post – could be I am not wording right.
Here is what I want to do.
On my Korg PA600 Keyboard Sequencer, I can have existing tracks (or selected time interval) to keep looping, while I record on a new track. The audio will play all the tracks. The new track keeps recording (cumulatively) to whatever I am playing.
If I do not like what is recorded, I can hit a key and the new track gets cleared and starts recording again.
Is already possible to do this Audacity using the current UI?
Wonder if there is there are plugins.
Appreciate insightful thoughts or guidance from experienced folks for getting this kind of functionality implemented using Nyquist.
BTW, I am just starting to look into Nyquist. I am quite comfortable learning yet another language and plunge as needed. LISP/SAL are no issues.
There are VST looper pedal plugins, (but they won’t work in Audacity).
The physical version costs ~$200 … https://youtu.be/Gd0NhglZWtw?t=576
It sounds like you want a “live looping sampler”. The only one I’ve used is Sooperlooper, but I think that’s only available for Linux and Mac.
Try a Google search for “live looping sampler”.
Thanks for your response and for the terminology.
I had been creating code in Python for all my audio workflow and automation needs.
Mostly headless - and then started looking into Audacity Plugins.
BTW I have been using Audacity for 20+ years but never ventured into extensive use of Plug ins (except for simple effects) and Plugin development.
As I mentioned, I already have the looped play/record capability on my Korg PA 600 - but that environment is limited for all other allied needs. Not to speak of the screen size that is just too small for eyes.
I could create the needed capability in Python rather easily - adding GUI and addressing some performance issues.
Then I would be sort of reinventing some basic things Audacity already does with great Mastery.
I do not understand yet the Nyquist programming model of Audacity yet.
Can .ny code be event driven call backs or have to be invoked only through menus?
I already played with some real basic examples with Nyquist prompt - and see that it may not support interactive edit/run/debug loops.
It is tempting to install CMUs nyquist IDE - but want to remain Audacity-centric.
Appreciate if you can point me to some posts which shows how to do interactive development/test of nyquist files in Audacity itself.
(Without having to save, load, install steps).
Nyquist integration in Audacity is basic. You call the Nyquist script (usually through a menu item, though may also be called via a “Scripting command” in a Macro or via Python). Audacity passes data to Nyquist. Nyquist runs the script and returns a value. There is no user interaction possible after the Nyquist script has been called.
The easiest way to experiment with Nyquist is to run commands in the Nyquist Prompt effect: Nyquist Prompt - Audacity Manual