Re: [GEM-dev] [GEM-cvs] [SCM] Gem - Graphics environment for multimedia branch, master, updated. ea9034f83180410f96e063a32903d06992355498
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 2014-05-13 12:58, Cyrille Henry wrote:
add a new 32 type for framebuffer (since GL_RGB_FLOAT32_ATI is not usable with intel GPU on linux)
wouldn't it make more sense to have a single float32 type on the patch-level ("RGB32"), and use whatever is available on the given GPU?
mfgasdr IOhannes
Le 15/05/2014 13:26, IOhannes m zmoelnig a écrit :
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 2014-05-13 12:58, Cyrille Henry wrote:
add a new 32 type for framebuffer (since GL_RGB_FLOAT32_ATI is not usable with intel GPU on linux)
wouldn't it make more sense to have a single float32 type on the patch-level ("RGB32"), and use whatever is available on the given GPU?
It would be nice that Gem choose what type to use, but I don't know how to do this choice when many type are available. I think they are not equivalent depending on what you want to do. So the easiest solution is to test them on each combination of patch / hardware.
moreover RGBA32 is a 4 channel type, while GL_RGB_FLOAT32_ATI is only 3.
cheers Cyrille
mfgasdr IOhannes -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 Comment: Using GnuPG with Icedove - http://www.enigmail.net/
iQIcBAEBCAAGBQJTdKRoAAoJELZQGcR/ejb4VTcP/2jnNTwYjL/mq2RkA3dlPJHX PDV8pME20GDxDCCKhTZXRJNoZ0SqJLK4B7ztim8Lt1jpY6Sf3abjr9Mr64tXwsRF tIHVqUBt49SuHE96KW+2jCdIpWrJvBLXsrn8WlL4e5lDA23Aa2kwfVV8br8QDOyH +MljD4GjD8CgSPs6DQgFQxyVZgCV6k85Q1eYJdZEtszLtNQyQQDUXSmHNJ8SIzoN PXM6NBQROHWSBmMyDsjD4Uk9JFfF+av5P8hfXHgjRBPxpaBsr5NLUACIFOqQyxPB KfsnlgJsyUD3hYhO28Be548S9ewBDmX+0BvFrY785tOl7E7Kq57PBSuo6UbGzxKZ kemgWgbcIZoARJAJVAp4sJCylKEQg69wrKxm229yUZefF1PLGSClVeeIGFHMVJOE U5+5Qa3b8P24legve1aJx2PSSiVzMQSxrcSiCnlsGiaJ5w6sPqFU6+3JUXScQSqH nDsPl8lu3Hn4EZEAqPxaFS25c6yStKl1v48WPYEBOd/ZoO49zbMAjgAmh4+ueJmI XQW0yavukF2/aNXPBSVbF3M29lq72chJWk4Ru+sCkewTeOr2g7BAUOXQnuLXffB9 Bjf2GC7YNdalzBIclCBe4l/p4LcGaYqa1huK76ozcVhwvIicgH4a749QYHHn59KX rwz/fYhSEXdSjOT1LHGj =o5zW -----END PGP SIGNATURE-----
GEM-dev mailing list GEM-dev@lists.iem.at http://lists.puredata.info/listinfo/gem-dev
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hello,
Le 20/05/2014 09:04, Cyrille Henry a écrit :
Le 15/05/2014 13:26, IOhannes m zmoelnig a écrit : On 2014-05-13 12:58, Cyrille Henry wrote:
add a new 32 type for framebuffer (since GL_RGB_FLOAT32_ATI is not usable with intel GPU on linux)
wouldn't it make more sense to have a single float32 type on the patch-level ("RGB32"), and use whatever is available on the given GPU?
It would be nice that Gem choose what type to use, but I don't know
how to do this choice when many type are available. I think they are not equivalent depending on what you want to do. So the easiest solution is to test them on each combination of patch / hardware.
moreover RGBA32 is a 4 channel type, while GL_RGB_FLOAT32_ATI is only 3.
I support to have a real RGBA32 than only a RGB32 with only three channels. It is more easy for me to mix textures from framebuffer in shaders with a "real" alpha channel. That's why i often use RGBA for this purpose (instead of RGB32)... ++
Jack
cheers Cyrille
mfgasdr IOhannes
GEM-dev mailing list GEM-dev@lists.iem.at http://lists.puredata.info/listinfo/gem-dev
GEM-dev mailing list GEM-dev@lists.iem.at http://lists.puredata.info/listinfo/gem-dev
Le 20/05/2014 11:42, Jack a écrit :
...
I support to have a real RGBA32 than only a RGB32 with only three channels. It is more easy for me to mix textures from framebuffer in shaders with a "real" alpha channel. That's why i often use RGBA for this purpose (instead of RGB32)...
why do you need a 32bit type for texture?
cheers c
++
Jack
cheers Cyrille
mfgasdr IOhannes
GEM-dev mailing list GEM-dev@lists.iem.at http://lists.puredata.info/listinfo/gem-dev
GEM-dev mailing list GEM-dev@lists.iem.at http://lists.puredata.info/listinfo/gem-dev
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQEcBAEBAgAGBQJTeyOeAAoJEOuluecjw8GUcnUH/iczZe+enrNNkfwQTE7eeJBg ZwB8LOZos8L0BynKqgMaP5bLPT0aT1abJ6LsbnPd2WBkjn3UWSuOzZBraLjk0BQl CVdz06ZtEvk5T9aWP40sQ2inMVFOSvpxXryoPjRybmRMKboklQhkXEYiCMfJ2RO2 GjQtrvMUUSJivy+TxZkEcYOvRMm/qEJhhGoCdu+Z/PzBOKEEQKaFK9Jt0DGp6R01 6YhVu/170DoktXVbyXpzT5iiJVdvXMw9mZ3yCpywk2XRXcrPMUjvEGfTuFZlyz0O WqLEh9r8w7+nvmlUGd1tzbz31ENqSjpUASi51LU+Hyswg9TiZM0M9lf1E32oVkM= =kR0G -----END PGP SIGNATURE-----
GEM-dev mailing list GEM-dev@lists.iem.at http://lists.puredata.info/listinfo/gem-dev
Le 20/05/2014 11:46, Cyrille Henry a écrit :
Le 20/05/2014 11:42, Jack a écrit :
...
I support to have a real RGBA32 than only a RGB32 with only three channels. It is more easy for me to mix textures from framebuffer in shaders with a "real" alpha channel. That's why i often use RGBA for this purpose (instead of RGB32)...
why do you need a 32bit type for texture?
For exemple, for feedback. ++
Jack
cheers c
++
Jack
cheers Cyrille
mfgasdr IOhannes
GEM-dev mailing list GEM-dev@lists.iem.at http://lists.puredata.info/listinfo/gem-dev
GEM-dev mailing list GEM-dev@lists.iem.at http://lists.puredata.info/listinfo/gem-dev
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQEcBAEBAgAGBQJTeyOeAAoJEOuluecjw8GUcnUH/iczZe+enrNNkfwQTE7eeJBg ZwB8LOZos8L0BynKqgMaP5bLPT0aT1abJ6LsbnPd2WBkjn3UWSuOzZBraLjk0BQl CVdz06ZtEvk5T9aWP40sQ2inMVFOSvpxXryoPjRybmRMKboklQhkXEYiCMfJ2RO2 GjQtrvMUUSJivy+TxZkEcYOvRMm/qEJhhGoCdu+Z/PzBOKEEQKaFK9Jt0DGp6R01 6YhVu/170DoktXVbyXpzT5iiJVdvXMw9mZ3yCpywk2XRXcrPMUjvEGfTuFZlyz0O WqLEh9r8w7+nvmlUGd1tzbz31ENqSjpUASi51LU+Hyswg9TiZM0M9lf1E32oVkM= =kR0G -----END PGP SIGNATURE-----
GEM-dev mailing list GEM-dev@lists.iem.at http://lists.puredata.info/listinfo/gem-dev
-
Cyrille Henry -
IOhannes m zmoelnig -
Jack