Up till now vmodsynth was developed with no clean memory management in mind. This may cause memory leaks, may lead to occasional crashes. It's high time this got fixed. That requires careful profiling (valgrind?) and examining how data structures are managed (how about using shared_ptrs?). This would get rid of these occasional SIGSEGVs.
Also increasing quality level will serve as a good motivation to keep it that high in the future.
Up till now vmodsynth was developed with no clean memory management in mind. This may cause memory leaks, may lead to occasional crashes. It's high time this got fixed. That requires careful profiling (valgrind?) and examining how data structures are managed (how about using shared_ptrs?). This would get rid of these occasional SIGSEGVs. Also increasing quality level will serve as a good motivation to keep it that high in the future.