effects plugins should run as a separate process to avoid crashes

Registered by ewan colsell on 2013-05-15

mixxx is getting ready to support effects plugins, while this is great news it opens a particularly nasty can of worms.
ladspa/LV2/vst plugins vary greatly in quality and stability.

i'm sure everybody is familiar with the situation in DAW software, where many plugins have use the plugin gui in strange ways and often the DAW program is crashed by badly behaved plugins(or even plugins that use parts of the plugin api that the host DAW hasn't implemented)

running plugins in a separate process in becoming standard pracitice in web browsers, and is being adopted by some DAW software (the much vaunted but still in beta Bitwig DAW come to mind)

although not a simple undertaking, running plugins as a separate process mitigates many problems with plugin development and frees valuble developer time.

Blueprint information

Status:
Not started
Approver:
None
Priority:
Undefined
Drafter:
None
Direction:
Needs approval
Assignee:
None
Definition:
New
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.