You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
CPU intense calculations like the Wavelet Transformation, especially with higher resolution and filtering requirements, shouldn't affect the audio thread. Currently, glitches and other artifacts might happen occasionally. The audio thread shouldn't be affected by intense calculations, since they are done to visualize the spectrum, not to change audio.
Expected
The audio thread should only be connected to a buffer that doesn't lock it
There shouldn't be any glitches any more
Ideas
Research buffering and thread synchronization best practices
Refactor link between audio thread and spectrum calculation and visualization
Problem
CPU intense calculations like the Wavelet Transformation, especially with higher resolution and filtering requirements, shouldn't affect the audio thread. Currently, glitches and other artifacts might happen occasionally. The audio thread shouldn't be affected by intense calculations, since they are done to visualize the spectrum, not to change audio.
Expected
Ideas
References
The text was updated successfully, but these errors were encountered: