Brecht

I've come across a problem which I don't quite understand :

-the plane is textured by a jit.gl.sketch

-this result is captured for use as a texture, using the @capture 

-a second jit.gl.sketch uses that resulting texture

a second construction like that, using a second jit.gl.render, does 

the same thing, renders to a second window which is output to the 

now, what happens : on the main screen everything renders fine, on 

the 'extended' screen, all is blank. When dragging a window across, 

it shows the content on the first, and 'blinks to nothing' as soon as 

the windowposition crosses the border to the second screen.

Is there something that should be taken into account when rendering 2 

contexts, with textures, with jit.gl.texture and/or @capture? Or any 

I've come across a problem which I don't quite understand :
I'm :
-rendering a plane in jit.gl.sketch
-the plane is textured by a jit.gl.sketch
-this result is captured for use as a texture, using the @capture  
'name' method.
-a second jit.gl.sketch uses that resulting texture
-this result is output so screen 1.

a second construction like that, using a second jit.gl.render, does  
the same thing, renders to a second window which is output to the  
second screen connected to the PC.

now, what happens : on the main screen everything renders fine, on  
the 'extended' screen, all is blank. When dragging a window across,  
it shows the content on the first, and 'blinks to nothing' as soon as  
the windowposition crosses the border to the second screen.

Is there something that should be taken into account when rendering 2  
contexts, with textures, with jit.gl.texture and/or @capture? Or any  
known issues?

system : max 4.5.7, latest jitter for XP
pentium D, core duo 3.something
nvidia 7950

texture-issue-rendering-2-different-screens

I should maybe ad that the failing of rendering on the second screen 

is only the case when I use a jit.gl.texture with the same name as 

given as an argument to the @capture attribute.

If I just give the 2nd jit.gl.sketch the message "texture 'name'" it 

works fine, but then the texture is not as nicely wrapped on the 

I'll see if I can make a stripped version as an example patch and 

On Sep 13, 2006, at 5:29 PM, Brecht Debackere wrote:

> I've come across a problem which I don't quite understand :

> -the plane is textured by a jit.gl.sketch

> -this result is captured for use as a texture, using the @capture 

> -a second jit.gl.sketch uses that resulting texture

> a second construction like that, using a second jit.gl.render, does 

> the same thing, renders to a second window which is output to the 

> now, what happens : on the main screen everything renders fine, on 

> the 'extended' screen, all is blank. When dragging a window across, 

> it shows the content on the first, and 'blinks to nothing' as soon 

> as the windowposition crosses the border to the second screen.

> Is there something that should be taken into account when rendering 

> 2 contexts, with textures, with jit.gl.texture and/or @capture? Or 

> system : max 4.5.7, latest jitter for XP

I should maybe ad that the failing of rendering on the second screen  
is only the case when I use a jit.gl.texture with the same name as  
given as an argument to the @capture attribute.
If I just give the 2nd jit.gl.sketch the message "texture 'name'" it  
works fine, but then the texture is not as nicely wrapped on the  
geometry as when I use jit.gl.texture.
I'll see if I can make a stripped version as an example patch and  
post it lateron.

> Hello,
>
> I've come across a problem which I don't quite understand :
> I'm :
> -rendering a plane in jit.gl.sketch
> -the plane is textured by a jit.gl.sketch
> -this result is captured for use as a texture, using the @capture  
> 'name' method.
> -a second jit.gl.sketch uses that resulting texture
> -this result is output so screen 1.
>
> a second construction like that, using a second jit.gl.render, does  
> the same thing, renders to a second window which is output to the  
> second screen connected to the PC.
>
> now, what happens : on the main screen everything renders fine, on  
> the 'extended' screen, all is blank. When dragging a window across,  
> it shows the content on the first, and 'blinks to nothing' as soon  
> as the windowposition crosses the border to the second screen.
>
> Is there something that should be taken into account when rendering  
> 2 contexts, with textures, with jit.gl.texture and/or @capture? Or  
> any known issues?
>
> system : max 4.5.7, latest jitter for XP
> pentium D, core duo 3.something
> nvidia 7950
>
> cheers,
>
> Brecht
>
>


sorry. never mind. disregard this post :)

On Sep 13, 2006, at 5:56 PM, Brecht Debackere wrote:

> I should maybe ad that the failing of rendering on the second 

> screen is only the case when I use a jit.gl.texture with the same 

> name as given as an argument to the @capture attribute.

> If I just give the 2nd jit.gl.sketch the message "texture 'name'" 

> it works fine, but then the texture is not as nicely wrapped on the 

> I'll see if I can make a stripped version as an example patch and 

> On Sep 13, 2006, at 5:29 PM, Brecht Debackere wrote:

>> I've come across a problem which I don't quite understand :

>> -the plane is textured by a jit.gl.sketch

>> -this result is captured for use as a texture, using the @capture 

>> -a second jit.gl.sketch uses that resulting texture

>> a second construction like that, using a second jit.gl.render, 

>> does the same thing, renders to a second window which is output to 

>> the second screen connected to the PC.

>> now, what happens : on the main screen everything renders fine, on 

>> the 'extended' screen, all is blank. When dragging a window 

>> across, it shows the content on the first, and 'blinks to nothing' 

>> as soon as the windowposition crosses the border to the second 

>> Is there something that should be taken into account when 

>> rendering 2 contexts, with textures, with jit.gl.texture and/or 

>> system : max 4.5.7, latest jitter for XP

sorry. never mind. disregard this post :)
On Sep 13, 2006, at 5:56 PM, Brecht Debackere wrote:

> I should maybe ad that the failing of rendering on the second  
> screen is only the case when I use a jit.gl.texture with the same  
> name as given as an argument to the @capture attribute.
> If I just give the 2nd jit.gl.sketch the message "texture 'name'"  
> it works fine, but then the texture is not as nicely wrapped on the  
> geometry as when I use jit.gl.texture.
> I'll see if I can make a stripped version as an example patch and  
> post it lateron.
>
> brecht.
>
> On Sep 13, 2006, at 5:29 PM, Brecht Debackere wrote:
>
>> Hello,
>>
>> I've come across a problem which I don't quite understand :
>> I'm :
>> -rendering a plane in jit.gl.sketch
>> -the plane is textured by a jit.gl.sketch
>> -this result is captured for use as a texture, using the @capture  
>> 'name' method.
>> -a second jit.gl.sketch uses that resulting texture
>> -this result is output so screen 1.
>>
>> a second construction like that, using a second jit.gl.render,  
>> does the same thing, renders to a second window which is output to  
>> the second screen connected to the PC.
>>
>> now, what happens : on the main screen everything renders fine, on  
>> the 'extended' screen, all is blank. When dragging a window  
>> across, it shows the content on the first, and 'blinks to nothing'  
>> as soon as the windowposition crosses the border to the second  
>> screen.
>>
>> Is there something that should be taken into account when  
>> rendering 2 contexts, with textures, with jit.gl.texture and/or  
>> @capture? Or any known issues?
>>
>> system : max 4.5.7, latest jitter for XP
>> pentium D, core duo 3.something
>> nvidia 7950
>>
>> cheers,
>>
>> Brecht
>>
>>
>
>
>


texture issue rendering 2 different screens