yacine

is there a reason why the erase_color seems not to work with fsaa on.

just tell me and i ll prepare an example patch if you find my request 

is there a reason why the erase_color seems not to work with fsaa on.
just tell me and i ll prepare an example patch if you find my request  
unclear.

fsaa-and-erase_colore

Yeah, we'll need to see a patch, as well as hear some more info about 

your machine. What platform/OS? What video hardware? What version of 

MaxMSP and Jitter? On my machine "fsaa 1" and "erase_color" are working 

Yeah, we'll need to see a patch, as well as hear some more info about 
your machine.  What platform/OS? What video hardware?  What version of 
MaxMSP and Jitter?  On my machine "fsaa 1" and "erase_color" are working 
just fine.

I found a way to make it work by setting the fsaa attribute of 

jit.gl.render to 1, when before I only set it for jit.window, which 

seemed logic to me as the only note I found on fsaa is in 

but still there is something weird going on, see the patch.

currently working on a macbookpro core2duo - ati X1600 - osx 10.4.8 - 

I found a way to make it work by setting the fsaa attribute of  
jit.gl.render to 1, when before I only set it for jit.window, which  
seemed logic to me as the only note I found on fsaa is in  
jit.window's helpfile.
but still there is something weird going on, see the patch.

currently working on a macbookpro core2duo - ati X1600 - osx 10.4.8 -  
max 4.6.2 - jitter 1.6.2.

I was looking for a solution for the same problem and found your 

post. About your way to make it work.... after having send the fsaa1 

message to your jit.gl.render....I can be mistaking but it seems 

there is no more fsaa at all. switching it on/of does not improve it 

on my winmax laptop. i can use the fsaa 1 in combination with the 

dell8500, latest max/jitter, nvidea go4200.

did you find in the meanwhile another workaround to have fsaa1 and 

erase_color working together without sending fsaa1 to gl.render 

object? (in my opinion the fsaa doesnt work for either jit.window, or 

jit.gl.render after having send fsaa 1 to gl.render) ?

On 24 Dec 2006, at 13:46, yacine sebti wrote:

> I found a way to make it work by setting the fsaa attribute of 

> jit.gl.render to 1, when before I only set it for jit.window, which 

> seemed logic to me as the only note I found on fsaa is in 

> but still there is something weird going on, see the patch.

> currently working on a macbookpro core2duo - ati X1600 - osx 10.4.8 

> #P comment 382 116 213 196617 this isn't documented , fsaa appears 

> only in the Box Quick Message Reference menu and in jit.window's 

> #P flonum 173 124 35 9 0. 1. 3 3 0 0 0 221 221 221 222 222 222 0 0 0;

> #P message 173 149 115 196617 erase_color 0. 0. 0. $1;

> #P number 92 75 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;

> #P message 53 385 69 196617 fullscreen $1;

> #P newex 53 419 288 196617 jit.window context @depthbuffer 0 

> @floating 1 @doublebuffer 1 @fsmenubar 1 @rect 630 100 950 340 

> #P newex 51 206 324 196617 jit.gl.render context @blend_enable 1 

> @light_ambient 2 2 2 1. @ortho 1 @erase_color 0. 0. 0. 0.1 

I was looking for a solution for the same problem and found your  
post. About your way to make it work.... after having send the fsaa1  
message to your jit.gl.render....I can be mistaking but it seems  
there is no more fsaa at all. switching it on/of does not improve it  
anymore.

on my winmax laptop. i can use the fsaa 1 in combination with the  
erase_color attribute....

dell8500, latest max/jitter,  nvidea go4200.

did you find in the meanwhile another workaround to have fsaa1 and  
erase_color working together without sending fsaa1 to gl.render  
object? (in my opinion the fsaa doesnt work for either jit.window, or  
jit.gl.render after having send fsaa 1 to gl.render) ?

