Re: [GEM-dev] anti-aliased [text3d]
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Le 16/04/2014 17:30, IOhannes m zmölnig a écrit : > On 04/16/2014 11:49 AM, Jack wrote: >> Hmm, people who used to use FSAA message to manage antialiasing for >> their fonts, will have something different in the 3D scene. > > yes they will, but the question is, whether this hurts. > openGL never guarantees pixel-accurate rendering across implementations, > so (in theory) your scene can look differently when you upgrade your > drivers. > and FSAA never consistently worked across all platforms. Yep, that's true. > > > >> And people >> who applied texture on their fonts, won't be able to apply them. > > yes. that's probably more of a problem. > one possibility would be to detect whether there is a texture in the > gemlist, and if so, fall back to the old behaviour (at least in some > default "autotexture" mode) > > another would be to allow configuring the default [text3d] backend via > gem.conf. Don't know. For me, if you can't antialiased all geos, why you particulary want to antialiased the text3d object (even if I know why). There is the same problem on curve, small square, small circle, etc. Then, you have several possibilties working on all geos (with different result) : - - FSAA - - shaders - - upsampling > > >> So for me it is important to have [antialias 0( as default. > > how many of your patches would be broken? 0 % :) ++ Jack > > > gfmdars > IOhannes > > > > ___ > GEM-dev mailing list > GEM-dev@iem.at > http://lists.puredata.info/listinfo/gem-dev -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.14 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJTTwfqAAoJEOuluecjw8GU3ZEH/1eq3VOqkXATJEGru20LQr8p 01s1F1vaDPqdpGyR1vFWYg5eREME3UnTWzaN2ilhKZdKwLGsZC0FZa2hCeGCWke4 edCBzWe0ZAcNC+RE4i+wmxnz7SqJs7VgW8oCInwbCSpvAZ5BHCwT+UPmGydgyXnW E5SBPBJGmYRUF882uSnLpzH3Bo5DoNWqAfh2metfG6Jp3GsFcYzwRwkboW98jR4b nWDKV0NZWCuyUkTLAcEgTDMk3Nx3TJCIMd65za77a72lGwJHpLaBw89UTgS3mI// V/3Q91wMSEqR5LSP0R6Tj36ApfxZMj6PBjBDhWO+q9pgZ1KevtSuMJ0r6SNt6YM= =xUVm -END PGP SIGNATURE- ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Re: [GEM-dev] anti-aliased [text3d]
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 OK, thanx to share. ++ Jack Le 16/04/2014 17:25, IOhannes m zmölnig a écrit : > On 04/16/2014 11:49 AM, Jack wrote: if so, then i guess it's a bug. >> I don't know, it was just a guess. >> What is the behavior of precision on antialiasing then ? >> > > > it's not a real "anti-alias". it's rendering the font onto a texture of > a given size (evtl. rather small) and then scaling the texture to your > needs. > so the bluriness does not depend on the window size. > > attached is a snapshot of two Gem windows displying text at > "precision=0.1", the left one is 250x250, the right one 500x500. the > text on the small screen is [scale 2]d to have the same size as on the > big screen. as you can see, they look the same. > > fgdsar > IOhannes > > > ___ > GEM-dev mailing list > GEM-dev@iem.at > http://lists.puredata.info/listinfo/gem-dev -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.14 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJTTwRFAAoJEOuluecjw8GUEcEIAJXw4DxGOwH0SrLJyRLSLNYW 7NFIv84V3mYoPpkrO6AqYI9eK8RNzH2t120LK4mZ9gl0mBjB7N1B16YlE7i55Qe7 ltZ/5rvXVxQbduCTxa+tyTvYMH0NS833RhgxTt2jdw5B9Q1fCqJIwccEL5fH+wKh OaguLflqcBCBlRoqBDB25LFwxWKuwPSm5M3eDvWvFQ8BZcatckmgsp7UKWskRZtn 5/xZyrXiMGPIKsDK5cuo3XbhUFFAwsn7yVrtbs8MJucs/QusTXTVAvcPBxcj9puD R1b84bFW4Vmp1jGtAE8OR7HxBYhZ1Pxjuk+GEFSAU5tNre8E51AI1GBY9BiKQYg= =/q9z -END PGP SIGNATURE- ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Re: [GEM-dev] anti-aliased [text3d]
On 04/16/2014 11:49 AM, Jack wrote: > Hmm, people who used to use FSAA message to manage antialiasing for > their fonts, will have something different in the 3D scene. yes they will, but the question is, whether this hurts. openGL never guarantees pixel-accurate rendering across implementations, so (in theory) your scene can look differently when you upgrade your drivers. and FSAA never consistently worked across all platforms. > And people > who applied texture on their fonts, won't be able to apply them. yes. that's probably more of a problem. one possibility would be to detect whether there is a texture in the gemlist, and if so, fall back to the old behaviour (at least in some default "autotexture" mode) another would be to allow configuring the default [text3d] backend via gem.conf. > So for me it is important to have [antialias 0( as default. how many of your patches would be broken? gfmdars IOhannes signature.asc Description: OpenPGP digital signature ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Re: [GEM-dev] anti-aliased [text3d]
On 04/16/2014 11:49 AM, Jack wrote: >> > if so, then i guess it's a bug. > I don't know, it was just a guess. > What is the behavior of precision on antialiasing then ? > it's not a real "anti-alias". it's rendering the font onto a texture of a given size (evtl. rather small) and then scaling the texture to your needs. so the bluriness does not depend on the window size. attached is a snapshot of two Gem windows displying text at "precision=0.1", the left one is 250x250, the right one 500x500. the text on the small screen is [scale 2]d to have the same size as on the big screen. as you can see, they look the same. fgdsar IOhannes <> signature.asc Description: OpenPGP digital signature ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Re: [GEM-dev] anti-aliased [text3d]
Le 16/04/2014 11:49, Jack a écrit : > but i would prefer if we could use the antialiased version as the > default (as i expect it to be more useful in general). Hmm, people who used to use FSAA message to manage antialiasing for their fonts, will have something different in the 3D scene. And people who applied texture on their fonts, won't be able to apply them. So for me it is important to have [antialias 0( as default. I think text3d was so ugly without anti-aliasing that it was almost not usable. and i dont mind breaking few patch for the better. but if it cause to much trouble, maybe text3d can be renamed in 3dtext (or somthing else), and a text3d abstraction can be made for compatibility with old patch. cheers c ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Re: [GEM-dev] Gem git repository
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Le 16/04/2014 10:47, IOhannes m zmoelnig a écrit : > On 2014-04-15 18:50, Jack wrote: > > What are the differences between these two repository ? > > git://git.code.sf.net/p/pd-gem/gem pd-gem-gem > > git://pd-gem.git.sourceforge.net/gitroot/pd-gem/Gem > > > Because i expect to find the new [text3d] on > > git://pd-gem.git.sourceforge.net/gitroot/pd-gem/Gem, but i was > > wrong. > > the official git repository of gem is on sourceforge. > > however, i mostly work on the github repository (esp. when > experimenting with stuff (there are a few branches only on github); or > dealing with pull requests). > > once i think that a feature is good enough to appear in the official > repository, i sync the two. > > fgmsdr > IOhannes OK, thanx for the precisions. ++ Jack -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.14 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJTTlLGAAoJEOuluecjw8GUV+oH/1kse/AJHHRL+yZCJvxhHNkw tzVJwPI5uB2ySp2e9OlyXeHQlBVyvrG+UCeqVBZ2f6ord8nVNMlumcd5UaciCtq4 ZIESuhVMeUaGZtn5IAQh5tF4HpamYnArJxuxdcv+HEO6XSfT+ZrtWeVylweYha0D WfPDYVi1+qhGWqqKszbVXU2YYD9rBoOweqW3TVExKE9RheI4t8P24JgMDFD7BbZT ZEz4HIz9e2Srbg4knVbJrCPqNc8bLIlMb5dIyGp8+UuGy4TxftciMTnrMnIuV35a wSRyjVRcaSzBfcuehHlGY7kOkMHmXOHmCSa/vcOkxr4goXgJy0j4N8JGLhwbSvg= =idw6 -END PGP SIGNATURE- ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Re: [GEM-dev] anti-aliased [text3d]
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Le 16/04/2014 10:45, IOhannes m zmoelnig a écrit : > On 2014-04-15 20:42, Jack wrote: > > > Le 14/04/2014 15:40, IOhannes m zmölnig a écrit : > >> i've just committed an updated version of [text3d] that has a > >> kind of anti-aliasing built-in. > > >> it uses textures internally. the size of the texture (and thus > >> the bluriness) can be controlled via the (revived) [precision( > >> message. > > The precision message depends on the gemwin dimen ? If precision=1 > > then the texture size is the size of gemwin ? If precision=2 then > > the texture size is the double size of gemwin ? etc. ? > > if so, then i guess it's a bug. I don't know, it was just a guess. What is the behavior of precision on antialiasing then ? > > > >> let me know, whether this change breaks any patches. > > Why, the default is [antialias 1( ? Should be [antialias 0(, no ? > > Because it will break patches... > > this depends on what *you all* say. > if it will break indeed "a lot" of patches (whatever a lot means), i > will revert the default to antialias=0. > > but i would prefer if we could use the antialiased version as the > default (as i expect it to be more useful in general). Hmm, people who used to use FSAA message to manage antialiasing for their fonts, will have something different in the 3D scene. And people who applied texture on their fonts, won't be able to apply them. So for me it is important to have [antialias 0( as default. ++ Jack > > > > mfgasdr > IOhannes > > ___ > GEM-dev mailing list > GEM-dev@iem.at > http://lists.puredata.info/listinfo/gem-dev -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.14 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJTTlJBAAoJEOuluecjw8GUuZ8H/jxx8SZcEx6xk2MyTRMSvNqy L8JqDOsQvo+u9NzToRnwkWB+lFkplBBLXirVzkAfiCNEYZ0RhvfOYsyK+yZYSD11 D0PFcw5BRWjq9WuSKocX/1HT87lkNgBCyvqRjRw37oQrEXXg0uu8qzHHrvQyUDRj PEoMj8Re8hfs1CYJl7gl8BtCmdyBLnxcT3hweaQ/xod8jYIDbZNxSA9KE0srA+nT ohUcdUFdJI1mM4ZHSMLGpG2wZd4OWcQ7shTjfSlM7DbYpLjIx2ans4SNQnlYH3ts QszCShAJm7pmLOrdgWxzX4Vs67DYy7hSNZwkiZHd+XeM0hceDEk4iA9W7M7g/kc= =ZFSh -END PGP SIGNATURE- ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Re: [GEM-dev] Gem git repository
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 2014-04-15 18:50, Jack wrote: > What are the differences between these two repository ? > git://git.code.sf.net/p/pd-gem/gem pd-gem-gem > git://pd-gem.git.sourceforge.net/gitroot/pd-gem/Gem > > Because i expect to find the new [text3d] on > git://pd-gem.git.sourceforge.net/gitroot/pd-gem/Gem, but i was > wrong. the official git repository of gem is on sourceforge. however, i mostly work on the github repository (esp. when experimenting with stuff (there are a few branches only on github); or dealing with pull requests). once i think that a feature is good enough to appear in the official repository, i sync the two. fgmsdr IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1 Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iQIcBAEBCAAGBQJTTkO/AAoJELZQGcR/ejb44SYP/jaOpSaFfg0SD0dl1bmFVDxg 9GIEipBF2VPTptV94j872AZJDQtMPf2T9xUG7sG3z31Scc5paLCuy+XJcAESER4Y R3CqPimYQOdavPS09l+W7+DIkIMvsJQKh83BeMl+/UZFMS/6a3fElv79c5kn66Lz 0LOw6Hdm/TQ91WhIPQg1qkCsFC6+luOtBtoAqzczYv2EgBqc61XqsgwUfh+i0s3i 85eWQVEWFMf6UeaEt7T1i8NwmQaQWP6deFaWm15e7G7nsmr2rkw6TMCb8T3QL9lb wfHvRNiQFQgz2appdeloh5ON/WYcM69saJKAfv38cwdWC+GPLV/fA9E1VNSYNt/g ZFOQj6WYGJQTVCITL5xN8RQkxYQdxlwIIFPjNgpcwB+Q1qyAu5oexPc3zCJlRTwI nrJ4RhorI8MFAM9XtAQ3SlZyjoT1r8f29yTNAGUNKAcra0lPplhuDTV8vi0yBM4N zsE782LWOGvy1HKyUQxqCj8P1HEu2XH66/oI+D2W9NcU1J2hs/4UpJXAnHVwyWpR x1R2vgjKQcODwboBeI+kt+giDzzY6zBaDqlbin1/VcrPVls1fq3Odd0dUn7JIiz5 hxvbzhp9rE47UDfWaOVFZs1qOrP5Dnff/dP5pZPCOsoS8WvpX/sz4FXP9MqZggXc +N2O06nsw0ypsixjcwwS =VGkD -END PGP SIGNATURE- ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Re: [GEM-dev] anti-aliased [text3d]
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 2014-04-15 20:42, Jack wrote: > > Le 14/04/2014 15:40, IOhannes m zmölnig a écrit : >> i've just committed an updated version of [text3d] that has a >> kind of anti-aliasing built-in. > >> it uses textures internally. the size of the texture (and thus >> the bluriness) can be controlled via the (revived) [precision( >> message. > The precision message depends on the gemwin dimen ? If precision=1 > then the texture size is the size of gemwin ? If precision=2 then > the texture size is the double size of gemwin ? etc. ? if so, then i guess it's a bug. > >> let me know, whether this change breaks any patches. > Why, the default is [antialias 1( ? Should be [antialias 0(, no ? > Because it will break patches... this depends on what *you all* say. if it will break indeed "a lot" of patches (whatever a lot means), i will revert the default to antialias=0. but i would prefer if we could use the antialiased version as the default (as i expect it to be more useful in general). mfgasdr IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1 Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iQIcBAEBCAAGBQJTTkM/AAoJELZQGcR/ejb44uQP/jRuQ2g5uuR5f0VvbP3PgByQ L4OxzEJR26agsszmLQ7qEwYvPpWYygPMmW9hc/Ihpd2ghi5lkFje8LI3f/4msL5N sIrr2I4SUQYsNFti1khbs7+DPxf2wwbY2/sQ99cemFtHp5bPRPC2nrqNl4c6Sv3J BeMKilcJka3OpQVDKyib2Yuo3+YLyKGTfUTsECAa284DtClR2Cy78EUXUs1cVCdX 4Bpp0FYQSNjDdKn2fiyPfv/OfJpKokUDqZdJWCmFZ+2bUEaJY9/+iqK09Z7yb7AC gR/T5skCzWWP/kKHQv8NOtOcIbv+OYyNGkw6ggna72luT6kSiTVFFoFEaqBOCfRI rF0RIc2o3QCtJqWIPNm8ZhW34uFeB/QGeeiyOcCIkV7qcg3eeiVlL3Fba+u8IMt4 Hj1x7Zua2JQvIO18atWO75MkRjtAC4bsy4Knda+duLiSeemsoRaiaDs+nDNrkuYn inFvUuN3q5TKOr/c3rzw1zNRhHwH1m+8ziVCK3iGxrjYMQL/AbAN4VTWDkrlDSh5 01JhIS5a5hvRPEvUptPGsliPMJSjIV7z4140MSvW+92L6jEkBVH1SJwUIgHVzONg C0ZWXUgjeQQ/Y7khLFNtkm/fZ/ELQAwKReU2r1epOyEG6Mj812VoqklO6Mo1z7cB iB/8KPku5vpXCfmedCgp =fbsR -END PGP SIGNATURE- ___ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
