I'm quite sure it is different... I'll leave the snake oil debate for other threads<G>, but I will agree that Dave Harrison, who founded the company after leaving MCI, would probably blush at some of the ad copy.
I did, finally, buy it at $39 last time around - mostly because one of my early mentors swears by Harrison consoles, and because I got to meet Mr. Harrison at a couple of AES shows years ago, and he was a very cool guy. I also really like both MCI and Harrison consoles, although in full disclosure, if I won the lottery I'd probably buy an API.
I like the workflow, I don't like the Windoze implementation a lot, but I got it to work, which is worth something I guess<G>.
I sounds nothing like the Harrison EQ plug-in that UA developed, but I don't think that's a fair comparison - the EQ is just an EQ, this thing is the entire console.
It does sound different than either Sonar or Studio One, the only two tools I can compare it to - and as mentioned in another thread, my current listening environment does not inspire confidence - I expect I'd hear a bigger different in a well controlled listening space, but I'm not sure I'd have a favorite...
bitflipper
Now, if you're mixing on a computer, wouldn't you prefer your software vendor to have "experience in computer sound"?
A RESOUNDING NO!!!
One of the biggest problems with the audio for computer space is that very few people developing hardware and software for audio applications have any real experience in professional audio. I will not mention names, but I have seen cases where hardware and software engineers had no clue:
- while certainly due to market pressure, there are no A/D or D/A chips that run off anything higher than +5V, and these are being replaced by chips running off +3V, and even +1V. While the mathematical arguments about scaling are lovely, they do not hold up in the real world.
- there are so many poorly designed input and output stages that the AES had to create a standard to explain how it should be done. For the record, these are things that Bell Labs, the BBC, RCA, Neve, and a host of other companies figured out and understood 50 years ago.
- I worked on a project recently where I spent a good part of my time explaining how dB related to rms and peak voltages and how analog signal levels corresponded to bits. I think anyone working in audio ought to understand the decibel.
- More than a couple audio software developers have made such a mess of metering that their implementations are completely useless.
- I worked on an early A/D and D/A converter, I focused on headroom, signal levels, and other "trivial" features... I was fortunate enough to work with a really talented digital engineer, and the product turned out really well.
So to answer your question, I want a software developer that understands AUDIO first, and computers second. (on the plus side, I've made a nice living teaching folks about audio<G>) I do not know who is left at Harrson - but so far I am willing to bet that some of the analog audio guys are still there.
Mixbus may not fit into everyone's workflow, but at $39 I think it is worth a try...