Hello
Iohannes is right.
The example i pointed out consumes quite some cpu-power.
but: in the help-browser you´ll find another example, that takes the
texture id of a framebuffer and allows to "crop" the texture. in this
example, the work is done by the gpu with the help of glsl-shaders.
Gem/examples/12.multi_screen_projection/02.nfp-help
regards peter
Am 27.04.15 um 23:33 schrieb IOhannes m zmölnig:
On 04/27/2015 11:00 PM, hi wrote:
Thanks peter
that looks promising and might fit to the rest of my patch.
but keep in mind that the texture->pix transfer is rather costy in terms
of CPU (well, actually in terms of transfer time), whereas doing
texture-only operations (e.g. using [pix_coordinate]) will be *very fast*.
gfnmsdr
IOhannes
_______________________________________________
[email protected] mailing list
UNSUBSCRIBE and account-management ->
http://lists.puredata.info/listinfo/pd-list
_______________________________________________
[email protected] mailing list
UNSUBSCRIBE and account-management ->
http://lists.puredata.info/listinfo/pd-list
