![]() ![]() They're doing something different from any other DAW - it's nice to have that option.įor me, Mixbus is my solution when I'm overwhelmed by the complexity of a mix in Reaper. While it's not my primary DAW, I love that Mixbus 32c exists as an alternative workflow. ![]() To match with their "analog sound" marketing they should have it on by default but users that don't want it could turn it off. And it could vary it with each channel, similar to Waves NLS or Brainworx's TMT. Truth is, Mixbus 32c could solve their marketing 'outrage' easily by adding a preamp stage of modeled harmonic distortion and samples noise from a real Harrison console. I do like the compressor and tape saturation, even if it's simple. I know this thread isn't about the workflow, it's about the sound.īut with that in mind, the "sound" comes from the combination of tools in Mixbus 32c. I'm primarily a Reaper guy, but I do like the mixer-like feel of working in Mixbus 32c sometimes. Harrison's marketing team blundered because what may have sold their DAW for a long time finally turned into a whole lot of negativity on forums everywhere. I did the null tests myself this weekend and my results were the same as everyone else's. *All comparisons were made using 24-bit, 44.1khz Broadcast Wave files (equating to -24LUFS when summed clean) using Reaper and Harrison Mixbus. The plugin is actually more versatile (stronger saturation settings available) than the DAW equivalent.ĬONCLUSION: Harrison Mixbus is not an exception to the rule that all DAWs will null when set equal.Īnd, in fact, if you like the sound, you’re better off just getting the plugin because it’s cheaper.Harrison provides this saturation within a stand-alone plugin so you do not need the DAW to achieve its effects.Harrison’s built-in “analog modelling” is down to one saturation plug-in that defaults to “on” but can still be turned off.So, what can we take from this? Well, in my own opinion: Default will null at around -23dB and of course, minimum (-30dB in the plugin) will null just as it did to the control. When you set it to 0dB, it will actually null against the Mixbus at maximum. The default setting isn’t 0dB in the plugin. We’re actually hearing bigger differences than the control!īut. The default is marginal (barely audible) but present and the maximum isn’t anywhere near the Mixbus maximum. Īt first, the plugin does not seem to compare against the Mixbus equivalent. Or can it? Given that there’s this 32c bus plugin. Max Saturation will not null and produces a noticeable difference.Minimum saturation in mixes DOES null against a control - meaning it can effectively be turned off and thus the conclusion you can read below. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |