![]() ![]() Good news! This ^^^^^^^^^^ completely solved the problem! When running DP11 with the -disable_crash_reporter option, All three scans of VST3, VST and AU ran to completion without any crashing at all. I haven't tried it on DP 11, but I know for a fact that it still worked on DP 10.xx Does the Mac console give you a clue? If not, does the crash log go directly to MOTU? Have you tried the Disable Crash Reporter script? Is MOTU getting your crash reports? ![]() I really hate to hear this and wish I could offer a magic bullet. Kontakt vst3 doesn’t pass validation in DP11 by the way, among others I agree with you that DP fails more plugins then some other daws such as logicpro, but all the other daws fail some plugins too once in a while, DP is not alone in that, but it does seem to fail more then the others but hard to prove that fact, but that ha generally been my experience for a long time.īut that is not the main problem here, the main problem is the horrible way DP is handling those failures. I will be trying the console trick later today maybe that will an ok work around. But the problem is also the way DP is keeping an internal list of some kind and keeps attempting to rescan the thing that just crashed, and meanwhile provides inadequate reporting of what just happened. Apple moved their scanning out of process a while back and improved the situation a lot. Yes that is definitely part of the problem. Sure, MOTU doesn't pass every plugin that Logic does - that's arguably a problem - but it could gracefully fail in the worst case. ![]() As long as we're being constructive, has anyone made a feature request to MOTU to take their plugin scanning out of process so that a crashing plugin can't crash the app? Seems like that's the main scanning issue at work here. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |