Plug-In Identification in Project Crashes

Max Output Level: -56.5 dBFS
  • Total Posts : 1891
  • Joined: 2012/10/05 21:28:30
  • Status: offline
2016/10/04 14:27:27 (permalink)

Plug-In Identification in Project Crashes

Is there a way Sonar can identify what plug-in caused the DAW to crash while being loaded? For example, I use Drumagog 5 Plat, and it sometimes has been known to crash Sonar (caused, likely by MS Windows Build). When safe-opening a project, it would be cool to not only know up front which plug-in crashes Sonar when loading a project, but perhaps allow the user to "No to All" of a plug-in that has the same name (even if different Instance IDs), but load all the other plug-ins, normally.
In short. Sonar, tell me what plug-in you think crashed us, and let me not load just that plug-in when safe-opening a project.

Sonar Platinum, Steinberg Wavelab Pro 9, MOTU 24CoreIO w/ low-slew OP-AMP mods and BLA external clock, True P8, Audient ASP008, API 512c, Chandler Germ500, Summit 2ba-221, GAP Pre-73, Peluso 22251, Peluso 2247LE, Mackie HR824, Polk Audio SRS-SDA 2.3tl w/upgraded Soniccraft crossovers and Goertz cables, powered by Pass-X350. All wiring Star-Quad XLR or Monster Cable. Power by Monster Power Signature AVS2000 voltage stabilizer and Signature Pro Power 5100 PowerCenter on a 20A isolation shielded circuit.

0 Replies Related Threads

    Jump to:
    © 2023 APG vNext Commercial Version 5.1