Masa

I find it difficult to fully understand how the naming concept of OpenGl context. I sometimes see that OpenGl objects communicating each other without a code, and sometimes I see they are connected with a cord.

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

, [jit.gl.slab mod] and [jit.gl.videoplane mod] are connected, but they behave in the same way even if I disconnect them.

Could anyone kindly tell me how the naming concept works, as opposed to connecting objects with a code? 

I find it difficult to fully understand how the naming concept of OpenGl context. I sometimes see that OpenGl objects communicating each other without a code, and sometimes I see they are connected with a cord.
For example, in the sample patch from https://cycling74.com/tutorials/the-video-processing-system-part-1/, [jit.gl.slab mod] and [jit.gl.videoplane mod] are connected, but they behave in the same way even if I disconnect them.
Could anyone kindly tell me how the naming concept works, as opposed to connecting objects with a code? 


understanding-opengl-context-naming-concept-as-oppoed-to-connecting-with-a-code

Jit.gl.render nfx draws to jit.window nfx

Jit.gl.node @name node-1 @capture 1 Captures any objects with its target name.

Eg. Jit.gl. Gridmesh node-1 or jit.gl.model node-1.

Jit.gl.node then sends a texture out which can be sent to a jit.gl.videoplane nfx.

Jit.gl.node can capture with a patch cord but this isn't dynamic.

You could setup 2 jit.gl.nodes with different names and send a different shape to each one. They would be separate layers.

Jit.gl.render nfx draws to jit.window nfx
Jit.gl.node @name node-1 @capture 1   Captures any objects with its target name.
Eg. Jit.gl. Gridmesh node-1 or jit.gl.model node-1.
Jit.gl.node then sends a texture out which can be sent to a jit.gl.videoplane nfx.
Jit.gl.node can capture with a patch cord but this isn't dynamic.
Its all about hierarchy.
From top to bottom.
Jit.window
Jit.gl.render
Jit.gl.node
3d objects

You could setup 2 jit.gl.nodes with different names and send a different shape to each one. They would be separate layers.
Hope this helps.


Jit.gl.slab doesn't need a context as it reacts to incoming textures. But the options there to keep things separate. The jit.gl.videoplane dos need a context because its a 3d object displaying a texture.

Jit.gl.camera is also a separate render context if you want it to be.

Jit.gl.slab doesn't need a context as it reacts to incoming textures. But the options there to keep things separate. The jit.gl.videoplane dos need a context because its a 3d object displaying a texture.
Jit.gl.camera is also a separate render context if you want it to be.


Understanding OpenGl context naming concept, as oppoed to connecting with a code