Stereo Tool

it looks bad ...

@Bojcha, that separation channel value used for the test?

_________________
by GAP
"Less is More" (Bob Katz)

hm?
Used Waves RVox compressor wich process both channel as separation 0% as almost every other compressor.

I have tested both, separately. Neither had any measurable effect on the CPU load.

I don't understand why you are confused? This is method 1 from my list of 2 options: Take the loudest channel and adjust all channels based on that. The other option would be to let BOTH channels be a bit louder, by using the average signal for BOTH channels - the -1.4 dB would then probably be a bit ABOVE 0 dB (!) and the other would again be 6 dB lower.

For sure avarage is not good.

Ok, then i'll wait solution1 when implemented.

Oh, i am intereseted about how it would work in "separation = 0"

I'm using a 2012 laptop with core i5 64-bit and dual core. I'm not familiar with the details of processor technology but I think a processor so new should support SSE3.

Made a lot of changes today! Some of these are important (as in: Have a big effect on the audio).
Removed Use side chain button. So presets might function differently if you disabled this button but had processing enabled elsewhere!
Compressor: Changed stereo separation in Peak mode. Now compressor responds to the loudest channel (at 0% separation), there's no averaging anymore.
Compressor Knee: Fixed bug that caused huge volume effects at large Knee values. So any preset with Knee values above - say - 10 dB should be checked!
Equalizer: More resolution for lower bands. So if you drew a shape steeper than what was allowed earlier it will sound differently now!

Also, Synchronize to output (stand alone version) should work now - not yet tested though, it might crash or do weird things.
And Multiband medians are displayed.

- I think I should probably remove the 'Use side chain' button, to make it work the same as all other side chains.
- I think I need to put the top line of Multiband sliders (which are very small) in a separate page.
- Add hold multiplier; in Simple mode replace all multipliers by one.
- And change the scale of the Drive slider indeed. -> Probably affects ALL sliders with values in dB's!
- Compressor: Fix stereo separation in Peak mode
- Multiband Compressor: Display coupled bands - Done, but without coupling is no longer visible!
- Multiband Compressor: Median displays (new MB only)
- Remove "blob" from Knee
- Equalizer: More resolution for lower bands - Twice as steep allowed now. #define peq_steep.
- Sound cards: Make 'Synchronize to output' work with Normal output To be tested; might crash/hang

Separate tests do not provide end-to-end SSE3 code. Based on your description, BETA053A does not have end-to-end SSE3 support.

To summarize:

- You have an Intel system, not an AMD system.

- Intel systems do not have the potential for sub-optimal codepath generation unless the person doing the compile instructs a lower instruction set intentionally.

- AMD systems have the potential for sub-optimal codepath generation despite what the person doing the compile does in numerous situations.

- If 43% of the time is spent in IPP libraries, and you made the non-IPP code as SSE3, but IPP code as FPU, MMX, SSE, or SSE2, then you absolutely do not have a beginning-to-end SSE3 code path, thus it is an invalid test case scenario.

- The performance that you will see in a mixed SSE3 and other instruction set that is of a lower technology level will likely be weighted towards the lower technology level.


As you don't have an AMD system, you have no definitive way to tell what does or does not happen on an AMD system. You cannot infer that because your Intel system doesn't see any difference that all processors wouldn't see a difference. You cannot rely on reports back from users for BETA053A, as again, the performance in a mixed environment would likely be weighted towards the lower technology level - the "lowest common denominator".

I know you're busy, and I'm sure you want to focus on revenue-generating / competing feature activities, but could you please just let me and those of us on AMD systems *TRY* what I suggested? I mean make a serious and genuine effort to make sure that SSE3 gets utilized? In fact, even if SSE2 gets utilized.

If it doesn't help at all, then the subject can be dropped, but it needs to be a serious effort, not a mixed-case situation.

Wow, I can not wait to try them

_________________
by GAP
"Less is More" (Bob Katz)

BETA054:
Stand alone: http://www.stereotool.com/download/ster ... 04-054.exe
Winamp DSP: http://www.stereotool.com/download/dsp_ ... 04-054.exe
VST: http://www.stereotool.com/download/vst_ ... 04-054.dll

Please read my previous post (3 posts up) for some notes about important changes in this version!

SKIPPING:
- Show 1 or 2 AGC bands in bottom meters is 1 or 2 used. -> Annoying side effects, not going to do this now.

DONE:
- I think I should probably remove the 'Use side chain' button, to make it work the same as all other side chains.
- I think I need to put the top line of Multiband sliders (which are very small) in a separate page.
- Add hold multiplier; in Simple mode replace all multipliers by one.
- And change the scale of the Drive slider indeed. -> Probably affects ALL sliders with values in dB's!
- Compressor: Fix stereo separation in Peak mode
- Multiband Compressor: Display coupled bands - Done, but without coupling is no longer visible!
- Multiband Compressor: Median displays (new MB only)
- Remove "blob" from Knee
- Equalizer: More resolution for lower bands - Twice as steep allowed now. #define peq_steep.
- Sound cards: Make 'Synchronize to output' work with Normal output To be tested; might crash/hang
- Check Wunjo's issue with BETA053 (very likely either a memory alignment or a too-aggressive-optimization problem). Appears to be in the "Knee" code. (Error in LUT?)

TO BE DONE:
- Multiband: Call Median Reset when loading a preset or hitting Reset
- Multiband: Optimize Median calculation (less frequent updates)
- Compressor side chain causes volume jumps (block overlap issue). -> Unable to reproduce... But this is scary! Earlier I also saw bad things happening to the 2nd channel. That's also gone now.
- Median display issue Probably fixed... But I haven't seen it happen yet so I'm not sure.
- Allow saving new MB / SB settings
- Hosts issue
- Weird spikes in signal when using Synchronize option for FM in stand alone version (DJ DOGGY) Appears to be fixed now, waiting for feedback (since it seems to cause different issues for different people/OS's/pc's/...?)
- Still silence using Synchronize option to normal output (?) Unable to reproduce, expect this to be fixed, waiting for feedback
- Crash reported by Christian Steifen: If you change to a different category and quickly change something it crashes (VST version). Unable to reproduce, waiting for feedback - was this with BETA054?
- Check new MB limiters and compressors: Optimize to reduce low frequency artifacts.
- Multiband compressor: Differentiate between Basic/Advanced/Extreme... modes
- Singleband Compressor: Differentiate between Basic/Advanced/Extreme... modes
- Some default logical Band crossover settings for MB (every number of bands)
- Update presets
- Change version number
- Release