jit.gl.slab.gauss6x not working. Need desperate help!

    Aug 19 2013 | 10:03 am
    Hi there,
    Any idea why this shader does not work properly? You can check/uncheck the second red toggle to see what happens. I have no clue to why this is not working.
    Thank you for looking into this! ygr
    PS: I also attached the patch with the shader that I found on the forums.

    • Aug 19 2013 | 10:50 am
      You have to make sure that the shader file is in the cycling 74 map. example.
      /Applications/Max 6.1/Cycling '74/Jitter Shaders/downloaded shaders
      If your downloaded shaders/patches aren't in the cycling 74 map then Max won't see them during startup.
    • Aug 19 2013 | 11:06 am
      Thanks for looking into this, Andro
      The thing is that I see the shader. But I am using 2 different slabs via 2 different renders and the first one work ok.
      Only the 2nd one does not work.
      Don't know why. :(
      PS: I see that the shader I am using (cf.gaussian.2p.jxs) comes with the package anyway.
    • Aug 19 2013 | 11:16 am
      Works fine on my system ! I assume the gauss6x is just there to blur the movies right ? When I move the numbers the blur kicks in on both sides. When I use the toggle switch it turns the slab on and off on both sides.
      So whats wrong with the jit.gl.slab then ???
    • Aug 19 2013 | 11:32 am
      On my computer, when I open the patch and toggle main metro, the second video, the one coming from [jit.matrix that2] outputs an overlapped video (It's the video coming from [jit.gl.texture test2 @name mask2] and another instance of it which is rotated 180 degrees)
      If I press the second red toggle, it works just fine, but only without the blur, of course.
      And if I turn it on again via the gate toggle to pass through the blur, I get the original image (countdown.mov), but it accumulates on itself.
      I attached 2 images:
      1. As I start the patch 2. After switchung off and then on the second red toggle
      You say you don't have this problem?
    • Aug 19 2013 | 1:30 pm
      This ones beyond me ! Hope a more advanced user can help you out :)
    • Aug 19 2013 | 2:06 pm
      Don't know why but your patch has made max 6.1.3 crash three times in a row when just checking the master toggle after having created the patch from the clipboard content. Tried to edit the value of the metro not to have its argument set to 0, which is a current crash reason, but that didn't change anything...
    • Aug 19 2013 | 6:25 pm
      i am able to get it to work by re-instantiating the gauss-blur abstraction, after rendering has started.
      i'm not sure what the cause of this is, but the way you're doing this blending is really inefficient. can you describe what your end-goal is, and maybe we can offer some suggestions?
    • Aug 19 2013 | 10:55 pm
      ;)) Yeap. It looks weird to me as well.
      I am trying to blend 4 images together, but in this order. First I need to blend video1 with video2 (which would act as a mask for video1). Then I would blend video3 and video4 (again as a mask for video3). Step 3 would be to blend the 2 images that are the results of the first 2 steps.
      Does it make sense? :)
      I would use this technique to mix 2 kinect masks to 2 videos and in the end, mix the 2 resulting images.
      Thank you all for looking into this!
    • Aug 19 2013 | 10:57 pm
      For mixing 2 images (one of them being the mask for the other), is it ok to use [jit.op @op *]? It seems to work but maybe this is not a good idea either.
      Both of them would have char 4 640 480 and the video for masking would have black for the masked parts, and white for the visible parts.
    • Aug 20 2013 | 7:05 pm
      you can use jit.gl.pix with a simply multiply for this effect. much easier:
    • Aug 20 2013 | 7:07 pm
      and unless you have a good reason, i would avoid using two render contexts.
    • Aug 21 2013 | 7:04 am
      I was trying to avoid that artifact. I thought it had something to do with playing in the same render context. It seems it didn't as I did get rid of the problem.
      Thank you very much for all your help!!!