Stereo Tool

I get strange slider effects in GUI when i click the gating level block.

@Hans:
I don't think it's on but what is the line I'm looking for in the STS file to make sure?

Thanks Hans, that sounds good.

The much much more CPU-Load (with beta 28) I can recognize, too. And no, I defenitly don't use the declipper, because it doesn't work with my PC. Activate the declipper the sound-output is dropping hard with winamp-DSP and with wavelab and VST the sound turns off (using the same preset).

Any idea's?

Greets
Maic

@maic, baires:
Could you try beta030? I'm not home right now, but that's the version I eerdse with this morning, and i didn't see any big jumps like that. Maybe there was some logging still enabled in 028 - I'll take a look tonight.

Clipping is disabled on startup, so unless you enable it it's off.

@eldoradofm:
Oops - in Las Vegas I met a blind guy who asked for a standard Windows interface so he could control it with screen reading software. I still need to disable those buttons in normal mode.

@Hans: I will try it tomorrow, for now I have to go to bed 'cause my alarm clock is ringing at 3 o'clock AM... ;-(

Ouch! That cannot be good! You should have it repaired!

I did the check myself, and I don't see any difference between 6.20-BETA028 and 6.20-BETA030.

I've also done a measurement with the !63 preset, and with that the difference that I'm measuring is that 6.20-BETA030 is 21-22% slower. Which is quite a lot, but still far less than what baires0314 reports.

Edit #1: With LOUDNESS disabled, the speed of 6.10 is equal to that of 6.20-BETA030. So Loudness seems to be the cause.
Edit #2: With ONLY Loudness enabled, 6.20-BETA030 is 44-45% slower than 6.10.


bairnes0314, could you check if you can confirm these results (the fact that it's only in Loudness)? Since your numbers are FAR more extreme than mine I wonder if something else is going on in your case.

You also had someone a few pages back complaining about stuttering using the preset that I made. Obviously I have no issues using the preset, and it uses loudness...

Hi Hans,
Hope you had a great time at the NAB.
Skipped quite a lot in terms of events and beta releases since the last time I checked in. So, going through the old posts from the archive.
By the way, congrats for the De-clipper that you have implemented.
I am yet to check out the betas in which De-Clipper can be seen in action. The last beta I downloaded (probably ~b11) had an issue with loading presets that have 'Minimum attack speed near top' > 1.0. I am referring to VST plugin. No matter what value I assigned to this parameter, it loads 1(or may be 0.9). Unless I manually move the slider in the GUI or 'Load the preset' multiple times (twice or even thrice). Simply selecting the preset from frequently used PresetList does not help.
Would check this out if it works the intended way in later releases.

Eagerly awaiting the De-Clipper to be made automated.
Good luck with your work.

_________________
visit website

Things are a bit slow here. I'm working on a clipping detection algorithm, which works for ALL kinds of clipped audio, and that turns out to be more difficult than I had expected.

I want something that can find clipped samples both in 'normal' clipping, but which also detects clipping in - for example - the Metallica track on the Perfect DeClipper site. And that automatically.

Now I actually managed to write something that's doing a VERY good job on the Metallica track, but it turns out that it flags far too many samples as 'clipped' in normal (not clipped!) audio, causing sounds like what Bojcha posted a few days ago. So it's not very usable yet.