View Single Post
Old 12-13-2018, 07:11 AM   #4
Human being with feelings
mschnell's Avatar
Join Date: Jun 2013
Location: Krefeld, Germany
Posts: 7,471

Tweaking the system for performance

  • If you intend to use many Sample instruments as VSTis, you might need to provide a decent amount of RAM
  • If you intend to use combinations of high level effects as VSTs, you might need to have a reasonably fast multi core CPU.
  • Audio/MIDI plugins: if you face some issues, contact the author for a bug fix. No fix => quarantine !
  • Mechanical and chemical elements are due to degradation, so using fans, hard disks or accumulators should be avoided if possible by using a fanless design and SSDs. At least a lot of care should be taken choosing excellent quality devices.
  • SSDs can feature degradation by wear-out if they are rather full and written to. So they should get filled to not much more than half, and unnecessary writing should be avoided as much as possible.
  • When reading, SSDs are faster than hard disks, so they are recommended for faster booting and loading large sample libraries.
  • Overheating will cause failure, hence an appropriate design of the system is necessary.
  • Regarding transport, the mechanical design (especially plugs) should be as rigid and easy to use as possible.
  • There are companies that provide Windows "Audio" PCs and Laptops especially for use with DAWs. Of course those are not cheap. Maybe using a "Gaming" PC or Laptop is a good idea, as well.

Reaper settings:
  • REAPER > Options > Preferences > Audio > Device > Audio Thread Priority to MMCSS Time critical might help to prevent certain CPU performance problems with ASIO drivers.
  • REAPER > Options > Preferences > Audio > Close audio device *...+: all disabled → We want to use the audio engine whatever happens
  • REAPER > Options > Preferences > Audio > Buffering > Allow live FX multi processing: enabled + set the proper number of CPUs
  • REAPER > Options > Preferences > Audio > Playback > Run FX when stopped: enabled
  • REAPER > Options > Preferences > Audio > Do not process muted tracks: enabled → CPU savings when the Live Configs’ option “mute all but active track” is enabled
  • REAPER > General > Maximum undo memory use: 0 (i.e. undo disabled) → When you use a “headless” system without PC-keyboard, mouse and monitor, you will want to shut it down just by hitting the power on/off pushbotton, making the OS close gracefully. If the above setting is 0, Reaper will not ask you to save your changes and hence not wait for user input.
  • REAPER > Main menu > Extensions > SWS Options: disable everything there
  • With Live playing setups, you will want to stretch the area for the track Controls to the right and squeeze the height of the tracks to see a greater number of threads on the screen.
  • Another discussion on multi-Core performance see ->
... much more to do ...

Some of these options are not really compatible with song editing. You can start REAPER with dedicated live settings (i.e. a “live edition” of the REAPER.ini file) thanks to a command line like: "reaper -cfgfile ReaperLive.ini myLiveConfigs.rpp"

Plugin settings
  • Certain plugins introduce some latency ("Plugin Delay Compensation" = "PDC" see -> ). Reaper displays this latency on the frame of the window it provides for the plugin. With certain plugins (e.g. ReaVerb) this latency can be configured (see above). Reaper automatically introduces additional latency to "faster" tracks do provide perfect alignment between the tracks.
    Unfortunately Reaper does not seem to display the resulting total project latency anywhere.

PC tweaking - more to be done -

MacOS settings
- no idea at all -

Corrections and suggestions for enhancement are very welcome ! Please answer in a new thread, as I might need to add more pages to this thread.

Questions in the forum are very welcome, as well.


Last edited by mschnell; 07-19-2019 at 10:49 PM.
mschnell is offline   Reply With Quote