uh, no you launch a thread, track your processing structure externally. using an exception handler when the thread fails you read the call stack and come up with an error message. you re-build the processing structures and launch the thread again, this time with the faulting plugin disabled.tony tony chopper wrote:If you were a programmer you'd know it's impossible.
cubase has done this for years. what are you talking about?
this is a basic feature. come on, pretty much every piece of software using dynamic linkage to untrusted libraries works this way today. see firefox, vlc, countless others.
if you were a programmer you'd already have implemented this.
yes there are some exceptions that can't be handled completely, but they can be protected against. in those cases it's a severe problem, more severe than anything you should attempt to recover from. the process may have walked over memory, in which case you need to write to the log if possible and kill the entire process.
it's just that this rarely happens. most plugin faults cause issues by having access violations or other exceptions that can be caught and dealt with.