Skip to main content

Buffer Size Multiplier

Overview​

The Buffer Size Multiplier is a newly added option in the User Preferences of the SideRack plugin. This option plays a crucial role in adjusting the plugin's internal buffer size, balancing latency and processing power.

Detailed Description​

The Buffer Size Multiplier represents how many times larger the internal buffer size should be relative to the host’s block size. For example, if the host’s block size is 512 and the buffer multiplier is set to 2, the internal buffer size will be 1024.

This setting is essential for managing the plugin's latency and the maximum number of rack instances.

  • Range of Possible Settings: 1-100
  • Recommended Range: 1-10
  • Default Value: 4

Balancing Latency and Stability​

Lowering the Buffer Size Multiplier can reduce latency. However, if set too low, it may exceed the device’s processing capability, potentially causing noise or instability.

Configuration Guide​

  1. In most cases, using the default value (4) provides a balanced outcome between stability and performance.
  2. This setting should work smoothly on most systems.
  3. This setting is suitable for tasks that don’t require strict real-time processing, such as composing and mixing.

To Minimize Latency​

For real-time applications like live performances or instrument playing where lower latency is essential, try the following:

  1. Edit the Buffer Size Multiplier in the User Preferences of the SideRack plugin.
  2. Set the Buffer Size Multiplier to 1.
  3. Adjust the block size in your DAW. Try setting it to the lowest possible value while monitoring for any noise.
  4. After making changes, always restart your DAW.

Note: These settings may place a significant load on your system's processing capacity. If you encounter noise or audio dropouts, gradually increase the Buffer Size Multiplier or the block size in your DAW until you find a stable setting.

Since optimal settings may vary by system, it’s recommended to fine-tune these adjustments as you use the plugin. However, unless a specific reason exists, the default value generally provides stable performance. If real-time processing is not a priority, maintaining the default value is likely to ensure more reliable operation.

Last updated on