Signal processing units (SPUs) empower the STx programmer by providing the possibility to create their own signal processing algorithms. Using a set of predefined atoms, the programmer can develop such things as a…
- synthesis circuits (e.g. additive synthesis using the ADDSYN atom)
- real-time spectrum analyzers (using SPECTRUM and WAVEIN2 atoms)
- complete speech analysis (e.g. by using the atoms F0SIFT, RMS
The SPU subsystem consists of the built-in Signal Processing Atoms (SPAtom), the SPU ciruit definition languange and the SPU shell items, implementing the run-time instances of the signal processing circuits. SPUs are defined using the circuit definition language. Once defined, they can be instantiated in an SPU item, or used as an element in another SPU.
Advantages of SPUs versus imperative programming
- fast signal processing: SPAtoms are C++ classes using special math libraries for acceleration
- parallel processing: each SPU instance may run in its own thread
- fast data exchange: data exchange using direct access (between SPAtoms) and messages (between SPAtoms and other shell items - e.g. graphs)
- complex circuits: SPU instances can be interconnected to build complex processing circuits
- real time signal processing is possible
Alternative: Imperative programming using the
An alternative for implementing signal processing algorithms is the EVAL command. The EVAL command makes the algorithms more readable and also more flexible, because the whole scripting language can be used for the implementation. On the downside, the execution is slower and needs more memory. In many cases a combination of SPUs (with or without their own threads) and EVAL will be the optimum choice.
The SPU source code defines a type of circuit. An SPU shell item is an executable instance of a circuit and is created from the source code using the NEW SPU command. On creation, the following steps are taken:
- An instance is created for all local elements. If an element is itself an SPU, it is replaced with the internal circuitry of this SPU and then its local elements are instantiated. This process is continued until all SPUs have been replaced with their most basic elements (SPUs). The interconnection, as defined in the function statements, is carried out at the same time as the instantiation.
- The second step initializes all the SPAtoms. All constant arguments are evaluated and used as initialization parameters for the SPAtoms. Additionally, all connections are tested (i.e. are all the necessary inputs available? Are all the data types compatible and valid?)
On completion of this compilation procedure, the SPU item is ready for use. A new process is started which is responsible for the control and execution of the item. On creation of an item, all initializations (parameters) and connections (inputs) are carried out. The data types and the sizes of the outputs are fixed. The outputs are, however, not yet connected!
The SPU outputs can be connected to the inputs of another SPU, to the inputs of a graph or to a value item. The output connection occurs after creation by the relevant macro commands. This has to happen before the beginning of the processing. An active (running) SPU item's connections cannot be changed (created or destroyed).
Because SPUs run in separate threads, a message handler has to be installed before the SPU is started. The most important message sent by an SPU is the
STOP message. This message indicates that the processing (and therefore the data exchange with other items) has finished.
Signal Processing Atoms
All built-in SPAtoms in alphabetical order:
ABS ACNV ADANA1 ADASEG ADD ADDSYN ADPAR1 ADRECORD ADSET1 ADSET2 AGCR ASEG1 ASIGIN AVR AWEIGHT CCANA CCONV CEPSTRUM CSIGIN DCTRANS DELAY DENOISE DIV DOT EXSTAT F0AC F0HGRID F0SIFT FFANA FFSYN FFTPAR FORMANTS GET IN2TABLE IRRECKEL KLATTSYN KLSYNRT KLSYNWAVE LENGTH LIMITER LOG LPCOEFS LPSPECTRUM MASKABC MCLUST MIX MIXALL MOD MORLET MUL MULACRTA MULACRTALOG MULACRTS MUXIN MUXOUT NOISE NPOST NSEND PEAKS POW PPM PVANA PVSYN PZTF RANGE RESAMPLE RMS RMSB ROUND RSIGIN SELECTAB SHEPARD SIGOUT SPBCOEFS SPECTRUM SSIGIN STAT STEPS SUB SUM TABLE2OUT TLOOKUP TONE TRUNC UCONV VMERGE VSPLIT WAVEIN2 WAVEOUT2 WIGNER WINDOW WLANA ZEROCROSS
Notes on the description of the SPAtom inputs
- The data type defines the type of data to be connected to an input. The possible data types are number, vector, matrix and string.
- The value type defines if an input is variable or constant. If an input is marked as variable, its value can be changed in every evaluation cycle. If it is marked as constant, its value is only used for the initialisation.
- The data type and the dimensions of an input (also if marked as variable) are checked during the initialisation and can not be changed.
- The default value (if specified) is used if an input is not connected.
Notes on the description of the SPAtom outputs
- The data type defines the type of data stored in an output. The possible data types are number, vector, matrix and string.
- The value type defines if an output is variable or constant. If an output is marked as variable, its value is changed in every evaluation cycle. If it is marked as constant, its value is set during the initialisation.
- The data type and the dimensions of an output (also if marked as variable) are set during the initialisation and never changed.