Stereo Tool

@Luke: Not really an option. Because the idea was that countries each used a different code, but in practice many stations use very different codes.

I found a few interesting links:
http://www.w9wi.com/articles/rdsreverse.htm - PI calculator for the US! Apparently there it's regulated such that the PI code is based on the station name!
http://radio-tv-nederland.nl/rds/rds.html - A list of Dutch radio stations' PI codes. No clear use of a country code here either.

If i remember correctly the country option is in http://www.diffusionsoftware.com/airomate.php
Yes: PI and ECC can be selected by country from a list.

These tests are with the DSP version and Winamp. With all of the tests, the vast majority of the CPU % was noted as coming from the in_mp3.dll instantiated thread of dsp_stereo_tool.dll.

Also, note that by "Multiband ON", I'm meaning just loading my standard preset with everything I normally have on. What I normally have on is:

Stereo Image: Azimuth correction and Stereo Boost (without the reverb option)
AGC (3-band, no bass AGC)
Multiband
Bass Boost
Noise Gate
Bandpass (Phase Linear Highpass, both options checked)
Singleband limiter
Final Limiter's volume increase
Loudness (Dirty bass, Improved Bass, Strict, Deep Bass, deesser, no AEHP, CPU shortcuts checked)
Hard Limit

4096 samples:

Normal Preset with GUI UP = 56-65%
Normal Preset with GUI in System Tray = 43-52%

Multiband ON with AGC off and GUI UP = 43 - 55%
Multiband ON with AGC off and GUI in System Tray = 36-40%

Multiband OFF with GUI UP = 32-38%
Multiband OFF with GUI in System Tray = same

Multiband and AGC OFF = 34-38% (no change in GUI UP vs. Tray)

2048 samples:

Normal Preset with GUI UP = 55-62%
Normal Preset with GUI in System Tray = 15-22%

The other tests show similar reductions, with the final test of AGC OFF and Multiband OFF = 8-12%, GUI UP or in Tray

Per our PM discussion, you felt the data collection routines for the GUI updating could be expensive. I'd suggest looking into that, as the most significant reduction was when I lowered the number of samples AND put the GUI to the tray.

Wow, now that is just crazy. Talk about all the agreements that were made thrown away and ignored by even official radiostations.
It's like the PS that should have been a fixed code to keep the driver of the car focusing on the road instead of the radio.

I should check my documents, if I still have them after .... what 18 years (djeeeeeez). I think I made a list somewhere of all the countries and the types.

Aha, that was it ECC

ECC - Extended Country Code: RDS uses its own country codes. The first most significant bits of the PI code carry the RDS country code. Their four bit coding structure only permits the definition of 15 different codes, 1 to F (hex). Since there are much more countries to be identified, some countries have to share the same code which does not permit unique identification. Hence there is the need to use the Extended Country Code. The ECC consists of eight bits.

Wooh! Now that's a BIG difference. And on my system there is nearly no difference at all (all the different latencies use the same amount of processing +/- 5% or so).

Just to make sure that this is not one of these Task Manager issues: Could you try the following?

1. In Winamp, select output to disk (I think it's called out_wav.dll, you could also use out_mp3.dll).
2. Then let Winamp run for a minute and check how much data it has processed.

This gives much more reliable numbers.

Could you also check this at latency 1024?

Like I said, on my PC I don't see anything like this _AT ALL_ so, this could really be the explanation of the performance issues on AMD's.

I`m sorry but i`m with AMD too and no differences like that
like Hans said just arround 5%

It is very important for you to state your EXACT processor, as if you have Phenom (K10 architecture), you have a shared 2MB L3 cache, and if you have a newer Phenom II (also K10, but with changes), you have a shared 6MB L3 cache, while K8-based AMDs, like what I have, only have a maximum of 1MB L2 cache per core and no L3 cache.

I'll do comparisons later today. I have to take care of some real life stuff for a while... BTW, yes, I was a bit extra-grumpy over the addition / change of the GUI displaying the ligher shading (amplification values) because of knowing about this GUI up vs. tray issue... The increase in load from BETA120 to 123 was 3-5% (absolute value of increase, not delta... the delta from 120 to 123 would be +5% to +10%) at 4096 samples.

@Brian: It gets weirder and weirder. Actually I had expected a VERY small CPU load increase from the voice protection filter in Multiband - but that was finished already before BETA120. So then it must be the band 1+2 link code - that does almost nothing (but almost probably isn't "nothing" enough). Will check if I can improve it; I hope that I'll be able to see the same performance difference.

The new display should not really make any difference for the performance - but the band 1+2 lock might. (I use some extra data for it. Only a few single values, but it might just be too much).