The error message:
error: bad place form
Function: #<FSubr-SETF: #7edd7b0>
Arguments:
LOFREQ
20
(COMMA 0)
1> error: bad place form
Function: #<FSubr-SETF: #7edd7b0>
Arguments:
HIFREQ
20000
(COMMA 0)
Function: #<FSubr-SETF: #7edd7b0>
is due to a recurring limitation in Audacity where commas (,) are not recognised as decimal separators, even when the system language is a European language that should accept the comma as a decimal separator. This has been fixed numerous times and has broken again an equal number of times. It is currently broken http://bugzilla.audacityteam.org/show_bug.cgi?id=173
The simple workaround is to use a dot (.) rather than a comma (,) as the decimal separator.
Plug-ins that require user input are not supported by the Nyquist Prompt effect.Corvinian wrote:when I copy the text content of the noisegate.ny effect to the 'Nymquist commandline'
and click 'Diagnose', the following is returned:
The reason for this is that the Nyquist Prompt effect processes the Nyquist code only and not any of the code that is intended for Audacity. The user controls are written into the plug-in as Nyquist comments, so that they are ignored by the Nyquist Interpreter. Audacity "sees" these special comments and produces the appropriate input controls.
An example of a "control" in a Nyquist plug-in could be something like:
Code: Select all
;control thresh "Threshold" real "dB" -20 -100 0but Audacity will read that line and produce a "slider widget"
The text in quotes is displayed as the slider control text, so in this case it will produce a slider like this:
Threshold [ -20 ] -------[]----------- dB
and the value entered is given to a variable called "thresh"
If the code is run in the Nyquist Prompt, this code is ignored, so the variable "thresh" has no value assigned, so producing the error:
Code: Select all
error: unbound variable - THRESHThe code to do this is quite simple:
Code: Select all
(setq thresh -20.0)This would need to be done for each of the ;control lines