I think that is what I want.
I am still trying to understand the jitter pipeline at a fundamental level... and am not quite sure I fully understand contexts and jit.gl.nodes. My basic understanding is that jit.gl.mesh is an OpenGl source that needs and OpenGl target (or context) to render to - and the dimensions of the output is determined by the target (i.e., jit.window).
The part where I get confused is when you add in a jit.gl.node sub-context and on top of that a jit.gl.videoplane rendering of that jit.gl.node.
Ok, that sounds kinda confusing... Here is what I am trying to accomplish. I have a single source of data - that is represented by a jit.gl.mesh. I want to render that data to two separate targets simultaneously. One target is actually a high-resolution jit.gl.syphonserver (which I have connected to a jit.gl.node sub-context). The other target is a low-resolution jit.window (which should be just a small preview of what is being sent to the jit.gl.syphonserver).
I have this working sorta using the following block diagram:
The problem is, the mesh is being rendered at the resolution determined by the jit.gl.node (which in this example is 1920x1080) and is being output to Syphon at this resolution (which is great) - it is also being output the the jit.window - however, the jit.window is a down-sampled view of the jit.gl.videoplane capture of 1920x1080 jit.gl.node. I don't want this.
Is it possible to render to two different resolutions? I basically want to render my jit.mesh to two separate contexts (I think context is the right concept - still not sure exactly what a context is). One giant res to jit.gl.syphonserver and one "preview" size (lets just say 320xsomething of similar aspect) to the jit.window.
I think what I want to do is send the output of the jit.gl.mesh (which I am not sure if this is still a jitter matrix or is now an OpenGl texture...) to two different jit.gl.nodes - each of different sizes - however, I am not sure of the syntax of how to do this using named contexts.
I hope all these questions make sense. If anyone can point me to a document which explains these concepts with nice flow-diagrams and calls out what happens where, that would be awesome. Also, if anyone actually understands what I am trying to accomplish and knows how to accomplish this and can provide some pointers, that would be awesome too!