nesa

I'm using jitter 1.6.3b2 and I'm running into strange thing using 

jit.gl.slab, it seems that it has eight input textures(try sending it 'read' 

I'm on windows xp, ati m9700 with not-the-latest-but-quite-fresh omega 

I'm using jitter 1.6.3b2 and I'm running into strange thing using 
jit.gl.slab, it seems that it has eight input textures(try sending it 'read' 
message, you'll get 8 opendialogs).

I'm on windows xp, ati m9700 with not-the-latest-but-quite-fresh omega 
drivers.

eighttuple-input-jit-gl-slab-in-jit1-63b2

i can reproduce this on a similar max install on xp with 6.14.10.9371 nvidia

and i didn't know the [error] object, very useful!

> I'm using jitter 1.6.3b2 and I'm running into strange thing using

> jit.gl.slab, it seems that it has eight input textures(try sending it

> I'm on windows xp, ati m9700 with not-the-latest-but-quite-fresh omega

> #P number 204 110 35 9 0 0 0 152 0 0 0 221 221 221 222 222 222 0 0 0;

> #P newex 32 98 110 9961481 jit.gl.slab out @inputs 1;

> #P newex 32 70 87 9961481 prepend sendinput;

> #P comment 83 46 100 9961481 8 input textures?;

i can reproduce this on a similar max install on xp with 6.14.10.9371 nvidia
driver  9700gs.
btw.
and i didn't know the [error] object, very useful!

On 12/23/06, nesa  wrote:
>
> Hello everyone,
>
> I'm using jitter 1.6.3b2 and I'm running into strange thing using
> jit.gl.slab, it seems that it has eight input textures(try sending it
> 'read'
> message, you'll get 8 opendialogs).
>
> Can anyone else reproduce this?
>
> I'm on windows xp, ati m9700 with not-the-latest-but-quite-fresh omega
> drivers.
>
> #P window setfont Geneva 9.;
> #P number 204 110 35 9 0 0 0 152 0 0 0 221 221 221 222 222 222 0 0 0;
> #P window linecount 1;
> #N counter;
> #X flags 0 0;
> #P newobj 204 88 66 9961481 counter;
> #P newex 204 62 20 9961481 t b;
> #P newex 204 40 42 9961481 error 1;
> #P message 32 45 39 9961481 name a;
> #P newex 32 98 110 9961481 jit.gl.slab out @inputs 1;
> #P newex 32 70 87 9961481 prepend sendinput;
> #P comment 83 46 100 9961481 8 input textures?;
> #P connect 3 0 1 0;
> #P connect 6 0 7 0;
> #P connect 5 0 6 0;
> #P connect 1 0 2 0;
> #P connect 4 0 5 0;
> #P window clipboard copycount 8;
>
>
>

> I'm using jitter 1.6.3b2 and I'm running into strange thing using 

> jit.gl.slab, it seems that it has eight input textures(try sending 

> it 'read' message, you'll get 8 opendialogs).

Sorry to follow up so late, but you need to use sendinput 

to only send to one input. Even with the inputs attribute, 

> Hello everyone,
>
> I'm using jitter 1.6.3b2 and I'm running into strange thing using  
> jit.gl.slab, it seems that it has eight input textures(try sending  
> it 'read' message, you'll get 8 opendialogs).
>
> Can anyone else reproduce this?

Sorry to follow up so late, but you need to use sendinput   
 to only send to one input. Even with the inputs attribute,  
there are 8 internal inputs.

But what about resources? Does jit.gl.slab allocate GPU memory when 

But what about resources? Does jit.gl.slab allocate GPU memory when  
it creates (unused) opengl textures?

> But what about resources? Does jit.gl.slab allocate GPU memory when 

Will investigate details of this to make sure it's not the case 

> But what about resources? Does jit.gl.slab allocate GPU memory when  
> it creates (unused) opengl textures?

Will investigate details of this to make sure it's not the case  
before 1.6.3 release.

eighttuple input (jit.gl.slab in jit1.63b2)