- HARRISON MIXBUS 32C VS PRO TOOLS LICENSE
- HARRISON MIXBUS 32C VS PRO TOOLS MAC
- HARRISON MIXBUS 32C VS PRO TOOLS WINDOWS
I guess I posted a long-winded version of what Lawrence said.lol I think of MixBus as a very elaborate plugin, really. But I can't see it ever replacing Reaper in my work. It has become one of the steps in finalizing my mixes. But I have been spoiled by Reaper's generous policies.Īs I said, I love the "sound" from MixBus for the stem mixes I do. Ok, that should not be a big deal, this is common for most software.
HARRISON MIXBUS 32C VS PRO TOOLS LICENSE
V2 license does not include free V3 upgrade.
HARRISON MIXBUS 32C VS PRO TOOLS MAC
Does the Mac version have this limitation?
HARRISON MIXBUS 32C VS PRO TOOLS WINDOWS
This is something that I am told will be addressed with the Windows version of V3. Like many of my reverbs, compressors, even a few choice EQ's. And I have been terribly bummed to find out how many of my plugins are coded this way. But if you have, for instance, a compressor that is "hard-coded" to have more than 2 inputs, then MixBus can not use it at all. I have been back and forth with their support with this, and I still don't fully understand this. Windows version only supports 2 inputs on plugins, even 32bit. This may seem trivial, but anyone who knows my work knows that I need my Nebula. The Windows version of MixBus won't support Nebula. I worked hard building a huge 64bit plugin collection, and I don't really want to re-gather all of the 32bit versions now. MixBus has a few gigantic short-comings that I can't overlook That final mix goes back into Reaper for a the actual final pre-master. It will never replace Reaper for me, but I have developed a work-flow of rendering buss stems from Reaper, inporting those into MixBus, and doing a mix down with that. I'd still track and edit in Reaper though. The sound of Harrison's mixer does greatly outweigh the shortcomings though. Any ASIO or Coreaudio device shouldn't have problems. (Harrison is working on their own controller and Reaper has Eucon coming!)ģ) Interfacing between Jack and any AVID sound device is an absolute shit-show. Better controller support would help them both. No idea on Mixbus's Windows performance.Ģ) Automation is a bit clunky. Also, I'll lose some plugins that I'm pretty attached to. I've heard the DSP runs better on Linux OS's, but to run linux would mean I have to ditch my AVID HD Native card for an RME w/ Madi, and buy a Madi card for the Burl converters we have. Still a pretty decent machine! I can mix massive sessions in Reaper, Nuendo, Logic, and Pro Tools without hiccups, but even on a 44.1 session with 40 tracks will start spiking the DSP core using only the Mixbus mixer. I use it on an 8-core Mac Pro with 16gb RAM. So rather than elaborate on that, I'll talk about its shortcomings (which most SHOULD be addressed is v3).ġ) DSP processing is limited to 1 CPU core. I could go on for days about the sound of Harrison's DSP, and would rate it an 11 out of 10. You'd be surprised how much you can do with just 3 bands of eq. The sound I get in my mixes is incredible! The console workflow is pretty much perfect.
0 kommentar(er)
