Stereo Tool

Strange one berrall - my DeClipper license is valid and I get the ND showing as active.

I don't have an FM License though, maybe that's the issue?

_________________
I just use ST with liquidsoap to enhance a streaming radio station I like...

There was a problem which caused ND to be deactivated for some licenses that did include the declipper - fixed in next version. Crash is also fixed.

It's normal. I don't know if it can be fixed (it probably can but I'll have to somehow dynamically load the Jack library myself instead of relying on the automatic mechanism - right now it crashes during loading, so long before I get the change to do anything.

Windows:
Winamp version: http://www.stereotool.com/download/dsp_ ... 25-012.exe
Windows stand alone: http://www.stereotool.com/download/ster ... 25-012.exe
Windows VST: http://www.stereotool.com/download/vst_ ... 25-012.dll

Changes:
- Hangup when pressing Natural Dynamics in bottom display
- ND license incorrect
- AZIMUTH default settings: viewtopic.php?f=15&t=4875
- Phase rotator: Change name "As early as possible" (unclear!) and hide in most modes?
- Organize ND settings better
- Fix loading existing presets (Gamma values, "As early as possible" etc.)
- Split ND settings in to GUI modes
- Remove old ND implementation (saves memory and makes STS files smaller) -> 8 MB less memory usage


Copy of Gamma description
Ok, about attack and release gamma. Bojcha pointed me to this issue. In the compressors, if there's a volume change, it takes quite long for the level to 'stabilize'. That's because the closer the actual level gets to the 'target' level, the slower it moves (the shape is asymptotic). Something similar happens in release. I always assumed that this is a good thing, and traditionally this is what compressors do.

I have now added a 'Gamma' - similar to the Gamma function that you can use in image processing to make things lighter or darker. Basically, what this does is:
- If the difference in level is 6 dB, nothing changes
- If the difference in level is less than 6 dB, for Gamma values > 1 the change speed is increased.
- If the difference in level is greater than 6 dB, for Gamma values > 1 the change speed is decreased.
More technical: We're using the Gamma'th root of the difference in level - so for 2 that's the square root etc.

What this means: The higher the Gamma value is, the more the movement to the new level will look like a straight line instead of an asymptote.


Fixed previously:
- Multiband: Improved Flat Frequency Response. Good values seem to be between 0.50 and 0.60 (depending on other settings!)
- Multiband: Added Attack and Release Gamma. See below.
- Phase rotator: Added checkbox to place it at the start of the processing chain (just before Natural Dynamics)
- Multiband/Natural Dynamics: Cleanup small spikes in Flat Frequency Response graph.
- Multiband/Natural Dynamics: Improve flat frequency response further.
- Mac: Default priority value to 46.
- Mac: Menu bar with Close APPLE+Q -> wxEntry exits but rest of software doesn't -> crashes.
- Mac: Cleanup named semaphores on exit
- Mac: RDS binary values
- Multiband/ND: Flat frequency response: value automatic conversion. ((v / .58) ^ .5) * .58
- Decide to which license to link ND -> Now linked to Declipper
- MB Knee does not work -> Yes it does...
- Linux: Test if everything still works. -> Yes, some small fixes were needed. Also removed printing to screen in Jack loop (bad!)
- Compressor: Place Gamma somewhere logical without making the interface too crowded.
- Display ND in bottom section
- ND handle changing number of bands
- Mac: Add auto-generating of .zip file with proper plist.
- Mac: Add icon
- Changed ND default settings (experimental!)

Remaining:
- Check and improve performance (Gain?)
- Default settings for ND
- ND artifacts band 1 (JesseG) - is this still an issue with larger drop times?
- Add presets

Later:
- Try to reduce MB/ND volume measurement CPU load. Maybe ignore some bands if there's nearly no signal there etc.
- Multiband/ND: Flat frequency response: Add separate settings for each crossover?)
- MB bands limiting display - Really difficult to fix (without increasing CPU load); it works fine without band coupling, and shows the actual reduction level if band coupling is used. So keeping it like this for now...
- Mac: VST: Child window support. Difficult... Maybe later!
- Mac: GUI performance.
- Mac: Cursors not supported. (Keep like that for now).

ND license issue is now ok with latest beta.

The default frequencies for the five MB bands after first start of initial install or factory reset are different from the settings you get after switching to e.g. six bands and then back to five bands and accepting the 'new' default settings the dialog box asks you for.
Is this intended?

Is there come back the situation of turning ON and OF the Normal output to affect the Fm output again . I think on last version or before last this behavior was changed not to affect . Now when turn on/off both outputs are restarted and even that not every time the Normal output is filled right on starting.

P.S: Do i notice some CPU load higher ? like 3-5%

I didn't change anything in that code in the last few beta's. (Or actually, since releasing version 7.240).

CPU load, compared to which other version?

the last beta compared to the last release 7.24 . i just see some little more load . I`m not saying that i`m fully right but just want to know and may be test for load . Is there any program to test load of the threads with other dimensions , not only %

And you didn't enable ND or anything? Could be the Gamma in the compressors, I might need to optimize that a bit.

The best measurement method that I know if firing up Winamp, sending output to a fast disk (MP3 encoding helps to avoid hiccups, although it does slightly offset the measurements), and then see how much it can process in a constant amount of time.