ppytprs wrote:So in conclusion, there's no way to apply one reverb globally to everything in a multichannel system.
...
Is there a way (for a future version) to apply the reverb like an insert to the group (like my second diagram above), such that if you had a group with many speaker outputs, you'd only need to apply it once rather than to every separate output? I guess it wouldn't be any more efficient in the processing, as it'd still be applying reverb to every output, but would be easier in the operation.
Hello ppytprs,
Just select the reverb for all of the primary mixer buses in your group. As nmailor mentioned, you can multi-select the buses to change their settings at once (with the exception of changing the selected reverb file itself) -- it only takes a few seconds to configure. Alternatively, apply the reverb to one of the master mix buses, and feed the output of that to a separate pair of speakers (e.g. positioned behind you), which is what most people who use multi-channel audio traditionally prefer to do anyway, since it gives the effect of the reverb coming from behind you, whilst keeping the drier direct sound coming from your main sets of speakers in front of you.
ppytprs wrote:But with this new reverb engine, are we heading to a different way of using HW? Will dry + reverb become the new thing? It's against the entire principle of the software as it was isn't it? I'm trying to slowly do some experiments of dry + reverb vs wet. I haven't decided what I think about it yet.
There's no intention at all to change the focus of Hauptwerk to dry sample sets + reverb, above wet sample sets. Hauptwerk has always supported wet or dry sets equally. The reverb functionality is included simply because lots of people wanted it (especially those people who prefer to use dry/semi-dry sample sets). You certainly don't have to use it, and wet sample sets won't be supported any less than they always have been.
Best regards, Martin.
Hauptwerk software designer/developer, Milan Digital Audio.