plugMain() not called with FF_PROCESSOPENGL
Posted: Thu Oct 10, 2019 06:02
Under what circumstances does Resolume allow the instantiation of an effect (ie it appears in the Effects browser and can be added to a Clip/Layer/Group/Composition) but then not actually call plugMain() with functionCode == FF_PROCESSOPENGL ?
I"m testing a "passthrough" plugin (not intending to modify the contents of the frame) and I was surprised to find that Resolume seems to only be calling plugMain() with functionCode == FF_SET_BEATINFO (after initialisation). In my case, this is actually fine, indeed better than copying the incoming texture, but I don't know why it is happening.
I'm working on narrowing down the problem, but some insight from the Resolume dev side is welcome!
-spxl
I"m testing a "passthrough" plugin (not intending to modify the contents of the frame) and I was surprised to find that Resolume seems to only be calling plugMain() with functionCode == FF_SET_BEATINFO (after initialisation). In my case, this is actually fine, indeed better than copying the incoming texture, but I don't know why it is happening.
I'm working on narrowing down the problem, but some insight from the Resolume dev side is welcome!
-spxl