Re: [Audacity-devel] Integrating Nyquist 3.02 into Audacity

[Leland <le...@au...>]

Roger Dannenberg wrote:
> 
> PS Have you thought about SAL syntax for plugins? My thought is they 
> should keep the same .ny extension, but there should be some indicator 
> in the header comments parsed by Audacity that the contents are SAL 
> syntax rather than LISP. I can't remember how the text was sent to XLISP 
> originally, but it should be fairly simple to use the SAL parser instead 
> of the XLISP parser. Alternatively, Audacity could encode the SAL as a 
> string and wrap it in  XLISP syntax that would parse the string as SAL 
> and execute it.
> 
One problem I'm having is getting the return value to Audacity.  For 
instance:

(display (sal-compile "exec snd-pluck(*sound-srate*, step-to-hz(60), 0, 
1, 0.1)" nil nil nil))

Produces:

(PROG (PROG2 (SETF *SAL-LINE* 1) (SND-PLUCK *SOUND-SRATE* (STEP-TO-HZ 
60) 0 1 0.1)))

Running that directly in the Nyquist prompt doesn't return any sound to 
Audacity.  However, running:

(PROG2 (SETF *SAL-LINE* 1) (SND-PLUCK *SOUND-SRATE* (STEP-TO-HZ 60) 0 1 
0.1))

Does return the created sound to Audacity.

I do not know how to get around this...

> SAL has it's own backtrace mechanism, but for debugging it might be nice 
> to allow the choice of an XLISP backtrace (by setting *tracenable* and 
> *backtrace* ) or a SAL backtrace when running SAL plugins.
> 
This'll be easy enough.

Leland