> hi,
>
> I found a way to make it work by setting the fsaa attribute of  
> jit.gl.render to 1, when before I only set it for jit.window, which  
> seemed logic to me as the only note I found on fsaa is in  
> jit.window's helpfile.
> but still there is something weird going on, see the patch.
>
> currently working on a macbookpro core2duo - ati X1600 - osx 10.4.8  
> - max 4.6.2 - jitter 1.6.2.
>
> marry XXX
> //yac
>
> max v2;
> #N vpatcher 9 56 897 620;
> #P origin -16 42;
> #P window setfont "Sans Serif" 9.;
> #P window linecount 1;
> #P newex 51 48 60 196617 loadmess 1;
> #P window linecount 3;
> #P comment 382 116 213 196617 this isn't documented , fsaa appears  
> only in the Box Quick Message Reference menu and in jit.window's  
> help file , not in jit.gl.render's;
> #P window setfont "Sans Serif" 18.;
> #P window linecount 1;
> #P comment 317 72 57 196626 >>>;
> #P window setfont "Sans Serif" 9.;
> #P flonum 173 124 35 9 0. 1. 3 3 0 0 0 221 221 221 222 222 222 0 0 0;
> #P toggle 318 102 43 0;
> #P message 318 161 44 196617 fsaa $1;
> #P message 173 149 115 196617 erase_color 0. 0. 0. $1;
> #P number 92 75 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
> #P toggle 53 363 15 0;
> #P message 53 385 69 196617 fullscreen $1;
> #P user jit.fpsgui 51 242 60 196617 0;
> #P newex 53 335 38 196617 sel 27;
> #P newex 53 313 40 196617 key;
> #P toggle 51 75 15 0;
> #P newex 51 121 61 196617 t b b erase;
> #P window linecount 2;
> #P newex 53 419 288 196617 jit.window context @depthbuffer 0  
> @floating 1 @doublebuffer 1 @fsmenubar 1 @rect 630 100 950 340  
> @fsaa 1 @sync 1;
> #P newex 51 206 324 196617 jit.gl.render context @blend_enable 1  
> @light_ambient 2 2 2 1. @ortho 1 @erase_color 0. 0. 0. 0.1  
> @depth_enable 0 @doublebuffer 1;
> #P window linecount 1;
> #P newex 51 100 51 196617 qmetro 1;
> #P newex 62 150 41 196617 s pulse;
> #P newex 422 337 41 196617 r pulse;
> #P message 447 386 304 196617 gltranslate $1 $2 $6 , glrotate  
> $3 0 0 1 , glscale -1 1 1 , plane $4;
> #P message 767 382 33 196617 reset;
> #P newex 422 420 332 196617 jit.gl.sketch context @lighting_enable  
> 1 @blend_enable 1 @automatic 0;
> #N vpatcher 737 434 1337 834;
> #P window setfont "Sans Serif" 9.;
> #P newex 423 150 70 196617 random 1000;
> #P newex 427 173 99 196617 scale 0 999 0.1 0.2;
> #P newex 282 112 70 196617 random 1000;
> #P newex 286 135 93 196617 scale 0 999 0 360;
> #P newex 168 135 70 196617 random 1000;
> #P newex 168 158 104 196617 scale 0 999 -0.5 0.5;
> #P newex 50 182 104 196617 scale 0 999 -0.8 0.8;
> #P newex 74 154 70 196617 random 1000;
> #P newex 50 235 307 196617 pack f f f f f f;
> #P newex 191 50 40 196617 b 3;
> #P newex 286 179 39 196617 !- 360;
> #P inlet 191 30 15 0;
> #P outlet 50 268 15 0;
> #P connect 5 0 6 0;
> #P connect 6 0 4 0;
> #P connect 4 0 0 0;
> #P connect 3 1 5 0;
> #P connect 7 0 4 1;
> #P connect 3 1 8 0;
> #P connect 8 0 7 0;
> #P connect 9 0 4 2;
> #P connect 1 0 3 0;
> #P connect 11 0 4 3;
> #P connect 3 1 10 0;
> #P connect 10 0 9 0;
> #P connect 9 0 2 0;
> #P connect 2 0 4 4;
> #P connect 3 1 12 0;
> #P connect 12 0 11 0;
> #P pop;
> #P newobj 447 367 64 196617 p randomize;
> #P window linecount 3;
> #P comment 382 72 212 196617 I have to send the fsaa 1 message to  
> the jit.gl.render to activate erase_color , then it can even be  
> turned off.;
> #P connect 24 0 11 0;
> #P connect 11 0 7 0;
> #P connect 7 0 10 0;
> #P fasten 18 0 8 0 178 197 56 197;
> #P fasten 10 2 8 0 106 172 56 172;
> #P connect 10 0 8 0;
> #P fasten 19 0 8 0 323 197 56 197;
> #P connect 8 0 14 0;
> #P connect 12 0 13 0;
> #P connect 13 0 16 0;
> #P connect 16 0 15 0;
> #P connect 15 0 9 0;
> #P fasten 10 1 6 0 81 144 67 144;
> #P connect 17 0 7 1;
> #P connect 21 0 18 0;
> #P connect 20 0 19 0;
> #P connect 5 0 2 0;
> #P fasten 3 0 2 0 772 411 427 411;
> #P fasten 4 0 2 0 452 411 427 411;
> #P fasten 5 0 1 0 427 361 452 361;
> #P connect 1 0 4 0;
> #P fasten 5 0 3 0 427 361 772 361;
> #P pop;
>
>
>

