There is also the [gemvertexbuffer] object to draw a mesh. See help and examples about it. ++
Jack Le 05/08/2016 à 19:26, cyrille henry a écrit : > hello, > > for now, i thik the most optimized solution is to : > use a tabdump extern to send the data to a pix_set object > use a shader to distord a mesh_square/mesh_line geometry according to > this texture > > I have plan to add a message to pix_set object to read directlly the > table to remove the list bottleneck (and an external dependency) > I would also love to have time to include this functionality to > mesh_square... > > > But if you have only few thousand line to draw, [curve 2] object (with a > [res 2< message) and a loop will be fine on any recent computer. > (or GEMglBegin etc) > > cheers > c > > > > Le 05/08/2016 à 18:56, Daniel Iglesia a écrit : >> I have (large, e.g. size >512) quickly-varying arrays of data in Pd >> that I'd like to turn into vertices/lines in GEM. How do I either >> >> 1) draw a large mesh (such as with jit.gl.mesh) without having to, for >> example, specify a [polygon] with 512 inlets >> >> or >> >> 2) send individual drawline commands to GEM (without having to, for >> example, use GEMglBegin with 512 GEMglVertex3f objects in a row), e.g. >> [drawline x y z x y z ( >> >> (the only other idea I have is to use a vertex shader and send in >> lists of point data as a parameter to that, which hopefully doesn't >> have a bottleneck) >> >> thanks for any advice, Dan >> >> >> _______________________________________________ >> [email protected] mailing list >> UNSUBSCRIBE and account-management -> >> https://lists.puredata.info/listinfo/pd-list >> > > _______________________________________________ > [email protected] mailing list > UNSUBSCRIBE and account-management -> > https://lists.puredata.info/listinfo/pd-list _______________________________________________ [email protected] mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
