Optimizing your song manually

To avoid running into DSP overload conditions, there are some manual optimizations you can make to your song. These are as follows;

• Use fewer sounds simultaneously (e.g. reduce polyphony requirements), for example by using multi-instrument mode on tracks.
• If feasible, force a track to use 50% ("50") or 25% ("25") spectral resolution (5/Ki button on a track's Global/"GLob" page) and if needed, tweak your patch so it sounds close enough to the original full spectral resolution. The "Auto" setting will always err on the side of caution.
  
• Reduce decay and release times for the AEGs and FEG for patches, so that your Woovebox is "done" quicker with sounding a voice.
  
• Rely on decay-only AEGs and FEGs for patches rather than having release stages.
  
• Turn off Bluetooth.
• Avoid using delay2 completely across your entire song.
• Avoid using distortion for a patch.
• Avoid using saturation for a patch.
• Turn off filtering for a patch.
  
• Set any unused oscillator's level to 0 for a patch.
• Consider internal re-sampling of complex synthesized sounds and triggering them as samples on a single oscillator.
• Use more sampled sounds in your song, instead of synthesized sounds.
• For chords, consider using track bs through A8 paraphonically instead of using the Cd track, while muting the Cd track and using it only to play/"convey" the chord information/notes (but not the sound). Paraphonic voices only count as a single playing voice, while the Cd track will play up to 4 voices.
  
• Play through the song, or part of the song that is showing DSP overload conditions to help the AI resource allocator better understand your song.
• Please note that the sample kit's algorithm defaults to "Warp", allowing for real-time pitch shifting and time stretching. This algorithm consumes more DSP resources than using the simpler subtractive algorithm. If you don't need the Warp algorithm, consider changing the track's algorithm (3/Ld/Algo on the track's GLob page) to subtractive ('Subt') instead.

Again, please note that rendering a song or its individual stems to a WAV file via Wooveconnect, is not subject to any DSP resource limitations.