geddonn

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:

https://cycling74.com/tutorials/the-video-processing-system-part-4/"

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 "jit.gl.slab mod @file co.normal.jxs" with a x.fade built in jit.gl.pix (using the [switch] object).

The same happens with my jit.gl.pix RGB balancer and the jit.gl.pix '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.

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:
"https://cycling74.com/tutorials/the-video-processing-system-part-4/"

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 "jit.gl.slab mod @file co.normal.jxs" with a x.fade built in jit.gl.pix (using the [switch] object).
This simply returns a black screen.

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.


issues-with-jit-gl-pix

Ok, the issue here is with the implicit context stuff not jit.gl.pix. If you see issues like this that don't make sense with jit.gl.pix, send a message "getdrawto" to jit.gl.pix and look at the result coming out of the dumpout (far right outlet). In this case, jit.gl.pix 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 jit.gl.pix finds the jit.pwindow and thinks it's a context.

1) put jit.window in the same patch level as jit.gl.pix or any other implicitly attached jit.gl object

2) assign jit.gl.pix the context name explicitly

Ok, the issue here is with the implicit context stuff not jit.gl.pix.  If you see issues like this that don't make sense with jit.gl.pix, send a message "getdrawto" to jit.gl.pix and look at the result coming out of the dumpout (far right outlet).  In this case, jit.gl.pix 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 jit.gl.pix finds the jit.pwindow and thinks it's a context.

1) put jit.window in the same patch level as jit.gl.pix or any other implicitly attached jit.gl object
2) assign jit.gl.pix the context name explicitly


I see. So I would put for example [jit.gl.pix @drawto blargh]

I've implemented this in the patch bellow but I still seem to get a blank screen.

Yes, or simply [jit.gl.pix blargh]. If you close and reopen the patch after making this change does it work? It does for me.

Yes, or simply [jit.gl.pix blargh].  If you close and reopen the patch after making this change does it work?  It does for me.


Aha, that worked! Thanks very much. Is this sort of thing in the documentation or assumed knowledge?

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 jit.gl 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

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:

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


Issues with jit.gl.pix