FAQ: PITCHMAP

CPU Load Optimisation

PITCHMAP does some very complex mathematics, and thus uses a considerable amount of CPU processing time. Here are a couple of suggestions how you can avoid CPU overloads:

  • Try increasing buffer sizes in your host software to their largest values, then gradually bring them back down until you find a suitable balance between latency and CPU load. In Logic Pro, this also includes the "Process Buffer range" parameter.
  • Try closing the GUI of any plug-in that you don't currently need to have visual feedback on.
  • Quit any open applications that are not needed.
  • In Logic Pro, all processes that are fed by a live source are processed on one CPU core. When using PITCHMAP under MIDI control, this means that all down-stream plug-ins are run on the same core as PITCHMAP whenever its software instrument track is selected and the record enable switch is lit. Selecting a different track in the arrange, or un-setting the record enable button allows CPU load to be spread out across all available cores, so this may help reduce CPU load.
  • Setting Electrify very low causes a higher CPU load due to more sounds being recognized, which causes the Display to render more symbols. Keep the value of Electrify around 50% if you don’t explicitly use it for fine-tuning your sound.
« Go back

Current Versions

PACE Versions:

PITCHMAP AU/VST/VST3/RTAS/AAX: 1.6.3p

UNVEIL AU/VST/VST3/RTAS/AAX: 1.7.9p

UNFILTER AU/VST/VST3/RTAS/AAX: 1.2.3p

UNCHIRP AU/VST/VST3/RTAS/AAX: 1.0.2p

MORPH AU/VST/VST3/RTAS/AAX: 2.3.1

UNMIX::DRUMS AU/VST/VST3/RTAS/AAX: 1.0.3

ADAPTIVERB AU/VST/RTAS/AAX: 1.1.2

WORMHOLE AU/VST/RTAS/AAX: 1.0.2

NON-PACE:

PITCHMAP AU/VST/RTAS/AAX: 1.6.1

UNVEIL AU/VST/RTAS/AAX: 1.7.6

UNFILTER AU/VST/RTAS/AAX: 1.2.1

UNCHIRP AU/VST/RTAS/AAX: 1.0.0

ORANGE VOCODER AU: 3.4.2

TIME FACTORY II MAC: 2.5.3