Visual Kitchen vzw
Office:
Onderwijsstraat 51
B-1070 Brussel
Belgium
t: +32(0)2 410 80 45
f: +32[0]2 520 07 82
e: jurgen@visualkitchen.org
skypename: jurgenvangemert
msn: jurgen@visualkitchen.org
www.visualkitchen.org
www.cimatics.com
subscribe to our newsletter at: http://userlists.all2all.org/mailman/ 
listinfo/visualkitchen


i have run into the same problem (on osx), almost same laptop (mbp coreduo 2.16 / ati x1600).

after some "unguided technical" tweaking, i discovered u need to turn off doublebuffer on the jit.window. u might also need to turn off depthbuffer.

also, u should send fsaa to the jit.window only, not to the jit.render and jit.window which is what i did at first.

just this ....if playing with combinations doublebuffer/depthbuffer/ 

fsaa on or off to jit.window ....it affects the blend_mode state of 

a render content in my opinion. the blend_mode state acts different 

with a various of combinations of doublebuffer/depthbuffer/fsaa 

state. i haven't find the logica behind it.

> i have run into the same problem (on osx), almost same laptop (mbp 

> after some "unguided technical" tweaking, i discovered u need to 

> turn off doublebuffer on the jit.window. u might also need to turn 

> also, u should send fsaa to the jit.window only, not to the 

> jit.render and jit.window which is what i did at first.

just this ....if playing with combinations doublebuffer/depthbuffer/ 
fsaa on or off to jit.window ....it affects the blend_mode state of  
a  render content in my opinion. the blend_mode state acts different  
with a various of combinations of doublebuffer/depthbuffer/fsaa  
state. i haven't find the logica behind it.

>
> i have run into the same problem (on osx), almost same laptop (mbp  
> coreduo 2.16 / ati x1600).
>
> after some "unguided technical" tweaking, i discovered u need to  
> turn off doublebuffer on the jit.window. u might also need to turn  
> off depthbuffer.
>
> also, u should send fsaa to the jit.window only, not to the  
> jit.render and jit.window which is what i did at first.
>
> j
>
>
>

Quote: jurgen wrote on Sun, 04 March 2007 11:41

----------------------------------------------------

> just this ....if playing with combinations doublebuffer/depthbuffer/ 

> fsaa on or off to jit.window ....it affects the blend_mode state of 

> a render content in my opinion. the blend_mode state acts different 

> with a various of combinations of doublebuffer/depthbuffer/fsaa 

> state. i haven't find the logica behind it.

am afraid i cant explain the logic! i have also noticed that a small floating window will have transparent objects (blend enabled), then when u go to fullscreen they become opaque, or vice versa??? weird...

but at least my last solution works! altho it would be good to understand a bit more what is going on.

Quote: jurgen wrote on Sun, 04 March 2007 11:41
----------------------------------------------------
> Ok works for me....
>
> just this ....if playing with combinations doublebuffer/depthbuffer/ 
> fsaa on or off to jit.window ....it affects the blend_mode state of  
> a  render content in my opinion. the blend_mode state acts different  
> with a various of combinations of doublebuffer/depthbuffer/fsaa  
> state. i haven't find the logica behind it.

Ive been doing quite a bit of testing, and disabling doublebuffer 

basically... totally breaks render to texture (not logically, the 

patches work, but you loose a lot of control due to not having that 

second buffer). I seem to be getting a lot of extra flashing as the 

buffer is swapped and slab effects also break on the render to texture.

Id suggest not using this methodology if you want to use a more 

is there a way, besides sending fsaa 1 to jit.window, to dynamically 

toggle fsaa on and off within a render cycle (between erase and the 

On Mar 4, 2007, at 6:41 AM, Jurgen Van Gemert wrote:

> a render content in my opinion. the blend_mode state acts 

> different with a various of combinations of doublebuffer/ 

> depthbuffer/fsaa state. i haven't find the logica behind it.

> On 04 Mar 2007, at 11:11, justin wrote:

>> i have run into the same problem (on osx), almost same laptop (mbp 

>> after some "unguided technical" tweaking, i discovered u need to 

>> turn off doublebuffer on the jit.window. u might also need to turn 

>> also, u should send fsaa to the jit.window only, not to the 

>> jit.render and jit.window which is what i did at first.

Ive been doing quite a bit of testing, and disabling doublebuffer  
basically... totally breaks render to texture (not logically, the  
patches work, but you loose a lot of control due to not having that  
second buffer). I seem to be getting a lot of extra flashing as the  
buffer is swapped and slab effects also break on the render to texture.

Id suggest not using this methodology if you want to use a more  
complicated pipeline.

is there a way, besides sending fsaa 1 to jit.window, to dynamically  
toggle fsaa on and off within a render cycle (between erase and the  
final draw bang to jit.gl.render?)

> Ok works for me....
>
> just this ....if playing with combinations doublebuffer/depthbuffer/ 
> fsaa on or off to jit.window ....it affects the blend_mode state of  
> a  render content in my opinion. the blend_mode state acts  
> different with a various of combinations of doublebuffer/ 
> depthbuffer/fsaa state. i haven't find the logica behind it.
>
> j
>
>
> On 04 Mar 2007, at 11:11, justin wrote:
>
>>
>> i have run into the same problem (on osx), almost same laptop (mbp  
>> coreduo 2.16 / ati x1600).
>>
>> after some "unguided technical" tweaking, i discovered u need to  
>> turn off doublebuffer on the jit.window. u might also need to turn  
>> off depthbuffer.
>>
>> also, u should send fsaa to the jit.window only, not to the  
>> jit.render and jit.window which is what i did at first.
>>
>> j
>>
>>
>>
>
> -- 
>
> Visual Kitchen vzw
> Office:
> Onderwijsstraat 51
> B-1070 Brussel
> Belgium
> t: +32(0)2 410 80 45
> f: +32[0]2 520 07 82
> e: jurgen@visualkitchen.org
> skypename: jurgenvangemert
> msn: jurgen@visualkitchen.org
> www.visualkitchen.org
> www.cimatics.com
> subscribe to our newsletter at: http://userlists.all2all.org/ 
> mailman/listinfo/visualkitchen
>
>
>

fsaa and erase_colore