Summary of FAUST Program Testing Strategies

The development of a FAUST program p.dsp, say, typically consists of the following steps:

 > faust p.dsp          # does it compile?
 > faust2firefox p.dsp  # check the block diagram
 > faust2octave p.dsp   # (maybe) inspect the output signal(s) in Octave
 > faust2jaqt p.dsp     # make a JACK-compatible application

These operations are so common that I have shell aliases f, f2ff, f2o, and f2j for these commands. More recently,the first two may be replaced by the Faust Editor. The third (f2o) is typically only used for serious testing, such as for a publication.