A word about clock speeds:

While some control systems may scan the console frequently, the most important metric is how fast the updates get to the chamber and how quickly the chamber can apply them.  Many control systems scan the console very quickly, but have a fixed (relatively slow) transmission rate to the pipe chambers.  Opus-Two sends a complete image of each and every scan to the chambers immediately, where they are processed and applied immediately.

To further clarify, many competing systems are event based, which means that the send only updates to the chamber.  When a key is pressed, a message is generated and sent to the chamber identifying that the key is now on.  When said key is released, another message is generated identifying that key is now off.  Stops, expressions, traps, tremolos, etc. are all handled the exact same way.  This way could theoretically be considered superior for single-change applications.  In fact, some competitors advertise extremely fast reaction times (1ms or less) per note.  This does not take into account what happens when many notes are played quickly.  The console can’t possibly send the updates one at a time as fast as the organist can play them.  Consider that most swell shoes have a resolution of 127 bits.  If the swell shoe is opened slowly, the single-event data stream to the chambers is very busy carrying successive swell shoe messages.  What separates one competitor from another is not how they work, but how they prioritize which pieces of information to send to the chambers.  This is most obvious when looking at systems that “lose expression changes” or “get behind in fast passages.”

Because of the opus-two systems approach to the scanning and transmission of data, full packets are sent every time.  Full processing is done downstream every time.  And because the system is efficient, there is always idle time in between cycles (usually a lot).  Therefore, it doesn’t matter whether you are pressing no notes or many notes, the system processes the exact same amount of work every cycle.  It is merely copying the contents of the keying buffers to the pipes, following a set of rules defined by the config file (such as pitch, wiring type, etc.).