The concern really game down to exaggerated marketing language, with “the sound of a Harrison console” causing people to expect per-channel harmonic saturation which even Harrison admitted wasn’t there. A huge deal was made of this.
Harrison said when they talk about the sound of a Harrison console, they mean the sum of the parts, which includes EQ frequency ranges and curves, etc…
Harrison already had drive on the bus channels and master channel. So they responded to the criticism by adding a “drive” button next to the trim knob on channels… Which is perfect.
And with that, the controversy died down and the product was made better for it.
But I wish all the hullabaloo had been about stability and bugfixing, which Worrall never mentioned. I spent many hundreds of dollars upgrading Mixbus over the years but I think I successfully made ONE song with it… Because I kept hitting catastrophic or incredibly annoying bugs.
A lot of the bugs were midi. The support guy was very nice, but it always came down to “MIDI really isn’t our focus” — and it’s like… They don’t advertise your support for it?!
But really… Just fix it.
I eventually had to give up on the product because above all else I need reliability… And to bring it back home to Waves, that is why Waves is number one in my plugin collection. I just don’t have the kind of bugs/issues/crashes with Waves that happen with other plugin brands.
