Stereo Tool

That makes sense to me, at least given my limited understanding of this type of low level stuff. I was just wondering if and how that relates to your question over on the Intel forum about portions of the code that won't vectorize.

fft_abs_sse2[2*cc] = max(fft_abs_sse2[2*cc], strength * m);

for (int c=0; c<f1; c++)
{
temp[2*c] *= one_DIV_bass_static_clip_level_dynamic;
temp[2*c+1] *= one_DIV_bass_static_clip_level_dynamic;
}

Forget about the instructions now.
We have a problem with the lowest band in MB ...
The "blop" effect . Also i see in the output scope some wave strange behavior when i put on low freq. tone say 35 40 Hz ? I can hear the "blop"effect .

The only strange thing is that when i put he Coupling to 100% this effect is reduced a little . I will make a video to show you all what i mean . And i`ll put it in the post after i make it.
Think that there is some wrong "calculation" in the filter.... other bands are not giving this effect. Tested with Bandpass OFF , same thing .All is coming from the MB

Question about the coupling parameter in the multiband.

When i slide it to 100% much songs sounds like " muffie"
Try this song whith the r type preset from Bojcha
Alexis Jordan - Happiness
sounds not nice when you slide it to 100%
Or is this normal?

_________________
Garbage in is Garbage out !

I compared with Beta 45. I did nt try the next ones cause of cpu overload.

_________________
Sexy Girls in your city

With coupling set to 100% all the bands will do exactly the same, so it behaves as a singleband compressor, although 'band mix' still works. So don't set it this high!

I think I should probably display the 'band calculation matrix' that is used. When I made this slider I viewed it by writing it to a file and it really helps to see what's happening. It might also be useful - extreme tweaking mode - to make this editable manually.

Preset is already VERY well balanced (maximum what bands can give) but yet preset/mb do full processing. For a reason coupling is disabled in preset - it does not need that, also, crossovers are tuned maximally to separate bands well already.

Setting BBP (default Rustonium settings) MPX output level to -3.0db feeding MPXTool, the peaks in MPXTool (default -3db input) frequently hit 100% modulation on most songs.

Setting ST (R-Style, latest beta) MPX output to -3.0db, with no composite limiting, peaks only frequently hit 92/93% modulation in MPXTool. Composite limiting has to be turned on quite high (~108/110%) to achieve peaks hitting 100%.

Is that expected and correct behavior?

And is sound card input still only 16 bit resolution ?

So , the video with the strange behave . When i turn the MB off it stops . Hans ?

http://www18.zippyshare.com/v/98468466/file.html

- Is it post amp at 0.00 (100%) ?
- Turn RDS OFF, since in BBP was not there when you tested
- Set composite to 102%
- Pilot 9.00% and RDS 4.53%

Result: http://i.imgur.com/6l04IFa.png

If you want RDS now set composite to 102+4.5, so ~ 106 or 107%.

In BBP composite clipping can not be turned off, so the comparison is not fair in my opinion.
So, in order to make a good comparison, you should at least turn the composite limiter in ST "ON" since ST does not have a composite clipper YET. (i assume BBP uses this to some degree, depending on preset)

_________________
----------------------------------------------------------------------------
AIRCHAIN-GURU professional independant airchain consultancy.
Orban/Omnia/Vorsis/DSPX/Aphex/Inovonics
----------------------------------------------------------------------------