paulclift

This is probably a stupid question with an easy fix but I can't figure it out myself..... basically, I have a jit.window with multiple jit.gl objects sending data to it; I want to be able to monitor everything that is sent to it with an in-patch jit.pwindow. How can I do this?

Hello all,
This is probably a stupid question with an easy fix but I can't figure it out myself.....  basically, I have a jit.window with multiple jit.gl objects sending data to it; I want to be able to monitor everything that is sent to it with an in-patch jit.pwindow. How can I do this? 

monitor-an-external-display-jit-window-with-an-in-patch-jit-pwindow

The quickest way is by using jit.gl.asyncread. If realtime performance is of concern you should consider keeping it in the GL realm, though your monitoring window will have to be a jit.window instead of a pwindow.

https://cycling74.com/forums/sharing-triplehead2go-rendering-setup-updated-for-max6-and-jit-gl-node

This could give some inspiration: https://cycling74.com/forums/sharing-triplehead2go-rendering-setup-updated-for-max6-and-jit-gl-node


if performance is an issue and you are on a mac,

you could make a seperate player standalone application and a seperate interface standalone application.

send the player ouput texture with the external "jit.gl.syphonclient.mxo".

receive the texture with the external jit.gl.syphonserver.mxo at your interface application.

this method has a bit overhead, but was the most efficient way i figured out.

also it is not trivial to build a standalone with the syphon externals.

perhaps this will be more comfortable in future versions.

if performance is an issue and you are on a mac,
you could make a seperate player standalone application and a seperate interface standalone application.
(they could communicate via osc)
send the player ouput texture with the external "jit.gl.syphonclient.mxo".
receive the texture with the external jit.gl.syphonserver.mxo  at your interface application.

this method has a bit overhead, but was the most efficient way i figured out.
also it is not trivial to build a standalone with the syphon externals.
perhaps this will be more comfortable in future versions.

Thanks for the responses guys! I have both methods up and running, will see if the payoff for performance is worth it with the standalone.

Monitor an external display jit.window with an in-patch jit.pwindow