Stereo Tool
https://forums.stereotool.com/

Stereo Tool 6.10
https://forums.stereotool.com/viewtopic.php?t=3065
Page 69 of 213

Author:  Bojcha [ Thu Jun 09, 2011 2:17 am ]
Post subject:  Re: Stereo Tool 6.10

is this OC forum or what ? :D

- E8400 @ 4,5GHz (500MHzx9) + ThermalRight True
- OCZ 1:1, so 1000MHz Dual Channel
- 2xOCZ VertexII SSD in Raid0

:P

Author:  hvz [ Thu Jun 09, 2011 2:47 am ]
Post subject:  Re: Stereo Tool 6.10

Quote:
@Hans, can we also expect a tilt correction slider for the output, with a 60 Hz square wave test tone for adjusting it?
That would be very useful... For FM output the workaround for this is to set all the phase sliders to the same value. And you'll have to find a 60 Hz square wave yourself. I'll add something like this later, but I'm not going to add it to the TODO list for version 6.20 anymore because it's really starting to take way too much time to get this version finished...

Author:  Nuke420 [ Thu Jun 09, 2011 7:29 am ]
Post subject:  Re: Stereo Tool 6.10

Quote:
is this OC forum or what ? :D

- E8400 @ 4,5GHz (500MHzx9) + ThermalRight True
- OCZ 1:1, so 1000MHz Dual Channel
- 2xOCZ VertexII SSD in Raid0

:P
I should see how well ST runs on my new rig. the i7 2600K @ 4.8Ghz (Sandy Bridge) 16GB Corsair 1866 DDR3. I usually just run it on an older Dual Core. :)

Sorry. Didn't mean to derail again.

Author:  DUB<^>STEP [ Thu Jun 09, 2011 6:40 pm ]
Post subject:  Re: Stereo Tool 6.10

Quote:
is this OC forum or what ? :D

- E8400 @ 4,5GHz (500MHzx9) + ThermalRight True
- OCZ 1:1, so 1000MHz Dual Channel
- 2xOCZ VertexII SSD in Raid0

:P
I do believe its over-clock war time.

i haz
WINDOWS 7 X64
CPU QWOD CORE. INTEL I7 930 -4000MHZ 1.28V
RAM ...6GB
MOTHERBOARD....ASUS RAMPAGE ll EXTREME .
SOUND CARD..SUPREME FX -FI
GPU GTX480.
HDD . ONE 80GB SSD AND A 2TB WD DRIVE.
..
I used to have the E8500 but I got a new system. very easy to oc.


but yes you have a good system there.

on my system stereo tool uses 4% on my cpu.

ANYWAY BACK TO STEREO TOOL AGAIN!

Author:  hvz [ Fri Jun 10, 2011 11:14 am ]
Post subject:  Re: Stereo Tool 6.10

BETA058:
Tilt detection performance improvement. (Now 13 calculations instead of 34, result should be identical).

From the previous beta (still valid):
The CPU load is also pretty high because I'm calculating 32 different tilt levels to find the best match (so automatic tilt detection works, but it needs serious optimization).

New slider: "Declipping margin" - if you set this to 75%, everything above 75% of the maximum level is considered to be potentially clipped.

Changed slider: "Never consider samples to be clipped if they are lower than:" - rule out soft sounds, whatever they look like, they are not clipped.



Winamp DSP plugin: http://www.stereotool.com/download/dsp_ ... 20-058.exe
Stand alone version: http://www.stereotool.com/download/ster ... 20-058.exe
VST version: http://www.stereotool.com/download/vst_ ... 20-058.dll
VST version (No SSE2): http://www.stereotool.com/download/vst_ ... 20-058.dll
Command line version: http://www.stereotool.com/download/ster ... 20-058.exe
Linux command line version: http://www.stereotool.com/download/ster ... ETA620-058 NOT AVAILABLE
Linux GUI version: http://www.stereotool.com/download/ster ... ETA620-058 NOT AVAILABLE

