Are you experiencing high CPU consumption while using HeadRush Revalver 5? Don't worry, we've got you covered!
TABLE OF CONTENTS
Why am I experiencing high CPU consumption?
Like any audio processing plugin, it can take a toll on your computer's CPU to deliver exceptional results - Fear not though, there are some easy methods to manage CPU consumption on either standalone builds of Revalver 5 or use as a VST/AU/AAX plugin in your favourite DAW.
First of all, it's important to ensure your computer meets the minimum system requirements for Revalver 5 - You can find this information below:
Windows
Runtime environment: Windows 10 21H2 or later. VST 2.4/VST3/AAX host, or sound card (preferably ASIO)
CPU: 64-bit with SSE2
RAM: 2GB
Disk Storage: 700MB
Windows Tablets are supported if they fulfil the requirements above. Tablets with ARM processors are not supported. A keyboard may be useful for some tasks.
macOS
Runtime environment: macOS 13.0 or later (64bit CPU, Intel or ARM). VST 2.4/VST3/AU/AAX host, or sound card
CPU: 64-bit with SSE2
RAM: 2GB
Disk Storage: 700MB
Audio Buffer Size
A low audio buffer size is crucial to reduce any latency during your performance however, it will increase the amount of CPU consumption on your computer.
In most cases, users can find a healthy balance of lower CPU consumption and minimal latency to achieve optimal results.
Note The settings configured for your audio buffer size will vary depending on your computers setup, soundcard choice and rig contents.
The following steps on Audio Buffersize adjustments apply to the standalone build of Revalver 5. If using a DAW, revert to the audio settings in your DAW's settings/preferences.
To adjust the Audio Buffer Size settings in Revalver 5...
- Navigate to the 'Settings' Icon seen on the top-right of your Revalver Graphical User Interface (GUI)
- Click the Audio/MIDI button
- Ensure your sound card is correctly configured for both the 'Output' & 'Input'
- Click the drop-down menu under 'Buffer Size' - Increase the samples gradually to make sure you're happy with the response of latency or CPU consumption.
- Click 'Close' once you've configured a Buffer Size.
- Click 'Close' on the settings window once complete
Rig contents
If your rig has a high number of modules including Pedals, time-based FX or a dual rig setup, it will naturally require Revalver to consume more CPU to process the signal / deliver the results you're expecting.
If you are experiencing high CPU consumption as a result, consider switching to a single rig setup and limiting the number of time-based FX in your signal chain.
DAW Projects
If your DAW project has a high number of Revalver 5 instances, you may notice the CPU consumption is a little higher than expected. Similar to the world of synth plugins/fx, once you've captured your recordings and dialled in the perfect tone, you may wish to consider 'printing', 'freezing' or 'bouncing in place' your tracks containing the Revalver 5 plugin.
The steps to perform either of the tasks mentioned above differ for each DAW - For some popular DAW's, please see the links below to help you perform these steps:
Logic Pro - Bounce track in place
Cubase - Render track in place
Questions? Concerns? Any other issues? Please don't hesitate to contact our friendly support team by submitting a new ticket and further assistance.