I have recently found a great solution for blending my effects using the MIX module but it has caused FPS drops.. I know if I chained all these effects i get zero FPS drop but when I try and link them all with the mix module, i get FPS drops. Attached is a screeshot of the problem. I am sure there is a simple solution I am just not seeing, I have a work around by powering off the pluging when its not in use but it still seems to have a huge impact on performance.

It could be you're just on the edge. I don't see a frame-rate drop mixing 6 different videos through 5 mix modules on a desktop GTX970 with a few 32-bit FFGLs and a couple of Trails thrown in to try to match your comp.

Can't see what you're doing in those other "CHROMA" scenes but you're probably just stressing your hardware with the mixes. Try turning off your trails - they are notoriously hard on the system. Perhaps try the 64-bit version of Magic? It looks like you're using the Mix modules to bring elements in and out with MIDI. Perhaps there's a better way for you to do this, e.g. Multi-mix or Transparency? The SpoutSender will also put pressure on the system.

I just worked it out. Because the vector is both A and B with the mix module, I can power off the FX when MIX is on A (Bypass) to increase the FPS and if I insert any random module and then POWER it off, it kills the other vector and fixes the FPS. It turns out if mix, even when set to 100% of 1 value, still processes the off value.Also, the chroma select is just 25 image files on a selector so no resource munching in that one. I am aware spout does a small load on the show, but i just cant get my head mix not working as logic gate that fades between A n B inputs. I was using transparency prior the mix but that does not allow me to fade just one module while leaving the others un-faded.

also to note, I am running a GTX1050. I run 32bit for the 32-bit ISF module compatibility.

Glad to hear you've found a solution. You don't have any issues with the modules turning off before the (0.9) smoothing is finished?

This seems like a similar (but opposite) workaround to that of the video module when it's connected to an input selector where connecting it to another (any) module as a keep-alive.

Your issue with the performance hit of the mix module reminded me of the same thing I experienced but with the multimix module. I'd found a nice way to use it and excited began inserting it into every scene but realised there was a performance hit, especially in already heavy scenes and had to be more sparing.