Read back from an OpenGL framebuffer Uses Pixel Buffer Objects (PBOs) to perform asynchronous reads of the OpenGL context at high framerates. The performance gain comes from using two pixel buffer objects in tandem to amortize the cost of the read operation over time without blocking other rendering commands from executing as is typically the case when naive methods are used. Cycling '74 Jitter Jitter OpenGL messages to this 3d object TEXT_HERE matrix output if enabled Outputs a Jitter matrix equivalent in size to jit.window object it is reading. dumpout Outputs 'get' queries. TEXT_HERE TEXT_HERE Output a copy of the frame buffer Output a copy of the frame buffer (OpenGL render context). The output matrix dimensions adapt to the size of the window. Reading mode Sets the reading mode. The available modes are:

split: Split reads a single frame in two passes and the output is concurrent.
interleaved: Interleaved reads an entire frame into each internal buffer, switching buffers every other frame. In interleaved mode, the readback is delayed for one frame. The internal frame buffer name Returns the name of the internal frame buffer (OpenGL render context). This object requires one argument: the name of a drawing context. A named drawing context is a named instance of a jit.window, jit.pwindow, or jit.matrix object that has an instance of the jit.gl.render object associated with it. Additionally it can reference the name of a jit.gl.node sub-context. This value may also be set via the OB3D drawto attribute. If no argument is present, the object is implicitly added to the first valid drawing context or sub-context found in the current patch or by searching up the patcher hierarchy.