I encountered an issue of there occasionally having a bitcrushing effect being applied, even when there are no effect boxes on the desktop, it can be found recorded externally here (https://www.audiotool.com/track/2q1ogm15/), I believe it happens when the audio engine is overloaded, but I could be wrong on that.
Comments (4)
Do other programs have this problem as well while you're experiencing this in AT?
I have a similar issue sometimes, but the cause lies within my audio driver (on Linux Mint).
Otherwise: does Stop/Play make the problem go away? Or do you have to restart the studio? Is the clipping-LED on StereoOutput on? Does the activation of the limiter solve the problem?
Is this always reproducible with the same track? Can you share a link to your draft?
Sorry - I missed your track link in the description.
Your track is heavily clipping and you don't use the limiter in the StereoOutput. The sound driver is free in its decision on how to react in those cases.
You're using several audio loops which is highly NOT recommended because this may lead to undefined behavior. In your case it even seems to produce a DC-offset which pushed the values out of the valid range. Your audio hardware cannot cope with this.
You might want to add a high-pass filter set to a low frequency and a limiter to protect your audio driver.
But I still recommend to refrain from using loops in your setup. The new engine will most likely allow them.
I'm going to close this.