Overview
Wireless Link takes a signal as input and exposes it as output without having to draw a visible wire across the graph. You can place the Wireless Link anywhere, connect it to the source, and several Wireless Links (via right-click → Same Wireless Link) can share the same source.
Typical case: a MediaIn that 5-6 different chains need. Instead of drawing 5 wires from the MediaIn in every direction, place 5 Wireless Links tied to the same MediaIn = a much more readable graph.
Where to find this node
- Effects Library:
Tools > Misc > Wireless Link - Quick add: right-click in the Node Editor →
Add Tool > Misc > Wireless Link
How it works
- Creation
- Add a Wireless Link and connect it to the source. The node appears with its input filled in.
- Output usable anywhere
- Connect the Wireless Link as an input to any other node, wherever it sits in the graph.
- Several linked Wireless Links
- To share the same source in several places, duplicate the Wireless Link (the new ones point to the same source). This gives you several "local" output points in the graph.
- No performance cost
- Wireless Link is purely a connection alias. No extra computation compared with a physical connection.
Setup
MediaIn used in 5 places:
Without Wireless Link (spaghetti graph):
MediaIn ─────┬───────────────────────► Process A
│
├───────────────────────► Process B
│
├───────────────────────► Process C
│
├───────────────────────► Process D
│
└───────────────────────► Process E
With Wireless Link (clean graph):
MediaIn ─► [WL]
↓ (invisible local branch)
[WL] ──► Process A
[WL] ──► Process B
[WL] ──► Process C
[WL] ──► Process D
[WL] ──► Process E
By convention, you place the WLs next to each consumer.Controls tab
- Input (connection)
- The source the Wireless Link is tied to. Physically connected as the input of the WL.
- Output
- An output you can use like any other node output.
No other significant parameters. Wireless Link is intentionally minimalist.
Use cases
- Multi-consumer source - a MediaIn / Loader used in 5+ places = WLs to avoid spaghetti.
- Complex comp with distant branches - a roto / matte that has to feed several sub-comps far apart in the graph.
- Shared Camera 3D - a single Camera 3D used by several Renderer 3D nodes (multi-pass), WLs avoid long wires across the graph.
- Common background - the same Background used for several Merges in different places = one WL per Merge with a shared source.
- Readable templates / macros - Wireless Link improves the readability of templates shared within a team.
- Side-comp workflow - a preprocessing chain feeding a main composite without spaghetti.
Tips
- No performance cost - a purely organizational alias. Use it without hesitation.
- Name your WLs for clarity - rename each WL with a descriptive name (e.g. "WL_BG_in") = even more readable.
- Place it near the consumer - the WL should sit near the node that uses it, not near the source. Otherwise the visual benefit disappears.
- Combine with Underlay - Underlay groups things visually, Wireless Link routes the flows. Together, an extremely clean graph.
- Not for modifying the flow - the WL only routes. If the signal needs to be modified, put the modifying node in the chain, not through a WL.
- Updates propagate automatically - change the source of the WL = every consumer sees the change instantly.
- For workflows with multiple reads, an alternative: chain directly and accept a few long but visible wires. A matter of personal preference.
