Our industry thrives on user inputs, interactions, and data streams. While these are normally exciting things to work with they can also be areas in your project where errors could pop up. Someone might upload a broken asset or incomplete data could come down an API pipe and if you aren't able to correctly catch those errors and log them, report them, or deal with them programmatically, you could end up with a broken system. The Error DAT can come to the rescue in this case!
Working with GitHub and TouchDesigner can be a real adventure – and what I hear most often is why and how. A bit ago I did a little write-up about working with git and Touch, but realize that’s still a bit intimidating for folks.
Something I hear often is the difficulty in doing TouchDesigner blob tracking. “It’s too slow!” or “the tracking isn’t working!” or “I don’t know how to use it!”.
We’ve all been in installations where you need to send textures between apps or process. It may be because of limitations of a process, maybe because we’re using different apps to do different processes.
