RichardKnott

So....taking this from my post on another thread...

Is it possible to have the output of a jit.gl.isosurf object, and a separate output of jit.gl.mesh contained within one jit.gl.render window?

i.e. I have a visualisation from mesh, and a visualisation from isosurf, and wish to somehow layer them together, but without one affecting the other.

I realise that @layer should work, but on which object should layer be used, and how?

Everything else I can seem to get around but this!

Is it possible to have the output of a jit.gl.isosurf object, and a separate output of jit.gl.mesh contained within one jit.gl.render window?
i.e. I have a visualisation from mesh, and a visualisation from isosurf, and wish to somehow layer them together, but without one affecting the other.
I realise that @layer should work, but on which object should layer be used, and how?
Everything else I can seem to get around but this!

layering-multiple-opengl-outputs

All that's really neccesary is to render the jit.gl objects to the same named jit.gl.render. In this example I've literally combined the jit.gl.isosurf and jit.gl.mesh helpfiles. 

And regarding layer, you give the @layer attribute to each openGL object that appears in your renderer (isosurf and mesh) with the attribute argument you set which layer you want the objects to draw on (think of it like photoshop layers). I believe the higher the number the further back the object is, so object with @layer 2 is drawn in front of @layer 3.

Could be reversed but the same idea is there. Or think of it like z-index in css?

And regarding layer, you give the @layer attribute to each openGL object that appears in your renderer (isosurf and mesh) with the attribute argument you set which layer you want the objects to draw on (think of it like photoshop layers).  I believe the higher the number the further back the object is, so object with @layer 2 is drawn in front of @layer 3.

Could be reversed but the same idea is there.  Or think of it like z-index in css?


If you want to layer them as if they were "video," rather than objects in 3d space, you can capture the output of a gl object to a texture, slap that texture onto a videoplane, and treat it as a 2d image that can be blended with other textures. For example, you would need to have your objects like this:

jit.gl.isosurf foo @capture isosurf_texture

jit.gl.videoplane foo @texture isosurf_texture @blend_enable 1 @blend_mode 6 7 @transform_reset 2

So instead of seeing the isosurf stuff in the render context as a 3d object, it's getting drawn to the videoplane.

If you want to layer them as if they were "video," rather than objects in 3d space, you can capture the output of a gl object to a texture, slap that texture onto a videoplane, and treat it as a 2d image that can be blended with other textures. For example, you would need to have your objects like this:
jit.gl.isosurf foo @capture isosurf_texture
jit.gl.texture foo @name isosurf_texture
jit.gl.videoplane foo @texture isosurf_texture @blend_enable 1 @blend_mode 6 7  @transform_reset 2

So instead of seeing the isosurf stuff in the render context as a 3d object, it's getting drawn to the videoplane.


Thank you all. Going to test out now. Results to follow...

I still can't get my head around this...please can one of you show me where I'm going wrong?

I want to be able to take the output of the jit.matrix (i.e. what would appear in the jit.pwindow or jit.window if jit.matrix was connected directly to it), but turn it into a texture as described in pnyboer's post, so that the process may be repeated with other matrix outputs, layered on top of each other in the same jit.window.

Apologies for the repetition, but it's just going over my head.

I still can't get my head around this...please can one of you show me where I'm going wrong?
I want to be able to take the output of the jit.matrix (i.e. what would appear in the jit.pwindow or jit.window if jit.matrix was connected directly to it), but turn it into a texture as described in pnyboer's post, so that the process may be repeated with other matrix outputs, layered on top of each other in the same jit.window.
Apologies for the repetition, but it's just going over my head.

Hi there, I really can't wrap my brain around what you are asking for this morning (brain is foggy) but I've fiddled with things so you can try and sort out what you are doing.

1. you can't do without a jit.gl.render, that's what makes the magic happen.

2. you can recapture the output of jit.gl.render using jit.gl.asyncread (careful, it'll slow down your patch).

1. you can't do without a jit.gl.render, that's what makes the magic happen.
2. you can recapture the output of jit.gl.render using jit.gl.asyncread (careful, it'll slow down your patch).


Ah, I understand what you mean now. However, I should have been more clear in what I meant. Further apologies for this, but to clarify, what I really needed to know was the following: -

How, in this patch, could I make the contents of "window2" appear on top of, or blend in with "window"?

I have tried altering @bend_enable, which does essentially do the trick as eventually both appear in the same window when the output is properly specified, however as the geometry output into "window2" requires constant erasure and re-drawing of frames, it interrupts the output of the other display from "window".

I hope this makes sense, and I'm not just doing something incredibly stupid!

(In this patch you simply need to select a sound source, press DSP Start, and slide the gain up, to get going)

Ah, I understand what you mean now. However, I should have been more clear in what I meant. Further apologies for this, but to clarify, what I really needed to know was the following: -
How, in this patch, could I make the contents of "window2" appear on top of, or blend in with "window"?
I have tried altering @bend_enable, which does essentially do the trick as eventually both appear in the same window when the output is properly specified, however as the geometry output into "window2" requires constant erasure and re-drawing of frames, it interrupts the output of the other display from "window".
I hope this makes sense, and I'm not just doing something incredibly stupid!

(In this patch you simply need to select a sound source, press DSP Start, and slide the gain up, to get going)


Ah! I understand. Okay and yes, I understand the problem. No it's not stupid, but you should be spending more time looking at how the render context works. Hope I can point you in the right direction and nudge you into being a little more careful about what you are copying into your patch.

Here's the deal. You shouldn't be sending two renderers to the same window. What'll screw you up is the order of drawing operations, so yes, two erases will conflict. Then you have blend_enable 1 and blend_enable 0. Bad mix. You are also using transform_reset 2 which is making one of the objects dissappear behind the other (simplistically transform_reset 2 means draw everything then redraw this object in it's initial position). Remember just because you can't see it, doesn't mean it's not there.

I deleted a lot of extraneous objects and attributes. Compare the patch below to your old patch and see the difference? But from now on Use ONE render context, one metro, one window, and make sure you are drawing things in the right order. BETWEEN the first erase output by trigger (remember trigger fires right to left) and the last bang you send to jit.gl.render.

But you are on the right track, so hopefully this helps.

Ah!  I understand.  Okay and yes, I understand the problem.  No it's not stupid, but you should be spending more time looking at how the render context works.  Hope I can point you in the right direction and nudge you into being a little more careful about what you are copying into your patch.

Here's the deal.  You shouldn't be sending two renderers to the same window.  What'll screw you up is the order of drawing operations, so yes, two erases will conflict.  Then you have blend_enable 1 and blend_enable 0.  Bad mix.  You are also using transform_reset 2 which is making one of the objects dissappear behind the other (simplistically transform_reset 2 means draw everything then redraw this object in it's initial position).  Remember just because you can't see it, doesn't mean it's not there.

I deleted a lot of extraneous objects and attributes.  Compare the patch below to your old patch and see the difference?  But from now on Use ONE render context, one metro, one window, and make sure you are drawing things in the right order.  BETWEEN the first erase output by trigger (remember trigger fires right to left) and the last bang you send to jit.gl.render.

But you are on the right track, so hopefully this helps.


You Sir, are a life-saver. I cannot thank you enough.

Layering multiple openGL outputs