Stereo Tool

In other news: I quit my job today.

What will be your plans?

??????

Lets makes things better? --> btw was this also printed on the scanners?
Depending on how you look at it
1) ok the machine cares about me
2) djeeeeeez what is meant by that? that it still doesn't work as it should?

What are you going to do Hans?

That was earlier, now it's sense and simplicity. But simplicity will not always mean better unfortunately.

I had mentioned to Hans a few days (a week?) ago that when Winamp runs, I see 3 total dsp_stereo_tool.dll threads. There might be more, but the tools I'm using are either not as in depth as, for instance, BMC AppSight Application Problem Resolution ... http://www.bmc.com/products/product-lis ... t_appsight , or I'm just not fast enough to see the others.

I've used AppSight when it was the product of Identify software, before it was acquired by BMC. One thing that it showed my former employer is that the software in use was doing way too many I/O (memory) operations.

At any rate, 2 threads are instantiated by winamp.exe. I think one is the the blind interface, and the other is what I think Hans has called the GUI updater. The other instance is created by in_mp3.dll, and that's where the bulk of the processing happens. Inside that instance, and Hans can correct me if I'm wrong here, but in that instance is where the data collection routines for updating the GUI reside. AppSight and the symbolic debug files could tell me for sure, but I'm thinking Hans isn't going to distribute the PDBs, not to mention I'm so poor that I can't pay attention, much less buy AppSight, Intel IPP, Intel compiler, an IDE, and whatever else is needed.

Weary resignation ^

There should be 3 threads:
- 1 that does most of the processing, started by Winamp. Could very well be the in_mp3 thread.
- 1 that does some extra processing, by now that's mainly for FM transmitters, and GUI data collection. Does noting if you do not select multiple cores in the stand alone GUI, or if there is only one core in the system.
- 1 that updates the GUI.

Brian, since you didn't see any throughput differences with GUI enabled/disabled, I don't think the GUI data collection code has any significant effect on the performance (it could affect the CPU load though, although I would not expect any major difference).

Gefeliciteerd! (Congratulations!)

The bulk of the CPU load is always from the in_mp3 instantiated thread. The other two threads, well, I can terminate one of the threads and notice no change at all, while terminating the other stops the GUI, but the audio keeps going.

I appreciate that advances often require more processing power, and you've come quite a way with improving things, given that it got to a point that even newer processors (Intel i and AMD Phenom II) were seeing sluggishness.

You've mentioned the strict clipping and AEHP. I don't use AEHP, so that's not what impacts me, although it might impact others.

...and I have no idea on whether to congratulate you on the quitting of a job or to give my condolences. If you quit because you're making enough money through this, then that's awesome. I wish that I could be my own boss / have my own product...at least if I / it was successful. You're not in the US, but at any rate, I despise corporate America. Getting a job is tough, and keeping it can also be tough, as people who are already relatively well off desire to continue to be well off and ship jobs out of the country to maintain their standard of living, regardless of the impact on those that they kick to the curb...

^ Frustrated and weary resignation...

In last minutes 'maybe', may i as for up to 500% of "Boost Strength" in Bass Boost filter

Post 2000! (of this thread )

So let me post two things here:
http://uden.kliknieuws.nl/nieuws/128952 ... eenfabriek
http://www.youtube.com/watch?v=bMve0i-hFE0

Translation (pretty bad...) of the first link here: http://translate.google.com/translate?s ... eenfabriek