Fade to white


    Feb 13 2006 | 3:39 pm
    Hi, I'm using the following patch to create a video feedback that fade to white. However, the fade is much too fast. I'd like it to last around 60 seconds. Does anyone has a clue how to make the fade slower?
    Best regards,

    • Feb 13 2006 | 4:05 pm
      If you don't want feedback to blow up on you, then you need a delay. TapTools has a delay object. You can use a 3dbuffer a la xray.jit.3dbuffer, uoi can use a matrixset...
      wes
    • Feb 13 2006 | 4:14 pm
      use jit.op + instead of jit.op * to ADD the feedback to the input instead of multiplying it, then control the feedback path with a * so you only add a really small part of the feedback matrix. The speed at which you fade to white will also depend on your framerate of course.
      hth, T_
    • Feb 13 2006 | 4:15 pm
      does this help?
    • Feb 13 2006 | 7:06 pm
      Thanks for the answer. However, I want a continuous feedback the way a delay works with audio. My patch is already working except that the fade is too fast. Probably slowing the FPS rate would work but since I don't use any QT movie, I don't know how to slow the FPS rate.
    • Feb 13 2006 | 7:09 pm
      did you not see my post about creating a delay line???
      wes
    • Feb 13 2006 | 7:25 pm
      If you mean that you want to set up an Infinite Impulse Response filter, this is how you would do it:
      The jit.op @op * gives you the ability to scale the feedback to prevent it from blowing out too fast.
      Is this what you would like to accomplish? If not, please explain more.
      Cheers, Andrew B.
    • Feb 14 2006 | 6:04 am
      On Feb 13, 2006, at 11:14 AM, Thijs Koerselman wrote:
      > use jit.op + instead of jit.op * to ADD the feedback to the input > instead of multiplying it, then control the feedback path with a * > so you only add a really small part of the feedback matrix. The > speed at which you fade to white will also depend on your framerate > of course.
      You can always just use jit.xfade as well, which has the benefit of being easy and not framerate/feedback dependent. Just move from 0. to 1. over an arbitrary period of time, with the second input being the white matrix.
      - John