*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.Default saturation from Mixbus will not null against a control.So, put that all together and you can find that: Harrison makes a 32c bus plugin which appears very alike to the Master channel in Mixbus.(But is it always doing something? See below!) You can disable most things but the “tape saturation” section remains active. Mixbus’s Master Channel, however, works a little differently.This processing actually defaults to off. Mixbus has options to disable any processing applied to individual channels.I’ll try to keep this as brief as possible but my basic findings of the DAW were: Well, the answer to all that is: IT WILL NULL. So that got me thinking “ Does Harrison’s DAW work any different?” Are the plugins that Harrison sells as stand-alone products reflect what is in the DAW? Can what is in the DAW be turned off to the extent that it can become the same as any other DAW and null against them? Can I add a Harrison plugin in any other DAW and null that against Harrison’s DAW and any inherent analog modelling it applies? There are no further parameters on that plugin to introduce saturation, THD or otherwise. Specifically, this video where he makes an expose on Harrison’s 32c channel strip plugin and how he can make the EQ null with only a stock EQ plugin (ReaEQ.) This shows that the 32c is not imparting any “analog character” as Harrison claimed, as modelling all components in an analog circuit should also introduce harmonic content. On the surface, I was willing to accept this, until I was coincidently introduced to Dan Worrall and his brilliant deep dives into audio phenomena. In the last thread, a common theme when concluding that all DAWs will sound the same was to caveat that Harrison’s Mixbus would not null in comparison to other DAWs because it models Harrison’s analog consoles within the interface. For Mixbus32C: A monitor with a height of 1200 pixels (or more) is highly recommended.This is a continuation post to this discussion.For Mixbus: A monitor with a height of 900 pixels (or more) is highly recommended.600 MB available hard disk space (for program installation only).A full-size keyboard with number pad is recommended (extra transport controls on the number keys).Trackpads and "Magic Mice" also work well. A standard 3-button mouse with scrollwheel is recommended.2Gig or more RAM is highly recommended (or much more, if you use sample-based virtual instruments).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |