The jit.slide reference says:
Given a slide value of 10, the slide up/down value output will only change 1/10th as quickly as the input.
First of all, what does it mean by "1/10th as quickly"? As far as I know, jit.matrix and jit.slide aren't aware of 'time' in that sense. They just send out a frame of video when requested (e.g. by a bang), and the rate of requests could vary from moment to moment. So I'm going to assume that by "quickly", they're talking about the number of frames it takes to reach the desired output.
Here's my theory: say you have a fully red pixel, and you then set that pixel to black. If you were to bang that matrix normally, you'd see that pixel turn to black after one bang. Therefore, if you put that matrix through a slide, with @slide_down 10., I'm assuming it takes 10 bangs/frames for the pixel to fully reach black.
So I put this theory to the test with a patch, pasted below. It actually takes more like 20 bangs to get the pixel from red to black, and likewise from black to red (with @slide_up 10.).
It's not a major problem for me - it still creates the desired effect and looks lovely and smooth when hooked up to a metro object. But I would still like to understand exactly how jit.slide calculates it's output, so I can effectively control the speed at which pixels slide up and down.
Can anyone explain?