LMMS • Forums

First let me say: I love LMMS. It is (along with Audacity) my DAW of choice: highly functional, intuitive and user-friendly. I have more than 200 VSTi's and a similar number of effects-VSTs, all of which I really like and all of which work perfectly in LMMS. I am very satisfied, and don't really need more than what I have.

However; there are quite a few excellent VSTs which I would love to try out --- both instruments and effects --- but which unfortunately, when loaded into LMMS, immediately cause the VESTIGE plugin to crash (Remote VST Plugin has encountered a problem, and needs to close), which in turn immediately causes LMMS to crash.

I'm not tech-savvy enough to be of much help in the development of LMMS; but I could certainly provide a CrashLog/ErrorText to a developer, if a CrashLog/ErrorText were generated when these and other crashes or other errors occur.

So I think it would be great for the continuing development of LMMS to somehow add a Crash Log feature.

(As a side note: when VESTIGE and LMMS crash, they usually leave open running processes which I can see in my Windows Task Manager, and each of which I have to manually close therein.)

thanks;
Andy

Having better debug symbols in Windows is something we've talked about. Just having the console log would be a big help and Toby once outlined the steps necessary to do that, but basically Windows is different than the rest, so it is a bit of work.

For now, I use Wine to debug Windows issues because I can get much better debug information.

Until this is implemented, we're stuck speculating the Windows side of things, sorry.