Presentation of iterative experimentation and second draft of written response.
(Jan 28,2025)
In the second week, I rethought my experiment direction. TouchDesigner is designed to provide a smooth and logical workflow for real-time multimedia creation. However, during the first week, I noticed that when loading large files, the software would crash or lag.
This made me wonder: Could “crashes” and “errors” become a starting point for creative exploration?
So, I decided to focus on TouchDesigner’s crashes and errors and explore their potential as creative tools.
First, I attempted to trigger software crashes in different ways, such as adjusting extreme parameters or overloading the system with too many components, to test TouchDesigner’s limitations and boundaries. Then, I collected these crash screens and recordings and put them back into TouchDesigner, using its own functions for iterative experimentation.
First, I triggered crashes by setting extreme.
Next, I tried adding a subdivision component and continuously adjusting its parameters.
Then, I experimented with modifying dynamic parameters.
Then, I tried stacking a large number of components to trigger a crash.
Finally, I triggered a crash by using data mismatches. I inserted plugins created with different versions of TouchDesigner into my current project, and the software immediately crashed.
Finally, I put the collected crash visuals along with a normal interface into TouchDesigner. I tried iterative experiments, starting with basic transformations and gradually increasing complexity by adding more components or adjusting parameters.
Draft2:
Leave a Reply