Idea for dealing with multicore VST bugs

I'd like to propose a feature to help deal with multiprocessor bugs in VSTs. Why not include an option to restrict all instances of certain VSTs to a single CPU/core? A checkbox for each plugin could be put in the "Rename VST" dialog. For instance, if 3 tracks have an instance of BuggySynthEditEQ, the load balancer should put them all on the same CPU/core, and then even out the rest of the load afterwards. Is this a feasible idea?

+1 if this is possible, it'd be very good. it'd possibly also be nice to have the list of "dodgy" plugins available as a separate file which could be maintained separately from reaper. it'd also be nice if that list knew about other common problems with plugins (e.g. "totally incompatible/generally unstable", "known graphics issues", "needs to render at 1x", "can't handle RAM above 2GB", stuff like that, so that users could be warned if they tried to instantiate one of those plugins in a session). sounds like a lot of work, though.

excellent idea +1 I haven't come across this much, but it sounds like an option worth having.

It should be noted I'm not sure whether this would fix the problem -- all I know is when I set REAPER's affinity to "CPU 0" only, the problems go away. REAPER seems to be perversely multithreaded so there could be other issues at work -- GUI and audio code running in different threads, for example. Cockos can do internal tests to figure this stuff out... I can't. ;) I'm also waiting on the arrival of a router to see if hosting plugs remotely (on a 1-core laptop) fixes any issues. That would be another clue