ok, I'm pretty sure at least one aspect of the issue involves the Reverb, as toggling it on/off seems to trigger the signal burst issue.Charlatan3 appears to crash my DAW if left running for a long time (4-8 hours). I reproduced it three times so far.
Win10 using FL Studio 12. Ryzen 5600x CPU.
I basically left a MIDI sequence playing on loop using a modified LA 2019 patch, with some automation clips being applied.
Could be some sort of timer overflow in memory or something.
Some notes
- GUI does not have to be active (third try had GUI closed), so must be the audio thread.
- I also encountered an issue where returning to Charlatan3 after 2-3 hours of silence caused a 'signal burst', causing some weird DC offset issue - my DAW was reporting 100% volume and clipping but there was no sound. Changing patch and attempting to play a note would cause another signal burst, after I used the "panic" feature to stop all audio, so I had no choice but to reload the plugin entirely to stop the issue.
Video (right click - open in new tab): https://github-production-user-asset-62 ... 61528b.mp4
So basically, if Charlatan3 is open too long, the Reverb breaks somehow.

