Stereo Tool

Asymmetry bug (overshoots in MPX) fixed.

Windows 32 bit:
Windows stand alone: http://www.stereotool.com/download/ster ... 01-009.exe
Winamp DSP: http://www.stereotool.com/download/dsp_ ... 01-009.exe
Windows VST 32 bit: http://www.stereotool.com/download/vst_ ... 01-009.dll

Known issues:
- Low Quality Low Latency monitoring (stand alone version) is disabled for now
- Generic plug-in (not posted) FM output to host doesn't work.
- Memory leaks on close

Have you tried running the new Single Mode Multi Threads model? Turn on advanced tweeker, in CPU turn off multicore and set the threads to the vCPU count that you have. If you running VMware, run up the TST in the VM, and then check the report on the VM for CPU Ready. This is infact a waiting status for underlying CPU resources that VMware kindly named incorrectly to hide CPU starvation.

Let me know how you go.

May i ask something:

Why (the hell) is the need of running ST in VMWARE ?What is the benefit ?
Testing? for what ? I think this kind of program have not any need of running anywhere but only in real machine.
I just don`t see anything more good in running in Virtual machine. Someone can tell me at least two reasons ?

Beta 9 still crashes:

_________________
The Power of Sound

''Music is a moral law. It gives soul to the universe, wings to the mind, flight to the imagination, and charm and gaiety to life and to everything.'' - Plato

I think I just found this one here too, related to having FM options enabled but no sound card selected so the output is at 44 or 48 kHz. Will fix it.

Lots of reasons DJ. In the new AoIP world thats evolving, the use of virtualisation something that we will need to live with. We have already done this with the VoIP work, with Asterisk, CCM and others now working nicely in the VM world.

Down under, our cost of electricity is massive when compared to the rest of the western world, and all attempts to minimise power use is taken, with virtalisation very high on the list.

Others?

saving electricity is not a reason directly connected with ST .

This is the reason to minimize the usage of PCs at all. I just ask for reason ST to run always in Virtual machine - was thinking about this but not found such ones. Also if you want to run "several PCs" in one real - don`t you think that it must be a "super PC" which will still consume energy , equal to more than one ordinary PC . For example - my previous Athlon was 45 W , now if you run some Buldozer at 125 W to be able to handle 2-3 virtual machines... this is 3 chips like mine, man !
So, this reason is kind of "smell" to me. Please, don`t be angry - this is just my opinion.

Do you mean the audacity process or the memory of the vst plugin? By the way the latest beta 9 does not show any screen in audacity. i only see only a grey screen.

here is the memory of audacity after opening a file it has around 9 MB RAM. if i am starting now the stereotool it increases to around 700 MB.

[Probably getting off-topic - apologies].

Electrical costs "down under" is a contributing factor however there is a lot more than that reason alone to review and use virtualisation.
Having a high end machine running a number of tasks means you decrease the server/PC footprint for one plus allows you to move your VMs around when things go bad (hardware) or you need to throw extra resources vCPU/memory towards it.

It also *really* helps to run programs like Stereotool in a testing/UAT machine that will mimic it's targeted production environment. Test, blow the UAT environment away, start again, learn how to get the most out of it - such as integrating third party tools/programs - and you have a great way of controlling your audio and facility destiny.

This is exactly what I have been doing since Hans released his new version (v8.00). We wanted to incorporate AoIP as our proposed default soundcard and found it to be relatively easy until we opted to incorporate FM/MPX output. Several crashes later we now have a stable UAT running ST x64 standalone using Audinate DANTE VIA ASIO and a soundcard in 192k mode for MPX. Challenge was having ST see the DANTE VIA inputs/outputs at 48k sample rate (max for VIA) and maintain a 192k rate for the analog output. Cannot wait for the Tiny/microMPX option to be an option.

Having cleared one hurdle we are now considering creating a VM to allow us to separate our processing for FM and streaming. AoIP allows us to either take it's own desk feed or take the FM output from ST as an option and process it for each pending endpoint whereas before it meant sourcing another machine, space and audio splits/distribution are no longer a factor. On a small budget that most community stations have, even a $300-400 machine becomes an issue. A windows 10 license running in a VM is simply a cheaper and more viable option.

Nothing like having fun though... right?

Rossco

Hans, I appreciate your pithy comments along with the BETAs, so I can judge how much cutting edge I need to be.

That said, I'm running the latest beta (009), stand alone, over the air (LPFM), sounds as stable as 8.00 and 8.01beta001.