Issues with

    Feb 13 2012 | 6:32 pm
    Hi guys, I'm trying to make a live video processing patch for my wife. I'm basing it on the patch from this tutorial: ""
    The problem I'm having is adding my own modules as whenever I put something new in I just get a black screen.
    For example I wanted to replace the GL x.fade shader " mod @file co.normal.jxs" with a x.fade built in (using the [switch] object). This simply returns a black screen.
    The same happens with my RGB balancer and the 'bleach' shader from the examples folder.
    Most of the patches work in jit.pix if I implement them before any GL stuff however.
    I've pieced together a quick patch to show this:
    Any ideas on what might be going wrong? I'm new to this whole GL optimisation thing and need some help getting my head around it.

    • Feb 13 2012 | 7:03 pm
      Ok, the issue here is with the implicit context stuff not If you see issues like this that don't make sense with, send a message "getdrawto" to and look at the result coming out of the dumpout (far right outlet). In this case, didn't find an implicit context because your jit.window object is in a subpatcher. Since contexts can also be attached to jit.pwindows, the finds the jit.pwindow and thinks it's a context.
      There are two solutions to this problem:
      1) put jit.window in the same patch level as or any other implicitly attached object 2) assign the context name explicitly
    • Feb 13 2012 | 8:11 pm
      I see. So I would put for example [ @drawto blargh]
      I've implemented this in the patch bellow but I still seem to get a blank screen.
      Thanks for your help by the way.
    • Feb 13 2012 | 8:16 pm
      Yes, or simply [ blargh]. If you close and reopen the patch after making this change does it work? It does for me.
    • Feb 13 2012 | 8:29 pm
      Aha, that worked! Thanks very much. Is this sort of thing in the documentation or assumed knowledge?
    • Feb 13 2012 | 8:51 pm
      Your patch should work without having to close and reopen. I've filed a bug report to look at so we can fix that problem. The implicit context stuff isn't documented. We're working on some updated jitter docs that will have all of this info in it though. In the meantime, here's how it works:
      If you create a object without an explicit context name, it will do the following to find a context:
      1) look for a jit.window object in the same patch 2) look for a jit.pwindow object in the same patch 3) if it hasn't found any, it will look in the parent patch if it exists and start again at step 1