From TouchDesigner Documentation
Jump to: navigation, search

Each operator has an attached Python "storage" dictionary. Values stored in this dictionary are persistent, and saved with the operator. The storage dictionary contents may be manipulated directly with methods such as OP.fetch() or described below, or examined with an Examine DAT.

The storage dictionary is accessible directly via There are also a number of utility functions associated with storage, which can be found here: OP Storage.

Automatic Cooking[edit]

When an immutable element of storage changes, expressions that depend on it will automatically cook. For information about cooking of mutable elements (lists, dicts, sets), see deeply dependable collections.

Preserving in Files[edit]

Storage is saved with .toe and .tox files and loaded on startup.

Also see: StorageManager Class, Storage in OP_Class.

Any of the procedural data operators. OPs do all the work in TouchDesigner. They "cook" and output data to other OPs, which ultimately result in new images, data and audio being generated. See Node.

Storage is a python dictionary associated with any operator, used to keep user-specified data within the operator.

TOuch Environment file, the file type used by TouchDesigner to save your project.

TouchDesigner Component file, the file type used to save a Component from TouchDesigner.