Stereo Tool

Hans,
can you tell us briefly , what causes this ringing (sine shaking) in MB especially between band1 and band 2 .
You said before that if quality slider can go to 200% , this "ringing" will be gone.
But why it appears only if difference in level increases ( i see it if the differenece go above 4 db , ringing starts to be noticeable). Difference can be positive or negative (same behavour). When they are equal (let`s say band coupling is used), no ringing in this case or effect is close to 0
"Flat tops" helps a lot for that and sounds so good

What is so "big pain" when level difference. And can MB be like AGC (as i remember you said AGC is a some kind of crossover type). Surely it will consume less CPU if it`s like that.

Edit: This effect occurs between band 1 and 2 . Around band 3 everything is OK. I think the problem is somewhere in the first band only, and continues close to 75-80Hz Hz in my opinion. At 100Hz , shaking is almost 0

MB message about multiband number changing is not hidding when i give it "No, and don`t ask me again" It asks every time

Something strange that i`ve never notice on old versions. When i enable only the Pilot 19 Khz without RDS there is some little peak stands to the lowest RDS floor , see it on picture.

bmp not allowed , sorry will have to attach it via external site. Because if i make it jpg , may be peak will not be see-able.




Edit: WOW , i just realize that this is the 3-rd harmonic of 19Khz . 3x19=57

yup! it's like with my question about what that hump is in the spectrum behind main audio when you demodulate MPX (it was RDS...) But recently I wondered why sidebands are present in the FM RF spetrum (in AM it's easier to understand). Well... and I got the answer I was looking for that turned out to be some kick-ass equation There is always something to learn.

@DJ_DOGGY: Bumps Come from steep filtering. If the bands are at equal level, the effect disappears when the bands are added back together again (The bump is in bands 1 and 2 in opposite direction).

There is a sort of fundamental frequency which is related to the bl kock site (4096 at 44100 Hz Is pretty close to 10 Hz, the further you get from there the less impact it has).


Pilot: must be a rounding error, will check it.

Thanks for the explanation Hans.
Is that mean if we have the lowest steep option (3db) it will be the lowest effect . And the opposite - if we use the highest steep(64db) , the effect will be increased ? Or may be if we use another sample rate ?
or this is not affected by this..

I wonder is there any solution ? Like this effect to be "moved" to the low side , let`s say below the highpass frequency which is 30Hz by default . Or any improve to the lowest filtering. i mean without increasing a lot the CPU load . Or may be to add the solution by adding separate button fot it , so we can turn it ON and OFF ?
I`m saying all this because it looks a kind of ... i don`t want to look like Criticism but this must be out of ST . ST is a proffesional program and is very very flexible . You can do almost everything with the sound So i hope you understand me right .

The first solution that i realize according your explanation is 4096 to become 8192 ? You must talking about the latency, right ?

@DJ_DOGGY: Well, increasing the latency would reduce this effect but it would create other problems. There is another solution that adds latency that might reduce the problem. But: Do you actually *hear* this effect when you play music instead of tones? At latency 4096 Quality 100%? Because I don't...

For music don`t hear it. But i test with tones just to see if there is something wrong (in this case effects like that). Because tones are the very best test method

Windows 32 bit:
Windows stand alone: http://www.stereotool.com/download/ster ... 52-010.exe
Winamp DSP: http://www.stereotool.com/download/dsp_ ... 52-010.exe

CHANGES:
- Fix declipper + PNR. Does it cause problems if it's used as intended? MUST BE TESTED TO MAKE SURE IT DOESN'T DAMAGE THE SOUND
- Fix crash when clicking on volume bars.
- Highs Gap Protection: 2nd step does almost nothing - why? - Correct, but seems ok this way...
- Highs Gap Protection: power_X must not be used (sounds better without), but it must be used for something else because if power_X is 0, the current filter is insufficient. --> Now not using power_X anymore, but 3 steps instead of 2 in HQ gap mode. This seems to be very close to the optimal result. Need feedback on this.... it appears to be ok but I'm not 100% sure that the problem is completely gone. And I still need to test if it doesn't increase highs intermodulation distortion (probably not though).

Note: CPU load for Highs Gap Protection in HQ mode might be slightly higher (haven't tested it yet; I'm doing more but I have also optimized the existing code).

TODO:
- Highs Gap Protection: Turn 3rd step off for non-FM mode.
- High Gap Protection: Forgot to make changes in Composite Clipper mode.
- ABDP: Check mid tone intermodulation distortion protection code. viewtopic.php?f=3&t=5734&p=26879#p26879 MADE A VERY SMALL CHANGE, WAITING FOR FEEDBACK MIGHT BE BETTER OR MIGHT BE WORSE.
- ABDP: Mid tone intermodulation distortion: Make new filter at start of ABDP to control mids clipping level. Clip lows and mids separately, then together, measure volume loss for each and then use that as new clipping levels. Only in case where there are loud tones present (voices) with loud bass. Bojcha: Phase Tornado fixes it.
- Sloppy causes crackling sound in piano's. Should probably be switched off is there are very little highs.
- ABDP: Calvin Harris ft. John Newman - Blame has distortion in lower highs; Highs distortion protection doesn't seem to handle it properly. Except for that I'm now getting a good sound for almost all tracks with bass clipping set to 100% (!) and Highs Priority to 20%, Sloppy at maximum
- Hide panels in password protected mode or something
- Check pilot generation code (57 kHz harmonic)
- GUI: Weird jumps at 100 ms buffer size reported by DJ_DOGGY
- Check Multiband settings Bojcha in Skype

PREVIOUS:
- Don't use Sloppy value when ABDP is disabled.
- Highs Gap Protection caused a jump in the spectrum between 3.5-3.8 kHz for loud highs. This is now smoothed over a bigger area (2400-4800 Hz).
- Bad gap in ABDP - causes highs to sound less full. Fix ASAP! Only in Composite mode! Was introduced in one of the previous beta's
- Make Configuration, Repair and Processing settings saveable separately.
- Split filters in Restoration / Processing.
- At Band Coupling '0' the values in the GUI weren't recalculated properly.
- Default value for Sloppy was 0% (-99 dB), should be 100%.
- ABDP: Added new "Sloppy" slider. Effect: Slightly louder, 0.5 dB more highs! And probably less pumping due to highs. (*)
- Band coupling settings don't work if Band Coupling slider in main Multiband window is set to 0%.
- Declipper result is very bad if PNR is used before it. NOT SURE YET IF IT'S REALLY FIXED.
- PNR can also be done AFTER declipping.
- Display FM lowpass frequency at bottom when FM output is used.
- Show warning when PNR is disabled due to changed settings.
- Added Multiband compressor Band Coupling matrix. You can use this to overrule the standard band coupling settings. Only available in Extreme Tweaker mode, awaiting responses to see how useful it it (if it is useful I'll move it to Expert mode).
- Advanced Clipper: Advanced Bass Distortion Protection (ABDP): Drop in output when strongly clipping around 2600-4000 Hz is reduced.
- Advanced Clipper: ABDP: "Smooth Slide" slider added to make transition between deep bass (clipped) and less deep bass smoother. There used to be a drop upto the 2nd configured bass frequency, with this switch enabled the drop is smoothed (maximum at 1st configured bass freq, gone at 2nd). Result: Warmer, more open, less 'restrained' sound. But probably also a bit more intermodulation distortion. (which might be fixable by changing the frequencies a bit). (*)
- Added PNR Noise & Hum
- PNR analysis data is saved now

one more for the "to do" if planned for now : the problem with the 0.100 sec resolution "Output signal display" reported some posts back.

Something here is not aligned right ?
May be the L+R must be the main and then separate displays for L and R