TODO:
- Fix loading changed multiband frequencies
- Add buffer and filter for SCA output (SCA1 ok, SCA2 ok)
- Finish AGC improvement - make mono value configurable (replace checkbox by slider) 1 hour --> NO, not needed - anything else needed? -> NO
- Fix Punch
- Check what to do with new filters (such as bass AGC) - keep them, remove them, change them? --> KEEP
- Save new BASS_AGC setting in VST mode
- Loudness: Annoying cracking sound in bass. Slightly present in 5.00, worse in 6.00, maybe even worse in 6.10. Only when bass is too loud. Much worse than in Final Limiter (at same input level!) - so this clearly indicates a bug. Most likely cause: The filter that was added to remove bass artifacts....... :shock: - No, it's the louder bass. But it can be fixed by changing some settings. Default settings updated, and behavior for 'not Very strict' improved. Also Deep bass boost and Very deep bass protection are enabled for latency 512 now.
- Fix crash at program close
- Fix VST plugin version (does not run)
- Dynamically drop 'Allow louder highs, even if it causes vibrations' to 0 when bass filter suspects noticeable voice vibrations. 1-2 hours
- Reduce Loudness CPU load days?
- Check and remove static variables
- Finish new de-essing filter (check what to do with the settings, remove at least some!) 1 day
- Convert Multiband input to MONO, then use arrays [2][4096] --> should give speedup. - FAILED
- Natural Dynamics: Fix or remove transient boost
- Natural Dynamics: Add expected + strength slider per band
- Finish declipping filter (clipping level detection + level reduction in dB). 1. Figure out why removal of unwanted frequencies causes flat lines at high quality setting with small overlap. This causes distortion, with this fixed repairs are MUCH better. 2. Fix MP3 correction, automatically scale down when this deteriorates the sound. --> TOP part fails!
- Declipping filter: Fix low latency behavior
- Always oversample clipping (configurable)
- Declipping filter: Change detection at lower input levels.
- "Test Right Channel" in "FM Transmitter Calibration" does not work since v6.10 (standalone) (bojcha)
- Declipper window close function - check! - Seems ok
- Scopes black background?
- Add AGC start level
- RDS issue reported here: viewtopic.php?f=15&t=3703&p=11524#p11524 partially solved
- Natural Dynamics: Voices, especially in chorus, still sound weird.
- Natural Dynamics: Smooth out different bands more to reduce low-bitrate-MP3-like sounds.
- Natural Dynamics: Optimize situation with no interaction between bands for performance.
- Declipping filter: Add setting and saving of new sliders (history size, percentage of highest samples to drop, tilt detection range start, end and precision)
- Declipping filter: Add comparting of sample history to make sure loud bursts are still detected properly (now, with 16 blocks of history, 65 samples are removed even when ignoring just 0.1%).
- Declipping filter: Optimize tilt detection for performance
- Declipping filter: Optimize peak matching for performance
- Update presets? (BASS_AGC etc.) 1 day
- Finish blind interface
- Channels L/R swap in stand alone version when changing filtering/quality (?) (eldoradofm)
- Move pre-emphasis to end of processing 1 day
- Save all new settings, also through VST interface
- Change version number 1 hour
- Release 1 hour
- Add lowpass filter for stereo signal (will cause a lot of extra latency!) - it might be possible to avoid this latency using a Hilbert transform
- Add smarter clipping detection. Maybe something much simpler suffices: Current clipping detection with threshold + flat line detection
- Declipping filter: Automatically override the 3 clipping level sliders if the clipping level is detected very clearly (clear thin spike in sample value histogram). - NONSENSE, this is already done by the histogram function. But it can be made a BIT better - I think - by automatically LOWERING the 'always clipped' slider if a lot of data is present at the highest few bins (but care is needed for DBN - Jack is Back like tracks)

Author:  Brian [ Fri Jun 10, 2011 1:36 pm ]
Post subject:  Re: Stereo Tool 6.10

Quote:
BETA058:
Tilt detection performance improvement. (Now 13 calculations instead of 34, result should be identical).
With 57, Winamp was running in the 80s as viewed by Task Manager with enabling declipper with all the other items in my preset on. With 58, that has dropped to 68-75, so some improvement. I used 57, since you were modifying Natural Dynamics, not Declipping, so I shouldn't have to fall back further, I wouldn't think...

Author:  Bojcha [ Fri Jun 10, 2011 8:32 pm ]
Post subject:  Re: Stereo Tool 6.10

I think that "clipping detection" in DeClipper should be higher, around 2.50dB

Author:  hvz [ Fri Jun 10, 2011 8:50 pm ]
Post subject:  Re: Stereo Tool 6.10

Quote:
I think that "clipping detection" in DeClipper should be higher, around 2.50dB
Tot kwam vignet, so lees android?
And only for BETA058 or also for previous versions?

Author:  hvz [ Fri Jun 10, 2011 8:54 pm ]
Post subject:  Re: Stereo Tool 6.10

Error correction sucks on Android, esp. if you select the wrong language...

So what I wanted to ask was: with higher, you mean less sensitive?

Author:  Bojcha [ Fri Jun 10, 2011 8:57 pm ]
Post subject:  Re: Stereo Tool 6.10

i checked this track (posted by Brian)
http://www.musicremedy.com/musicaudio/D ... e-4335.asx

And some obviuos samples are not 'restored'. that was in beta057. (default settings)
In beta058 (default settings) something is different for same track. More restored. So i get better result when i set "clipping detection" from 1.40 to 2.50dB.
Maybe other should be readjusted (?)

edit:Clearly less 'red' on scope

Page 69 of 213 All times are UTC+02:00
Powered by phpBB® Forum Software © phpBB Limited
https://www.phpbb.com/