Trash was designed to work at very low
latencies, and so buffer sizes aren't generally an issue when using Trash. Even so, it is useful to
understand a few buffer-related issues in order to get the most out of Trash's
DSP.
In general, as latency is set lower, Trash's CPU usage will rise. The latency that your host application is configured for will related directly with the buffer sizes it sends to Trash. You can find out exactly what these buffer sizes are using the Buffer Size Viewer.
If you notice CPU usage starting to rise for no apparent reason, check to see what size buffers the host application is sending. You might consider increasing latency slightly to see whether this helps reduce Trash's CPU usage. Also if your host application is sending very small buffers (50 samples or less), you might try experimenting with the Alternate box modeling option in the Miscellaneous Options tab.
For more tips about Trash usage, check the Support section of the iZotope web site:
http://www.izotope.com/products/audio/support/trash.html
As we learn more about how Trash interacts with various host applications, we'll update these pages with the latest info.
Note: This help file is a quick reference for basic Trash functions and controls. We have separate "how to" guides that provide tips and techniques for getting the most out of Trash. You can download these guides from http://www.izotope.com/products/audio/trash/guides.html