[LV2] worker thread question
brummer- at web.de
Sat Dec 29 12:16:02 PST 2012
Am 29.12.2012 20:35, schrieb David Robillard:
> As I said, this was tried, and it was much, much more complex and raises
> a massive set of problems for little to no benefit. It is particularly
> tedious to implement on the host side, which is why nobody implemented
> it. Doing I/O in run() is a deliberate design decision arrived at after
> a lot of thought and experimentation. It is this way for good reasons.
> In short, you're breaking very important rules in order to "optimize"
> away nothing significant, with a result that's much more complicated,
> error prone, and slow than the simple and correct solution.
> This code is broken and needs to be fixed. Do not break the threading
> rules of the API. Seriously.
sadly I notice that you didn't understand the need of non-rt dsp
processing with user interaction in a plug-in. To bad :-(
I guess that you makes thinks more complicated then they really are.
That isn't what I understand under a Open spec. Your assumptions leads
to no way for implement what I need to make my plugs work with your
bless, so be it. I have tried to find a way for communication about that
with you, but it seems to me there isn't.
Maybe you tried out my work, before you totally negate it.
That it works stable, have nothing to do with luck.
More information about the Devel