Keep Local and local tools
Not everything in a shared network should be shared. A path to a .tox may exist on one machine
only; each machine has its own cameras and MIDI devices; a tool you summon into the network may
need what only your computer has. Four rules cover this:
| Rule | What it does |
|---|---|
| Keep Local | Never sent, dropped when it arrives, not compared, left alone by Sync Zone |
| Always Sync | Sent wherever your network editors are, even from a network nobody shows |
| Not checked | Syncs as usual, but the drift check leaves it out |
| Local tools | An operator tagged as yours alone: never sent, compared or repaired |
The first three live in the zone's Keep Local table, which belongs to the host: whoever joins takes the host's, a change anywhere goes through the host to everyone, and a zone sent with Sync Zone carries it. The host's Partners May Edit Keep Local (on by default) decides whether Full Edit partners may change it; Observe and Adjust Parameters never may.
Kept local by default
- External .tox parameters, on every COMP: a path to a
.toxmay exist on one machine only. - The Collab Zone COMP's own Clone parameters: a zone cloning a master outside it would overwrite synced edits. Clones inside the zone sync.
- Hardware device operators, every parameter: Video and Audio Device In and Out, MIDI, serial, DMX, LTC, depth cameras and sensors, VR, joysticks and tablets, laser DACs, camera tracking. Not NDI, Spout, Syphon or streams.
If everyone has the same files (a shared folder or a network drive), switch External .tox to Sync in the TDXCollab window; the same goes for Hardware devices when everyone has the same ones.
Keep Local
Drop a parameter on the TDXCollab chip in the main menu bar, or on the TDXCollab window, and choose to keep it local:
- on this operator,
- on every operator of its type,
- wherever a parameter of that name is in the zone,
or to sync it again. Drop a whole operator to keep every parameter of it, or of every operator of its type, local; its flags, wires, place, name, colour and comment still sync. Then drop one of its parameters and choose Sync for an exception.
The TDXCollab window lists every rule with a rule button (Local, Sync or Not checked) and × to remove it. Open Table opens the table itself to edit by hand. A rule follows its operator's renames and goes with its delete.
Always Sync
For what you want sent wherever your network editors are: a table a control panel writes into, a COMP you edit from a floating window, a parameter a UI changes in a network nobody shows. Drop it on the chip:
- an operator offers "Always sync:
noise1": every edit of it; - a COMP also offers "Always sync:
ctland what is directly inside": the COMP and the operators one level inside it; - a parameter offers "Always sync:
periodonnoise1": that parameter alone.
Choosing it again ends it. Keep Local still wins: a parameter kept local stays local on an operator that always syncs. An operator made or deleted inside an always-synced COMP is sent only while a network editor shows that COMP.
Not checked
For what may differ between the copies on purpose: a scratch COMP, a COMP a local script fills in,
a parameter a script keeps changing on each side. Its edits sync as usual, but the drift check
leaves it out, so it never shows as drift and Resolve Drift never repairs it. Drop it on the chip:
"Not checked: noise1" (the whole operator), "Not checked: scratch and everything inside" (a
COMP, at any depth), or "Not checked: seed on noise1" (one parameter). The Collab Zone COMP
itself is always checked, and Sync Zone still sends everything.
Local tools
Tag an operator TDXCollab:ignore (Common page, Tags), or with one of the tags you list in Ignore
Tags (Zone page), and it is yours alone: a tool you bring into the network that needs a global
shortcut or a palette only you have, and would show errors on the other side.
- It, everything inside it and every operator docked to it are never sent, never compared and never repaired. Wires from it into synced operators stay yours too.
- Sync Zone sends your zone without your local tools. When a partner's zone replaces yours, theirs are dropped and yours are put back into the new zone, at the same place.
- Tag it before it lands in the zone (a
.toxthat carries the tag does): tagging it later takes back nothing already sent. - Tags are case-sensitive. On the Collab Zone COMP itself they mean nothing.