The SynthLab-DM synths may use an optional config.txt file that is located in the SynthLabModules folder.
In the initialization phase, the config.txt file will be opened and parsed prior to the SynthEngine instantiation. This gives you some flexibility in how you use the DM products for testing your modules. And, if you have written a toxic module that crashes the synth on loading, you may turn off the DM option and restart the synth – it will revert to its non-DM mode and load its own modules. Note that if the config.txt file is missing, the synths will boot into non-DM mode, loading their modules statically. You may edit this simple file with any text editor and the handful of fields are easy to understand. Here is what the default config.txt file looks like:
You set the boolean variables for your particular needs. Make sure to use the lower case as this is the only valid indicator! The table below lists the configuration variables and their meanings:
| config varaible | What it does |
|---|---|
| kDMBuild | enables or disables the DM mode in the synth; disable to boot into safe-mode with no DM loading |
| kDualMonoFilters | the oscillator -> filter signal path is stereo, but only the SynthLab-PCM oscillators are true stereo all other oscillators are actually dual-mono; this variable forces the filters into dual mono-mode as well, cutting the number of required filters in half |
| kHalfSampleSet | when true, instructs the PCM oscillators to load only half of the samples enable this if you have memory issues when loading the PCM synth |
| kAnalogFGNFilters | see the synth book for details on analog finite gain at Nyquist options for my VA filters note that both traditional BZT and these analog FGN outputs are always calculated, so this does not save CPU cycles; it allows you to hear the different modes of operation and experiment |
| kParamSmoothing | the ASPiK framework that was used to design and generate the DM synths features automatic parameter smoothing; you may disable that by settting this config variable to false; it should not affect CPU usage very much for Release builds, but will significantly reduce CPU overhead in Debug builds |
You will need to restart the synth after editing this file for the changes to take affect.
