There are many reasons why you’d want to lock your projects. Some of those may be artistic reasons and some of them might be business-related. In our last blog post, we talked about how you can use Project-level privacy and how you can use that to keep your whole project work behind a password. Now let’s dive into the next level of privacy you can implement: component-level privacy.
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.
