Library and assets
The Library view in Tato Studio. The node types, generators and views a project can use, and its assets, pictures, video, models and data, which you import, organize and choose from a node's Asset pins.
The Library is everything the project can use. Its Show menu, in the view’s header, switches between four lists: node types, generators, views and assets.
Node types and generators
Section titled “Node types and generators”Node types lists every node the project can place, grouped by where it comes from: the project’s own nodes, each module it added, and the Python packages it installed. Select one to see its description, its pins with their types, and its settings. These are the same nodes the Add node search offers in the graph.
Generators lists the project’s graph generators: Python functions that build a group of nodes and wires, which you place from the Add node search as a subgraph. See Streams as compositions.
Views lists the panels the project and its modules bring to Studio, beside Studio’s own: an operator panel with buttons for a show, a scope for a sensor, a map. Each says what it shows and where. A view can be an area of the window, which you pick from any area’s view menu, or a node in the graph whose pins feed it, which you place from the Add node search like any other node.
Assets
Section titled “Assets”An asset is a file the project uses: a picture, a video, a sound, a 3D scene, a model’s weights, a lookup table, a simulation. Each lives in the project’s folder, so the project carries it wherever it goes.
Import
Section titled “Import”Show Assets and press Import asset…, then choose one or more files. Studio copies each into the project, into a folder for its kind, and lists it as a card with a preview, its format and its size. The folders down the side narrow the list, and the search finds an asset by its path.
Use one in a node
Section titled “Use one in a node”A node that reads a file has an Asset pin, which asks for one kind of asset: a video, a scene, a model. Click the pin’s value, on the card or in Properties, and the Library opens as a picker showing only the assets of that kind. Choose one, or import a new file from the picker, and it’s chosen at once.
The node is given the asset itself, not its path. In a node’s code, ctx.asset_content_path(asset) gives the file to open. See the Python SDK reference.
Rename, move and delete
Section titled “Rename, move and delete”Each card’s ⋯ menu has:
- Rename asset gives the file a new name in its folder.
- Move asset moves it to another folder of the project, which is made if it’s missing.
- Delete asset removes it from the project.
Nodes that read an asset keep reading it after a rename or a move: each asset keeps one identity for its whole life, stored beside it in a small .asset.json file. An asset a node still uses can’t be deleted until nothing uses it.
Each of these is an edit on the project’s history, so Edit › Undo takes it back. The history records an asset by its .asset.json file, not its bytes, so undoing a delete brings the file back only while it’s still on disk.
Assets from modules
Section titled “Assets from modules”A module you add can bring assets of its own, such as the scene a sample uses. They stay in the module’s folder, inside imports/, and its nodes read them from there.
A project’s cover
Section titled “A project’s cover”The cover on a project’s card in the Projects window is a picture you choose in the project’s Details, in the Projects window.