I’ve been using Harrison Mixbus 32c for the last couple of years. For mixing, I really like it - the limitations of the fixed bussing scheme don’t bother me, and the VST implementation (apart from total lack of VST3, 32bit bridging & ARA capability) is very good in terms of signal flow & flexibility of routing inputs & outputs.
For recording and production it’s a bit less brilliant, though. While I have successfully recorded & edited tracks from scratch in it, and there are some very well thought through things like the automatic crossfades and translucent waveforms etc, the virtual instrument and midi editing is pretty rudimentary and slip editing multitracked drums can be a slow process.
So, because I’m thinking about doing some more modern production with electronic percussion, virtual instruments etc, I thought I’d get Studio One.
So far I’ve hardly had time to do anything with it. But… I’m surprised the Console Shaper, which is a plugin that operates on every track & bus, is so coloured. I was expecting something quite subtle but there’s an obvious character even with the gain turned down. I’m not totally sold on it, but further investigation is needed.
I also think Mixbus 32c must do more under the hood than I thought, because I noticed when I was adding plugins in Studio One, even before I’d touched a knob, that I could hear quite clearly the analogue modelling of, say, a Neve preamp or the difference between MJUC’s 3 compressor modes. On Mixbus, I wasn’t really aware of that. I wonder if that’s because Mixbus was already doing some analogue modelling through the channel EQs, so the extra difference of adding a modelling plugin was less. Hmmm.
Anyway. I will add more to this thread as and when Studio One either pleases or frustrates me.