I designed a large-scale kinetic sculpture “Reflexion” - a wall of 91 programmable mirrors. All movements are defined in grasshopper script, compiled as .txt file (describing servo positions in time). By now, I only had this “hard coded” possibility. But me and my friend @makermatty developed MQTT plugin, so I can stream live data to my sculpture and move it directly from Grasshopper. What’s more, I can use external controller (positioner, accelerometer…) and access data from Grasshopper, use it to manipulate geometry and send data directly to mirrors. But we got noticable latency (in comparsion with direct connection between controller and mirrors). So…
I doubt that many people use it for this purpose, but still. I would like to ask someone more experienced than me about speed issues. I don’t understand Rhino/Grasshopper processes enough to optimize it to minimize latency.
Subscribe / Publish components are fast. I noticed that whenever I use timer, all the GH definition run slower (also in other definitions). Is there something that I can do differently, use different approach?
The question is simple - does it make sense to buy better computer, so Grasshopper get / set data faster? Or is it better to solve the problem on software side? Does someone have experiences with “live streaming” from Grasshopper and knows, how to deal with speed / latency issues?
Sharing the full script doesn’t make sense, because our MQTT plugin requires some dll dependency and is not ready for release yet So at leaset a scheme: