Tarik

When I set multiple textures on jit.gl.slab, with "texture " they get forgotten the moment it receives an input "jit_gl_texture " message...

which is a shame because I'd like to set my textures without immediately having the slab calculate the result (as it does upon receiving jit_gl_texture).

Now I'm using the workaround to first set thru and enabled to 0, send a jit_gl_texture message, and set them to 1 again. I'd like to be less hacky though..!

am i missing something or is this a bug? (see example below)

When I set multiple textures on jit.gl.slab, with "texture " they get forgotten the moment it receives an input "jit_gl_texture " message...
which is a shame because I'd like to set my textures without immediately having the slab calculate the result (as it does upon receiving jit_gl_texture).

am i missing something or is this a bug? (see example below)


jit-gl-slab-doesnt-remember-textures-bug

Hi Tarik. Hmm, I often use jit.gl.slab/pix @thru 0 for this and send a bang when I want it to calculate/output a texture. So far haven't had any problem. I might be misunderstanding the context for your problem though.

Well its a bit of a hassle to disentangle my whole chain of interconnected slabs and send them individual bangs when needed. Nothing that can't be done though. It does seem like a small bug though and therefore something that might need some solving

Hi!
Well its a bit of a hassle to disentangle my whole chain of interconnected slabs and send them individual bangs when needed. Nothing that can't be done though. It does seem like a small bug though and therefore something that might need some solving

oh btw... does a 'thru 0' message also prevent the slab from doing any calculations when it receives a jit_gl_texture?

jit.gl.slab doesn't remember textures (bug?)