Console Based Pipe Processing
Today we are proud to announce a paradigm shift in how Opus-Two processes and distributes data from consoles to chambers. Since the launch of the product, through various implementations, the core method of data transmission has always remained the same: distributed processing. While other manufacturers have long moved on from this technique, we continued with it because it provided the fastest results. We have long been committed to follow the most data-processing efficient path from key press to pipe playing, it is what sets Opus-Two apart from others. The console has traditionally scanned itself, created a digital representation of all keys, expressions, and stops, and sent that data to the chamber processors, which would apply their individual configurations. While they are doing that, the console is free to begin the process over again.
We have now completed the first installation that uses a different approach. The console contains its usual configuration as well as all of the chamber configuration. All cards, stops, ranks, and expressions are completely processed in the console, formatted for the card strings, and those final formats are sent to the chamber. This has several (huge) advantages:
All configuration of an entire instrument is done in the console and instantly applies to the entire instrument.
There is no need to physically access each chamber processor to update it.
Almost no processing time is required in the pipe chambers. Once they get the data, they can immediately send it to their connected cards.
Chamber controllers no longer require a lot of hardware components, and chamber work is mostly a software task. This will enable a new family of inexpensive chamber controllers.
PipeBus links can run significantly faster because there is no need for chamber traffic management between link bytes.
Watch this page for general availability of this new approach. We expect to have this rolling out as our standard in 18 months, depending on ARM development progress.