Stereo Tool

I have changed the message to:

A piece of audio was ignored due to a timeout. This may have caused an audio glitch.

This may have been caused by a (momentary) spike in CPU usage on your pc.

Hi Hans,

looking at the configuration settings I found this, if I remember correctly, they were all active.

could it affect the problem?


edit : I confirm: by installing the 9.63 the "2nd Force" ticks are off, loading the same preset "all setting - import"

Probably not. The "percentage of time in processing" bars are pretty low. But how many cores does your system have? If you have more threads than cores, that's bad.

i7 3770k
4 core
8 threads

i7 3770k
4 core
8 threads

this is something I never fully understood, please explain to me how it should be set up, for example with systems:

2 cores 4 threads
4 core
4 cores 8 threads
8 cores 16 threads
etc

You can use the "CPU usage" pulldown on the top left, that will show all the settings that make sense for your system and configure it automatically.

With 8 threads, that's enough for what you've configured.

thanks Hans ....

last night I reinstalled 9.63 and this morning I received the error, as mentioned there does not seem to be any audio problems (glitch, pop etc.)

I will monitor live as much as possible, to see if there are any audio interruptions

as I wrote you previously, when I load a preset from version 9.62 "2nd / force" is not checked and it does not save access password

Turning off "force" might actually fix the issue!! I'll check what's wrong with loading/saving that setting.


Edit: Password protection was indeed broken, I've restored the code from version 9.62. I don't see any issues with "Forced".

in my opinion, i would change "quality" to 100%, "display" to 0%, process priority to "high" and keep ST minimized.

BETA007 is posted. Biggest change is that we've updated some code that leads to some small performance improvements, especially on ARM (MicroMPX using V4 is 3.4% lighter than before).

Regarding Bypass mode: does this still bypass the Low Input Level Correction or the Output level in the plugin menu? Would that be a reasonable thing to add an exception to?

What about in the new GUI having a Bypass Processing button that's separate from the current implementation (Bypass All)? This would keep things like static level corrections enabled for quick A/B-ing how a preset would sound compared to level-corrected unprocessed audio. It would also be nice for things like the ITU 1770 loudness meter to stay enabled as well in such a Bypass Processing mode.

Thanks!