Project Inputs
A Project Input is a named source owned by the project. Layers, shader graphs, 3D scenes, and bindings can all refer to its stable identity. Replace the source once and those consumers stay connected.
Common input kinds
Section titled “Common input kinds”- Images and textures
- Video
- Image sequences
- Cameras
- Audio files and video audio
- Microphone and system audio
An input declares the kinds it accepts. A visual input in the official starters usually accepts image, video, image sequence, or camera. An audio-reactive input usually accepts audio, video audio, microphone, or system audio.
Replace an example source
Section titled “Replace an example source”- Find the named source in Rack.
- Choose an existing compatible source, import a local file, or select an available device.
- Check the Stage result and any audio-driven controls.
- Save the project only after the new source is working.
The Project Input is the connection point; the imported file is one possible source for it. This is why a library add flow can ask you to map the input instead of silently copying demonstration footage.
Text and sequences
Section titled “Text and sequences”ZoneQ does not provide native editable text or automatic text segmentation. Use a replaceable image, video, or sequence containing your typography.
An image sequence is one explicit Project Input kind with ordered frames and playback settings. It is not a curve, keyframe timeline, or list of unrelated images. See Image sequences.