TOPIC:

Here's some very odd behavior. I have 3 way active speakers, and I normally just run them with a digital input, 2 outputs to my tweeters 2 outputs to my mids and 2 outputs to my bass woofers.

Sometimes I run my midrange drivers by themselves, full range, just so I can tune them without hearing the influence of the tweeters or the bass woofers. When I do this, I mute the tweeter outputs (Output 3 and 7 on the miniDSP), and I mute the bass outputs (Output 1 and 5 on the miniDSP)

Next, in the midrange crossover settings I bypass both the low and high filter points for the midrange by clicking the "bypass" buttons.

So, now I should be getting a full range signal to my mids with no overlap/influence from either the bass or the tweeters, right? I thought so too, but that's not true.

The weird behavior is this - when I go into my muted tweeter crossover settings and toggle the bypass option for it's high pass setting at 2500hz, the sound from my MIDRANGE driver is affected, significantly. With the tweeter crossover bypassed, I get full range sound from my mids. If I engage the tweeter crossover, I lose highs from my midrange. WTF????

As a final note, none of my channels are linked together in any way, so it can't be that.

Can someone explain this behavior to me, and show me how to avoid it?

Updated to the latest firmware and to the IR Beta 4x10 plugin to try to fix this. And it did! I've tried every combo of bypass, crossover slope, and outputs I can think of and nothing affects anything that it should not.

So, if you guys are seeing issues like I describe earlier, upgrading to the latest plugin and flashing to the latest firmware addresses it.

"... now I should be getting a full range signal to my mids...."

That sure sounds dangerous, as well as potentially misleading.

What's the point of sending low freq to the mids that they won't be getting in use?

Plus it may distort what they will.

Mmmh, this is an odd one which we've never seen before. From talking to the engineers, it sounds like it could have been an issue related to "configs" (and their subsequent bypass settings)that linked up to the bypass feature (i.e. disable the filter).

Thanks for sharing the issue and glad to hear that problem is solved on the latest firmware.

Devteam