plugMain() not called with FF_PROCESSOPENGL

FFGL, OSC, GLSL. If you like abbreviations, this is the forum for you
Post Reply
User avatar
Hasn't felt like this about software in a long time
Posts: 134
Joined: Thu Jun 05, 2014 09:32
Location: Melbourne, AU

plugMain() not called with FF_PROCESSOPENGL

Post by subpixel » 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!


Team Resolume
Posts: 91
Joined: Tue Mar 12, 2013 13:56

Re: plugMain() not called with FF_PROCESSOPENGL

Post by Menno » Thu Oct 17, 2019 16:27

This is not something we have to explicitly allow under once circumstance or another. Plugins aren't provided guarantees that they get a FF_PROCESSOPENGL opcode for every instance that's being created (not even if their initGL was a success).
As a result, plugins need to be sure that they're resilient against any usage deemed necessary by the host application.

Post Reply