Muse Research Receptor v1.7 Release Notes - Manual (Page 30)

Receptor v1.4 Release Notes 30 Muse Research, Inc.
This functionality still exists, but is now one of two options for specifying how Receptor routes incoming MIDI
CC data. The new option is called “Route MIDI CC’s to Source Plugin” and is located in the MIDI section of
Receptor’s Setup View.
This is the new
“Route MIDI CCs to Soure Plugins”
option.
On the front panel, you can get to this option by pressing the SETUP button and scrolling to the parameter
called “MIDI CCs to Source”.
When you check (or turn on) the Route MIDI CC’s to Source Plugin option, Receptor passes all MIDI CC
information through to the source plugin. Receptor does not use the MIDI CC’s to control its internal mixer,
nor does it determine which MIDI CC’s are routed to which plugin parameters -- rather, it lets the plugin itself
decide what to do with all the MIDI CC data. This is particularly beneficial if you’re using larger, more complex
plugins (such as Native Instrument’s Kontakt 2) and you’re more concerned with controlling the plugin via
MIDI CC than you are controlling Receptor’s mixer.
NOTE: This setting is not global -- rather, it’s saved and recalled with a MULTI patch. This lets you determine
where to route MIDI CC data on a patch-by-patch basis.
New Feature: Dual Function CPU Gauge
Receptor v1.4 features a new, dual-function CPU meter. Specifically, on the graphical interface, the CPU meter
now measures both the instantaneous peak CPU usage and an average CPU usage.
Peak Meter
Average Meter
Receptor constantly monitors the amount of CPU required to process each audio buffer (as set by the Sample
Buffer Size parameter in Setup view). Given the fact that each audio buffer is processed in mere miliseconds,
it would be impossible to display every buffer graphically. And, even if the human eye were fast enough to
see all these CPU values, the amount of CPU required to process each buffer will vary greatly, meaning the
meter would ‘jump around’ so much as to be useless. So, Muse Research provides a couple of different ways to
monitor the CPU usage, which allow you to extract useful information that will help you optimize CPU usage
on your Receptor:
• Peak Meter: The Peak Meter is constantly looking for the highest percentage of CPU used over the course
of the past few audio buffers. For example, if the CPU was 90% for one buffer, and 10% for the next
several buffers, the Peak Meter would show 90% since this was the highest CPU encountered. Often times,
plugins may require a rush of calculations within a single audio buffer than could cause short bursts of CPU
activity. As long as these CPU bursts happen within a single audio buffer, it’s very unlikely that they’ll
cause any sonic abnormalities. However, it’s a good idea to keep an eye on the peak CPU meter. If it’s
hovering around 100% or peaking frequently, you may want to consider bouncing some of your Receptor
tracks or modifying your sequence. In general, CPU peaks are nothing to be alarmed about unless they
cause sonic abnormalities.