In Part 12 of the "A Few Minutes with BEAP" tutorial series, we look at an unusual source for generating CV for your favorite BEAP modules - video. It's a quick way of adding UI controls to run multiple modules, too.
My first thought would be that perhaps you're running a video that has very little in the way of change in it through the converter - remember that you're taking a grayscale average of ALL the pixels and outputting that average. The big giveaway would be to keep a close eye on the FADR (if you're patching along with the video). If you see very little in the way of movement by the fader, then that's probably the offending beast. Is that the case?