Damn. My guess is that this happens once you load an image in the meantime? Because that’s the on place where that error is generated. I’ll have a look at this again. The difference in how image/video textures are accessed (see here) makes all this shader logic more annoying that it should me.