Stereo Tool

Not yet. I can restore the old code (but then it hangs in mAir something), there's definitely something wrong but I haven't looked into it yet.

VST is not so important for me.
I have a free DSPtoVST adapter/wrapper (a VST plugin to load winamp DSPs), but I cannot remember where I have found this.

But I have a little wish for an extra option (key) inside the dsp_stereo_tool.ini.
An extra key like "Recent File Amount=".
The default of ten entries in menu is already good.
But sometimes I would like more recent presets at hand to better trace the evolution of preset development.

Or is this option already inside the ini and I have overlooked it ?

And another odd idea (for Stereo Tool V6 ):
An option ("load" button) in every section to load only the part of a STS file for the specific section.
This would help to combine presets from different users.
Until now I use as a workaround a screen capture tool and copy manually some settings of other users to my own presets.

Nothing interesting: I cleaned up some code and now I can build Stereo Tool also with GCC. This also means that I had to remove all the MFC (Microsoft Foundation Classes, an annoying very incompatible Windows GUI programming layer that can only be built using Microsoft's own compiler and the Intel compiler, not with GCC) from the code. Unfortunately some things work slightly less well without MFC, so the current 'normal' (non-GCC) build still uses MFC. (For example, without MFC the Stereo Tool icon on the left top of the window appears in the windows only after the mouse has moved over the window, with MFC the correct icon is immediately displayed).

The good news here is that most of the Windows-specific stuff is gone (or at least can be turned off), all that remains is the GUI description (where the buttons are placed) and some functions that can easily be patched to use in other OS's.

Also, not including MFC makes the executable a bit smaller (not much, about 30 kB). In a future step I want to fix the few issues that remain in the non-MFC version and remove MFC altogether.

The version I'm posting now should be completely identical in behavior to the previous BETA version. Just with a bit cleaner code.

(I've done this to check the performance in GCC, and to enable future conversions to other OS's. Unfortunately, the GCC performance is a lot worse than the current performance, so for the Windows version I won't change anything.)

Winamp DSP plugin: http://www.stereotool.com/download/dsp_ ... 510-28.exe
Stand alone version: http://www.stereotool.com/download/ster ... 510-28.exe
VST version: http://www.stereotool.com/download/vst_ ... 510-28.dll
VST version (No SSE2): http://www.stereotool.com/download/vst_ ... 510-28.dll
Command line version: http://www.stereotool.com/download/ster ... 510-28.exe
Linux command line version: http://www.stereotool.com/download/ster ... BETA510-28


Just for info: I've also managed to get this thing building with Winelib, but if I run it it crashes immediately.

Michi: I've copied your post to the 'Wish list' forum. Ideas are very good (well at least the one about partial presets), but I'm not going to (be able to) do that in version 5.10.

... Yeah for me beta25 is doing very well , no kidding
this program is going better and better ... thanks to Hans and testers too .

But I say once more to think about it Digital section in StereoTool . This would be greatest radio station in the world ... think about it ( Analog FM in the air , Network stream ready and why not digital in the air , all in one I mean really ALL IN ONE station , all possible way to transmit radio . PCI devices are ready to do the digital signal for amplification and are not very expensive . So if we have a computer , we have multifunctional Radio station . Here in Bulgaria the digital is ready to go . And why not Hans to do your job and take your part of the treasure ( you know they say : greater is great ... money is money when they are a lot of ). All i say is that i notice a greater and greater job around this program , Keep up the good work and hope we help make it even better. If you wish , I`m here.

And two things ... if You notice in only deep bass played by stereo tool little ... ammm .. "flop flop" sound ... i don`t know it depends on sometning to be there ... may be the kind of bass .. i don`t know in some songs this "flop" is much , in some songs not present , in some songs repeats in 2-3 seconds or more ... different. Second is the clock send per minute .. I`m not able to show the right clock on receiver even i change the time zone on computer .So my suggestion is to make clock with menu of time zone because in my stereo tool shows +03:00 , i don`t know from where ( I`m in zone +02:00) and when clock is real 12:00 , on receiver shows 15:00 ?!?!? lots of experiments and no success to show the real clock and same in receiver...Why? there is difference all the experiments



And for the record i must say that I wish to come to Holland and take little talk with you , but for now it`s hard to do this

Nice to see gcc builds.. but just a word of warning: GCC has a habit of being a poor performer on windows (as you found out) and it also has a "masking" effect on bugs (usually stack overflows/corruption) that would otherwise crash an msvc build. So I recommend sticking to msvc or other compilers rather than gcc for debugging purposes (unless you are on a linux or bsd based os for that case there is no option but gcc + gdb)

I know this as I am also a developer too (not just a radio tech

Yeah I did

About hiding bugs: I'm currently using the Intel C++ Compiler (which generates much better optimized code than MSVC); after trying to compile in GCC I did find a number of instances where I used the wrong type for a variable or return value - strangely this was hidden in Windows, not in GCC (on Linux with WineLib; in Windows MinGW's GCC didn't complain).

The files I uploaded are NOT built with GCC, because their performance is just too bad, the only change here is that the code is updated so now it builds in GCC. I'm still posting the Intel Compiler builds.

Hans, a little adjustment on the poppy preset (on the bass low end). Have a nice weekend!

This update ONLY affects the COMMAND LINE version (Windows and Linux).

- Added '-p | --preset' option to select one of the built-in presets from the command line (use -p with no arguments to see the list of presets).
- Added '-x | --export' option to write the current settings to an STS file. Useful to get a settings file without the need to run the Windows GUI version, as a starting point for editing the preset file manually.

Winamp DSP plugin: http://www.stereotool.com/download/dsp_ ... 510-29.exe
Stand alone version: http://www.stereotool.com/download/ster ... 510-29.exe
VST version: http://www.stereotool.com/download/vst_ ... 510-29.dll
VST version (No SSE2): http://www.stereotool.com/download/vst_ ... 510-29.dll
Command line version: http://www.stereotool.com/download/ster ... 510-29.exe
Linux command line version: http://www.stereotool.com/download/ster ... BETA510-29

Hans I found something strange You must check that
It`s about the HARD LIMIT
In version 4.22 hard limit do his job but the sound is not that affected when turn it on ( the job is more.. "backgrounded" like they say.. but in 5.02 this hard limit is saturated the sound .. work so "visible" , sound affected and from 5-6 KHz and above there is big difference with and without hard limit . In 4.22 this difference is not that big (noticeable) .. I mean that i test with one and same song both versions. But in both versions MPXTool not detect even at "instant response" any peaks ..... with hard limit option . In loudness (let`s say little 1.40) option when turn it on i found that there is a kind of limitation like (not the same) "hard limit". This limitation is good but not at the "Hard limit" level of limitation . Hard limit is limiting at the right level but very fast and affects the sound . From where is that big difference between versions (Any latency for this hard limit or something .. ( i guess it`s about time for "look ahead" is very small ) You must say what is the problem. May be the answer is to make the "Hard limit" adjustable - Latency (time to look ahead from 5ms to 2s ) , level to "hard limit" ( I mean limit after pre-emphasis like in LOUDNESS from -5 to +20 db) will be very cool. This options will help to set the perfect and strong modulation for transmitter and receiver deviation.