The drawback ib Processing its all the calculation is made in the CPU but I think, if you have not a problem with the number of instances and the number of pixel, you would be better staying in Processing to generate the drawing, using OSC and Spout to communicate with TD. to produce one or several images (as screen in Processing). In TD, you are basicaly in virtual 3D space, without any image and you use cameras, lights, textures etc. If you want to erase it, you have to redraw the screen. The primary object in Processing is the screen, “processed” by Java but your are every frame drawing on this screen, even with the 3D motor, ading points, lines etc. Beside the proper code, the object himself is not the same. Perhaps I say false thinks and more clever people can correct me. I think the metaphore beneath Processing is very different. I’m loosing myself in the maze of “I want to do like in the framework A into the framework B”Īctually, it is interesting for me for exploring what I can easy do here or easier To continue our conversation… As far as I understand, for instance, I couldn’t change the width of one line instance, and if I wanted a line drawn between two defined points… that would involve rotation, scale instead of “just” doing a line(point1,point2) like… I think that would be a big mess to handle things like that. The code (python, I …guess) should alter the whole things using for() loops, alter instances coordinates, width etc. I mean, I wouldn’t instantiate or draw other kind of things here. Good point, this is a project based on lines only. The master control would be the code, and the primitives, the instancing, the rendering would be SOPs. I’d have a code that could control all instances on a procedural way.I’d have a whole system able to instanciate lines, render them.The thing I guess here could be a system that could control a SOPs and Geom COMP and using instancing… programmatically. If this post makes sense to some of you, I’d be very interested by how you’d approach this.Įven if it ends by : “you know processing, use it for this kind of projects” I’d like to try to do it with td because for me, it is another way to explore with td, at first, and also because I could imagine some benefits.īut as far as I understand the very interesting tuto by Noah, we have to create a “kind of” framework at first (sop, tools, maybe line functions, ellipse and recreating everything) and then using it as a template and only modify the draw loop part of scripts, am I right ? I’m just trying to evaluate which direction to go for a project and what could be the benefits of td here vs processing (which I know). Maybe, the 2D way is very short-sighted as it could be done at the final stage (projecting 3D to 2D) It links python scripting and SOP but I don’t understand the benefits of instancing these whole big machine instead of drawing directly with python in a texture (which I don’t know how to do, in td, and which is maybe the reason I don’t understand the previously exposed “benefit”) I checked Drawing in Python - Noah Norman - YouTube Procedural can be done with pure python, and actually I’d like this (and make some processing/java port to py as exercises). What would be a good start for this with TD ? Here, I’d like to open a thread about drawing strategies. I’m trying to retrieve some coding feeling & strategies I already got with Max and procedural/text frameworks like Processing and Openframeworks. For those who follows the (not so interesting) story, I started to work with TD 2 months ago.
0 Comments
Leave a Reply. |