wavehammer surround broken - for you too?

ibliss wrote on 11/22/2005, 8:29 AM
This is a cross post - sorry, but no one in the Vid forum has responded yet. Trying to find out if this plugin is buggy for everyone or just me, before I send to support/ report it as a bug.

Wavehammer Surround plugin is supposed to let you choose which channels trigger compression (ie trigger the threshold control) and which of the output channels the compression is applied to.

I thought 'oh, so you could route music through the front pair, dialogue through the back and set up automatic ducking of the music when ever speech occurs. Wavehammer would be set to respond to the voice going through Ls and Rs, but only compress L+R channels. (then render the music track for re-import into a project - i didn't actually want the audio routed this way!!)

But it doesn't work because the plugin is broken - threshold still reacts to all channels it seems, and also the L R Ls Rs C LFE channels in the 'Routing' tab of the plugin seem to affect the wrong channels -
the are labled: L R Ls Rs C LFE
but seem to be: L R C Ls Rs LFE

Anyone else? Is this a know issue?

Comments

ibliss wrote on 11/22/2005, 5:55 PM
Here's an update:

The channel lables for selecting which channels trigger compression and which are affected by compression are definitely wrong. Actual order is L R C Sl Sr LFE.

When in peak dection mode, wavehammer surround responds correctly to only the chosen trigger channels.

When in rms dection mode, wavehammer surround responds incorrectly to both the selected and un-selected trigger channels, and compressess both un-selected and selected channels. BUG.