Stereo Tool

hold ...?
what is the measure instrument ?
Because with MPXTool i can`t see 100.1..
Where is the part with 100.1 , what is the exact minute /seconds ?
If it`s no problem to tell me ?!

Hello all... I havent tried any beta from Beta69. I compare Beta69 (onair) with Beta79 without Declipper Both, with same presset.
Beta79 has more compact sound, more clear Bass
Beta69 with Natural Dynamics has more clear Voices and highs and this is that is listening more stereo wide.

Thats my comparison, till now.!

but i still cant run it both in HIGH Quality, i have gaps my quality is Quality=30.000001907 pls HANS do something for this.!
I noticed that on Beta79 i can have full Quality.. and Beta79 with Dynamics will be BETTER than ever
and pls i want to try Declipper... is the default values ok to enable it?

_________________
Sexy Girls in your city

Sure! Just turn it on! There are settings that give slightly better results when there's really a lot of clipping, but the defaults should improve everything.

the latest beta is the best version EVER created for realtime audiio processing
( but presets matter a lot for a good resault )


Chris are u Greeeeeeeeeeeeeeeeeeeek ?

Yeah today again test the ... blop blop sound from the bass around 400 Hz like other users noticed .
And still there for beta 80 too ..... don`t know think of structure problem , not latency ...
Better Hans to say . Maybe is a filter problem .... like after or before some element , maybe it`s a filter oscillation. hope to find the problem and solve it

Yes as long as the HPF is not fixed you will get that strange sound around 400 Hz. I still think it's a bug and i'm still waiting for an answer about it from Hans. See my latest question about it.

About the maximum hold. It's in the MPX stool statistics. If you play the recording you can see where it peaks at 100.1%
I can look later for you if you want to know where it exactly happens, but you can also try it yourself.

I try man ....... but .... no success
Thatswhy i want to tell me

Ok i see what's the difference.
I have Response set to instant in MPX tool, so it will respond even to very tiny spikes.
The default setting is 125us, but with that setting it will respond less to very short spikes in the MPX.

With the response set to instant i have Maximum Hold of 100.1% at around 5:31.
With the response set to 125us the maximum hold of the whole recording is 96.7%.

..... ok man see it now but don`t panic this is not a spike ..
spike is let`s say 105 110 % and above this is a real spike ... 100.1% would be a MPXTool error ... so everything is OK .
If you see what are doing the stations here in Bulgaria or Romanian radios ... you will take the gun and pull the trigger

@eldoradofm and others: The 400 Hz issue is caused by a design flaw in Stereo Tool that has been there since version 1.0 - the effect has gotten less bad over the years but I never managed to completely get rid of it. I think I know the solution now, but the only quick fix (not even a full repair) for it would double the CPU load which is unacceptable to almost everyone so I need to find something better.

Yesterday I visited Leif in his new office and we visited a pirate radio station called Radio Olifant (Radio Elephant) which played mainly Dutch and German language music and polka, all from vinyl . Anyway, we've been chatting all day and it looks like we gave each other some hints for big improvements in both our products. Can't tell you too much about it for now, but in a moment I'll post a new BETA in which I improved the clipper design a lot further - and the difference is really noticeable. This time it sounds _better_ than before instead of worse. And the output is another 0.1 dB louder.

Note: This filter change is intended to make the filter more efficient in what it does - reach peak levels without audible distortion. The redesign does NOT tackle things like volume drops when loud highs kick in, or voice vibrations (although both should be reduced a bit because the filter is more effective now, especially when FM output is used).

Note #2: The code is not yet fully optimized, although it runs at a higher speed than BETA080 due to a bug in that version. I'll look into the performance later.