Project modules and groups
Append a project
Section titled “Append a project”Choose File → Append Project…, then pick a project from the library or a .zq file. In the Append dialog use the Module / Layers buttons:
- Module embeds the complete project in one layer. Its author-exposed Rack parameters, directly exposed layer parameters and Sources appear on that layer.
- Layers keeps the layer selection and Source mapping workflow, then places the imported layers in a group named after the source project.
New content goes to the front of the stack. Studio remembers your choice on this device; the initial choice is Module.
Compose modules
Section titled “Compose modules”Project Modules have a purple header and a package icon. Click the name to rename the instance, and use the disclosure control to hide or show its controls. Collapsing keeps playback running.
A module always follows the parent project’s canvas and playback timing. A portrait project can therefore become a module in a landscape composition without introducing a separate fixed-size frame.
The Input image setting defaults to Stack Below, which lets an effect process the image beneath it. Choose Project Background to use the embedded project’s own Background Source. Opacity and blending apply to the module’s combined image once.
Module controls use the same sliders, toggles, dropdowns, colors and vectors as other Studio parameters. Drag a slider or click its number to type a precise value. A module edit affects only that instance. Resetting a control restores the value saved in the embedded source project.
Use the parameter pins to drive module controls from the parent Rack. Click the eye beside a parameter in Layers to expose that same parameter in the parent’s Macros and Player. An active eye stays visible; an inactive eye appears when you hover over or focus the row. Hiding it removes only its macro entry. You do not need to make a Rack control or binding first. A driven parameter shows its live value and cannot be edited until its binding is removed; undriven vector components remain editable. Controls exposed inside the child project appear on its module card, but remain private to the parent Macros until you expose them there. Map an exposed module Source to a parent Source to share its camera capture or media decoding.
The mute button silences audio owned by the module while visuals and audio analysis continue. A mapped parent Source keeps its shared parent audio output.
Organize with groups
Section titled “Organize with groups”Use Create a layer group in Layers, or Put in new group in a layer’s More actions menu. Rename it inline, collapse it with its disclosure control, and use Move to folder to move layers into or out of nested folders. Each child retains its Layer Graph. Grouping creates no separate Rack or Layer Graph; child layers keep their existing Rack connections. Folder icons and indentation show membership. The group has its own visibility, opacity, blending and background input.
Break into Layers
Section titled “Break into Layers”The module header’s Break into Layers button replaces it in place with an editable group. Its canvas framing, output references, parent bindings and compatible playback state are preserved. Child Rack resources appear in a named parent Rack group and initially remain unexposed in Macros. Undo restores the module.
Update a module
Section titled “Update a module”For a Portal module, click its cloud button. Hover or focus the button to see the source, loaded revision and latest check status. For a local module, click its file button and choose a newer .zq version of the same project.
Compatible updates retain instance values and parent bindings. If controls or Source mappings became incompatible, Studio asks whether to keep the embedded version or remove the affected overrides and bindings. Each instance updates independently. A failed download or missing source leaves the embedded version usable; Undo restores the previous revision after an update.
Saving a .zq includes nested project snapshots and their assets. Studio, Player, Portal publishing and video export share this composition model. OBS and Wallpaper currently report these composition features as unsupported.