hello,
I've noticed a small problem on osX version of Gem.
the problem is related with curve object. sometimes, curve objects are not drown properly. they can be drown with a random width, and can sometimes disepear.
the problem is random, but it never happend the first time pd open a gemwindow.
exemples : open pd + attached tst-curve. create gemwindow.
ok, everyting is fine. close the patch. open the patch again.
now, you should have some problem. (I've got problem with the 3 diferents computers on OSX (10.3) I tried).
I tried diferents gem version.
does anybody kown what to do?
I rebember that I have the same problem long time ago on windows and linux, but the problem is gone...
anyway, what's appening with "width" message to primitive. most, but not every, primitives accept a "width" messages. this messages is not really documented (not in the help file). is it on purpose? does this messages will disapare on future gem release?
thanks
cyrille
#N canvas 576 418 596 436 10; #X obj 104 166 gemhead; #X obj 31 89 gemwin; #X msg 31 49 reset , create , 1; #X msg 46 69 0 , destroy; #X obj 104 209 curve 2; #X msg 148 188 3 3 0; #X obj 192 168 gemhead; #X obj 192 211 curve 2; #X obj 284 167 gemhead; #X obj 284 210 curve 2; #X obj 372 169 gemhead; #X obj 372 212 curve 2; #X msg 236 190 3 -3 0; #X msg 328 189 -3 3 0; #X msg 416 191 -3 -3 0; #X obj 148 130 loadbang; #X obj 106 266 gemhead; #X obj 106 309 curve 2; #X obj 194 268 gemhead; #X obj 194 311 curve 2; #X obj 286 267 gemhead; #X obj 286 310 curve 2; #X obj 374 269 gemhead; #X obj 374 312 curve 2; #X obj 150 242 loadbang; #X msg 150 288 3 0 0; #X msg 238 290 0 -3 0; #X msg 330 289 -3 0 0; #X msg 418 291 0 3 0; #X connect 0 0 4 0; #X connect 2 0 1 0; #X connect 3 0 1 0; #X connect 5 0 4 2; #X connect 6 0 7 0; #X connect 8 0 9 0; #X connect 10 0 11 0; #X connect 12 0 7 2; #X connect 13 0 9 2; #X connect 14 0 11 2; #X connect 15 0 5 0; #X connect 15 0 12 0; #X connect 15 0 13 0; #X connect 15 0 14 0; #X connect 16 0 17 0; #X connect 18 0 19 0; #X connect 20 0 21 0; #X connect 22 0 23 0; #X connect 24 0 25 0; #X connect 24 0 26 0; #X connect 24 0 27 0; #X connect 24 0 28 0; #X connect 25 0 17 2; #X connect 26 0 19 2; #X connect 27 0 21 2; #X connect 28 0 23 2;
Hey Cyrille,
First time I opened it on linux the vertical curve was very thick, after closing and opening then it apears normal. Third time the curve widths are different again.
I tried it with my recent Gem build on OSX and the same deal, except the width is significantly more extreme.
I'm rebuilding Gem under linux now and...
Well I can't get the Gem update from today to compile: /home/bbogart/gem/gemcvs/Gem.pd_linux: /home/bbogart/gem/gemcvs/Gem.pd_linux: undefined symbol: _ZN12pix_movement17processYUVAltivecER11imageStruct
My old build was about a month old.
Thanks for the test patch cyrille.
Ben
cyrille henry wrote:
hello,
I've noticed a small problem on osX version of Gem.
the problem is related with curve object. sometimes, curve objects are not drown properly. they can be drown with a random width, and can sometimes disepear.
the problem is random, but it never happend the first time pd open a gemwindow.
exemples : open pd + attached tst-curve. create gemwindow.
ok, everyting is fine. close the patch. open the patch again.
now, you should have some problem. (I've got problem with the 3 diferents computers on OSX (10.3) I tried).
I tried diferents gem version.
does anybody kown what to do?
I rebember that I have the same problem long time ago on windows and linux, but the problem is gone...
anyway, what's appening with "width" message to primitive. most, but not every, primitives accept a "width" messages. this messages is not really documented (not in the help file). is it on purpose? does this messages will disapare on future gem release?
thanks
cyrille
#N canvas 576 418 596 436 10; #X obj 104 166 gemhead; #X obj 31 89 gemwin; #X msg 31 49 reset , create , 1; #X msg 46 69 0 , destroy; #X obj 104 209 curve 2; #X msg 148 188 3 3 0; #X obj 192 168 gemhead; #X obj 192 211 curve 2; #X obj 284 167 gemhead; #X obj 284 210 curve 2; #X obj 372 169 gemhead; #X obj 372 212 curve 2; #X msg 236 190 3 -3 0; #X msg 328 189 -3 3 0; #X msg 416 191 -3 -3 0; #X obj 148 130 loadbang; #X obj 106 266 gemhead; #X obj 106 309 curve 2; #X obj 194 268 gemhead; #X obj 194 311 curve 2; #X obj 286 267 gemhead; #X obj 286 310 curve 2; #X obj 374 269 gemhead; #X obj 374 312 curve 2; #X obj 150 242 loadbang; #X msg 150 288 3 0 0; #X msg 238 290 0 -3 0; #X msg 330 289 -3 0 0; #X msg 418 291 0 3 0; #X connect 0 0 4 0; #X connect 2 0 1 0; #X connect 3 0 1 0; #X connect 5 0 4 2; #X connect 6 0 7 0; #X connect 8 0 9 0; #X connect 10 0 11 0; #X connect 12 0 7 2; #X connect 13 0 9 2; #X connect 14 0 11 2; #X connect 15 0 5 0; #X connect 15 0 12 0; #X connect 15 0 13 0; #X connect 15 0 14 0; #X connect 16 0 17 0; #X connect 18 0 19 0; #X connect 20 0 21 0; #X connect 22 0 23 0; #X connect 24 0 25 0; #X connect 24 0 26 0; #X connect 24 0 27 0; #X connect 24 0 28 0; #X connect 25 0 17 2; #X connect 26 0 19 2; #X connect 27 0 21 2; #X connect 28 0 23 2;
yes, you are right, the problem also occur on my linux box. so,only windows version of gem are not affected by this problem.
thanks cyrille
B. Bogart wrote:
Hey Cyrille,
First time I opened it on linux the vertical curve was very thick, after closing and opening then it apears normal. Third time the curve widths are different again.
I tried it with my recent Gem build on OSX and the same deal, except the width is significantly more extreme.
I'm rebuilding Gem under linux now and...
Well I can't get the Gem update from today to compile: /home/bbogart/gem/gemcvs/Gem.pd_linux: /home/bbogart/gem/gemcvs/Gem.pd_linux: undefined symbol: _ZN12pix_movement17processYUVAltivecER11imageStruct
My old build was about a month old.
Thanks for the test patch cyrille.
Ben
cyrille henry wrote:
hello,
I've noticed a small problem on osX version of Gem.
the problem is related with curve object. sometimes, curve objects are not drown properly. they can be drown with a random width, and can sometimes disepear.
the problem is random, but it never happend the first time pd open a gemwindow.
exemples : open pd + attached tst-curve. create gemwindow.
ok, everyting is fine. close the patch. open the patch again.
now, you should have some problem. (I've got problem with the 3 diferents computers on OSX (10.3) I tried).
I tried diferents gem version.
does anybody kown what to do?
I rebember that I have the same problem long time ago on windows and linux, but the problem is gone...
anyway, what's appening with "width" message to primitive. most, but not every, primitives accept a "width" messages. this messages is not really documented (not in the help file). is it on purpose? does this messages will disapare on future gem release?
thanks
cyrille
#N canvas 576 418 596 436 10; #X obj 104 166 gemhead; #X obj 31 89 gemwin; #X msg 31 49 reset , create , 1; #X msg 46 69 0 , destroy; #X obj 104 209 curve 2; #X msg 148 188 3 3 0; #X obj 192 168 gemhead; #X obj 192 211 curve 2; #X obj 284 167 gemhead; #X obj 284 210 curve 2; #X obj 372 169 gemhead; #X obj 372 212 curve 2; #X msg 236 190 3 -3 0; #X msg 328 189 -3 3 0; #X msg 416 191 -3 -3 0; #X obj 148 130 loadbang; #X obj 106 266 gemhead; #X obj 106 309 curve 2; #X obj 194 268 gemhead; #X obj 194 311 curve 2; #X obj 286 267 gemhead; #X obj 286 310 curve 2; #X obj 374 269 gemhead; #X obj 374 312 curve 2; #X obj 150 242 loadbang; #X msg 150 288 3 0 0; #X msg 238 290 0 -3 0; #X msg 330 289 -3 0 0; #X msg 418 291 0 3 0; #X connect 0 0 4 0; #X connect 2 0 1 0; #X connect 3 0 1 0; #X connect 5 0 4 2; #X connect 6 0 7 0; #X connect 8 0 9 0; #X connect 10 0 11 0; #X connect 12 0 7 2; #X connect 13 0 9 2; #X connect 14 0 11 2; #X connect 15 0 5 0; #X connect 15 0 12 0; #X connect 15 0 13 0; #X connect 15 0 14 0; #X connect 16 0 17 0; #X connect 18 0 19 0; #X connect 20 0 21 0; #X connect 22 0 23 0; #X connect 24 0 25 0; #X connect 24 0 26 0; #X connect 24 0 27 0; #X connect 24 0 28 0; #X connect 25 0 17 2; #X connect 26 0 19 2; #X connect 27 0 21 2; #X connect 28 0 23 2;
GEM-dev mailing list GEM-dev@iem.at http://iem.at/cgi-bin/mailman/listinfo/gem-dev
Quoting "B. Bogart" ben@ekran.org:
I'm rebuilding Gem under linux now and...
Well I can't get the Gem update from today to compile: /home/bbogart/gem/gemcvs/Gem.pd_linux: /home/bbogart/gem/gemcvs/Gem.pd_linux: undefined symbol: _ZN12pix_movement17processYUVAltivecER11imageStruct
I forgot some ifdefs and Johannes added them, but the #ifdef __VEC__ should be inside the function in the .cpp file. Alternately, you could wrap the ifdef around the prototype in the header file. I will fix this up when I get home later if it's not done by someone else before then.
cgc
-
B. Bogart -
cgc＠humboldtblvd.com -
cyrille henry