|
2012-04-03 04:25
|
Screen Shot 2012-04-03 at 2.20.19 PM.png (37,672 bytes) |
|
2012-04-03 04:27
|
|
|
|
As a general thing Ardour should be able to bypass and put "on hold" or even ignore any plugin that has a non normal return state. |
|
|
Summary should have made clear that this crash occurs when Ardour is checking a new AU plugin at startup. Also should add that when plugin is removed (deleted from components) all is well - in other words there is no obvious mess left as a result of the crash. |
|
|
Mac OS X Lion 10.7.3 iMac i3 8GB ram using JackRouter to route audio into ardour interface M-Audio fast track ultra 8R |
|
|
Further investigation shows that it is the plugin that crashes - running the standalone Jupiter-8V2 app exhibits the crash. In other words Ardour is inheriting the crash state. So, not Ardour's problem per se, but none the less would be good to have Ardour isolate plugins in a forked process/new thread to avoid the main Ardour thread crashing with the plugin, at least during the check phase. Not knowing Ardour's architecture, I may be talking trash - but the principle applies. |
|
|
And just to complete the picture - it appears I was trying to run the paid version without the bits it needs rather than the demo - a problem for Arturia to deal with of course. Nonetheless Ardour should protect itself if possible from hosted plugin crashes. |
- Anonymous
