The Great Inversion
2 Likes
This is amazing work. Thank you for developing it and for writing it up so clearly.
The “inversion” framing is really useful because it names a problem I keep running into with TouchDesigner: the .toe file is an incredibly powerful live environment, but it can also become a difficult place to hold structure, memory, documentation and version history.
What feels important here is that this is not just about adding AI to TouchDesigner. It is about making TouchDesigner projects legible enough that AI can participate meaningfully. Without that legibility, AI could easily just accelerate confusion.
I’m especially interested in trying this with some of my existing TouchDesigner work, not initially as a way to generate new systems, but as a way to document and better understand what is already there. I have projects where the visual outcome is compelling, but the internal logic becomes hard to hold once the network gets layered and nested. Using something like this to read, describe and externalise those systems could be very valuable.
So I read this less as “AI will build TouchDesigner projects for us” and more as a shift toward making TouchDesigner projects more readable, portable and traceable.
Really exciting. Thank you for sharing it.
1 Like
Thank you for the thoughtful response @TA73. I agree, this is fundamentally about improving the clarity of our collective development practices. I chose the name “Embody” to articulate the intent of the component: to “represent (a TouchDesigner project) in a physical form.” Or, more specifically: in linguistic form.
Thanks @dylanroscover, that makes sense. Looking forward to trying it.
1 Like
@dylanroscover This looks really powerful. I’m looking forward to diving into this.
1 Like