;nyquist plug-in;version 4;type generate;categories "http://lv2plug.in/ns/lv2core#GeneratorPlugin";name "Click Track...";action "Generating Click Track...";info "For help, select one of two help screens in 'Action choice' below.";author "Dominic Mazzoni";copyright "Released under terms of the GNU General Public License version 2"

From this, you can create your own template - a text file on the desktop for instance - and copy it into each new plug-in.

A few remarks:The first two lines should never change.Version 4 plug-ins have the most features, thus, I would stick to it.The type might change, there are also process and analyze available.;categories is not really necessary - it's a bit confusing to find the right type online.;name and ;action have to be adapted for each new plug-in.Action is what will be displayed on the progress bar when executing an effect.

;info seems to be no longer in use, I cannot see any text displayed in the Dialog.

;author and ;copyright appear under the manage menu (alt+m) of the effect dialog, under "about" to be more specific.Confusingly enough, they are renamed:;author --> Vendor;copyright --> Description

Each line of the header begins with a single semicolon followed by a keyword and then one or more parameters. The following four headers are required (essential) for all plug-ins. The keyword must always be typed in lower case. The parameters must also be lower case unless the parameter is quoted text (such as the name of the effect).

;nyquist plug-inThis tells Audacity that it is a Nyquist plug-n

;version 4Plug-ins may be version 1 to 4. Version 4 is the most recent and as Robert says, has the most features. New plug-ins should use the most recent version number.

;type processor;type generateor;type analyzeThe type tells Audacity which menu to put the plug-in into. Process type plug-ins go in the Effect menu, Generate type plug-ins go into the Generate menu and analyze type plug-ins go into the Analyze menu. As a general rule, plug-ins that process audio and return audio to the track should be ;type process, plug-ins that generate audio should be ;type generate, and plug-ins that analyze audio or create labels should be ;type generate.

;name "Quoted name of track"This is the name that appears in the Audacity menu. Try to use a short but descriptive name. If the plug-in has an interface the name should end with three dots. If the plug-in acts immediately without showing an interface the name should not have the three dots. The name must be in quotes and is usually in Titles Case.

Those are the 4 essential headers.

The ;categories and ;info headers are not currently used by Audacity (ignored).

The headers look OK except that there are 4 spaces at the start of each line. The header lines should really start at the beginning of the line.Also, there would usually be an empty line separating the header lines from main plug-in code.

However, it will not work as a plug-in because the code is incomplete. If you try to run it using the Debug button you will get an error beginning with:

Normally when writing LISP code (and Nyquist is a type of LISP code), some lines are indented by spaces so that the code is more readable (for sighted users). I realise that can be difficult, and of no benefit, if you can't see the code, so don't worry about indenting the code. If necessary I can add appropriate indentation for any plug-ins that we wish to upload to the Audacity wiki.

The code is still incomplete, so it still does not run. Specifically, in the first line of Nyquist code you have:

(setf low (if (member key

but "key" has not been defined. I'm guessing that "key" would be an input variable, but currently there are no input controls.

By the way, I notice that there are error in the code that Robert posted earlier in this post: viewtopic.php?p=205709#p205709To specify a character, the correct syntax is a hash symbol followed by a backslash followed by the character. For example, for the character "A" :#\A