TDMorph will work with latest TD build or other 2020 series (and probably latest 2019 builds) but will NOT work with build 2020.24520, which had a bug that prevented proper functionality.
What can I do with it?
- Random search of states for parameters on any node or number of nodes.
- Random morphing between states using various different interpolation curves.
- Storing and retrieval of any arbitrary number of presets.
- Control of parameters and transitions with automatically generated UIs.
- Automatic storing, randomization and transformation of all parameters of arbitrary nodes.
- Auto-learn MIDI and OSC for every control in the generated UI.
- Full scripting control of all UI features via high-level commands.
- Global and local timing controls for every single parameter.
- Automatic creation of animations from stored presets.
- Flexible cueing system with follow actions and quantization.
- Pattern generation via scripting with the Patterns library.
- Algorithmic cueing via scripts.
And much more!
How does it work?
The architecture of TDMorph is fully modular, allowing you to access the core functionality as a whole or as separate building blocks. There are therefore various approaches you may take, which can be also interchangeably used. Here the most obvious:
- You can create an ElementsContainer UI, from where to control your parameters, using widgets and a set of buttons to perform various functions.
- You can create a PresetManager node, which is a UI-less object that allows you to control any arbitrary amount of nodes at once and is the backbone of the engine, suitable for advanced developers who want to make their own systems.
- You can create a SceneLauncher node, which is a UI that lets you create and control presets with follow actions.
Ok, I want to use it!
Great! TDMorph is a rather deep tool and requires some exploration to master but the basic functionality should be self-evident. Please check the full collection of tutorials to learn everything TDMorph has to offer in a structured manner. You can also folllow them here, at the end of the post.
TDMorph uses a number of shortcuts to perform various actions which you need to be aware of. Please see here the full list of shortcuts.
The philosophy behind the construction of TDMorph is that the UI is "dumb". This means that it is completely decoupled from core functionality, so when you interact with it you are invoking lower level commands that do not know what a button or a slider is, at least not implicitely. There is a plethora of high and low level set of commands that you can pass to control all objects in TDMorph, using Python.
In general, a node in TDMorph has always 2 extensions:
- Core extension (Core UI-less functionality)
- UI extension (deals exclusively with operations for UI elements)
UI extension methods
This category of commands are to control TDMorph via the UI. These do not talk with the core nodes in the system but with the widgets. To give an example: you could locate an ElementsContainer in TDMorph and then target a specific element of the UI you want to control, that being a button, a parameter or a widget.
To access an ElementsContainer you need to invoke it by number (counting from 1), so assuming you have only 1 ElementsContainer in your TDMorph workspace, you can invoke that element using:
elementsContainer = op('TDMorph').GetContainer(1)
Now, you can control all the UI elements of that object. So if you would like to change its morphing time via the UI you can do:
Core extension methods
The second category of commands are to communicate directly with the objects, not with the UI. These methods are the ones used by the system under the hood, so you can do much more with them. These are meant for more advanced developers that want to build systems on top of the toolbox. To give an example: you could locate an ElementsContainer and then delete it, by doing this:
elementsContainer = op('TDMorph').GetContainer(1) elementsContainer.Delete()
Please refer to the help files with all available methods in the archive. If you plan to extend or use TDMorph as a bedrock for your own implementations, please read carefully the instructions about architecture in the source code, so you create programs that adhere to its philosophy. This is important because will make things easier to mantain as TDMorph evolves.
Since version 2, TDMorph comes with a "Patterns" library, which I wrote based on the homonimus library in the SuperCollider language. Patterns were conceived in the SuperCollider programming language as a "rich and concise score language for music". See: https://doc.sccode.org/Tutorials/A-Practical-Guide/
The need for values generation in TouchDesigner moved me to embrace this idea and further create this library for the TDMorph toolkit and TouchDesigner in General. It is not a port but a reverse engineering of the original SuperCollider version, using Python's great support for generators and lazy evaluation.
Feel free to dig around and please suggest improvements if you see something that could be done better in the networks or the code. Also please get in touch if you see I did something stupid somewhere (which is bound to be the case). To report these, please use the issue tracker in the Github repo:
You are more than welcome to propose additions to the toolkit. Feel free to build your own tools based on TDMorph and get in touch if you want to propose making them part of the official distribution. Please make sure to check carefully the obligations in the license if you plan to make your work available to others.
The motivation to share this tool stems from the wonderful sense of comradery that the TouchDesigner community in general hasand by the brilliant philosophy of Derivative as creators of the TouchDesigner software. I hope that the ethos that characterizes TD continues and that this system helps you in expanding your capabilities as a maker.
About the license
Since we are artists/programmers and not lawyers, I trust you will give credit where credit is due and respect the licence: GNU General Public License v3 (GPL-3). See this link with common questions if you wonder what it implies. This means that if at some point you would like to use any part of this toolbox in a commercial endeavour for which you do not want to disclose the source code, you will get in touch first, so a fair arrangement can be made.
You can support this project by making a donation. Any contribution is appreciated!