Projects

Projects help you organize your work and store device configurations for generating Device Labels. A project combines your snapshot files with your stage equipment setup.

What is a Project?

A project contains:

• Name and description: Identify the project (e.g., "Summer Festival 2025 - Main Stage")
• Device configuration: Your stagebox and WING mixer setup
• Linked files: Snapshot files associated with this project
• Version history: Track changes to your device configuration over time

Projects are especially useful for:

• Generating Device Labels with your specific equipment setup
• Keeping related snapshots together
• Reusing device configurations across multiple shows
• Tracking configuration changes over time

Note: Projects require a Wing Tools account. Device configuration can also be stored locally in your browser if you're not logged in.

Creating a Project

1. Navigate to Projects from the main menu
2. Click New Project
3. Enter a project name (required)
4. Optionally add a description
5. Click Create

Your new project appears in the project list, ready for configuration.

Device Configuration

Device configuration defines your stage equipment setup. This is required for generating Device Labels that show accurate channel assignments, and it also drives Multi Device Signal Flow.

Opening the Project Editor

1. Select a project from your project list, or click Open Project on its card
2. The Project Editor opens on a canvas — this is where you author your rig: mixers, stageboxes, personal monitor stations, hubs, and the cables between them

The Project Editor has two modes, toggled at the top of the page:

Note: Not logged in? Click Configure Devices from the Routing Generator to open the same editor in local (browser) mode. Your configuration is stored in this browser only and is not synced across devices. Log in to save to a project with full version history.

Adding a Device

Click + Add Device to open the Add Device dialog. It lists every supported device grouped by connection type (AES50 · Behringer/Midas, AES50 · Midas Pro, StageConnect, Personal Monitors, Hubs & Distribution), with a badge on each entry showing its transport(s) (AES50, StageConnect, ULTRANET). Click a device to add it to the canvas with the correct type already set — there's no separate type dropdown afterward. Devices marked Beta have specs sourced from manufacturer documentation and aren't yet hardware-verified.

Note: In Free-tier Simple mode the canvas is limited to one mixer and one stagebox on AES50-A, added with a single + Add Stagebox button instead of the full dialog. Switch to Advanced mode (Basic tier and above) to use the full Add Device dialog and add unlimited devices on any bus.

Cabling Devices

Drag from a device's port handle to another device's port handle to connect them. Port handles are color-coded by transport so you can tell them apart at a glance: AES50 ports render light blue, StageConnect ports render pink. When a device has a configurable Source (for example a P24Hub's SOURCE SELECT), the port currently selected as that source is highlighted with a gold outline and badge.

Misconfiguration Warnings

A device node shows a small warning triangle when Wing Tools detects a likely misconfiguration — hover the triangle to see the reason. Examples:

• A device has no cable connected to any port
• A mixer has no model selected (Desk/Rack/Compact)
• A P24Hub's configured Source (SOURCE SELECT) isn't actually cabled
• A Powerplay monitoring station (P16-M/P24) has no feed connected

Hard connection errors from validation (mismatched transports, incompatible StageConnect roles, over-capacity AES50 daisy chains, and similar) also surface as warning triangles on the affected devices, in addition to being listed in the editor's issues panel.

Adding Stageboxes (AES50)

To add a stagebox on an AES50 bus, use + Add Device, pick the stagebox from the AES50 · Behringer/Midas or AES50 · Midas Pro group, then cable it to the mixer's AES50-A/B/C port (or to another stagebox, for a daisy chain). Set its properties in the device panel:

• Name: A descriptive name (e.g., "Stage Left", "Drum Riser")
• Device Type: SD8, SD16, SD32, DL8, DL16, or DL32 (plus the Midas Pro and P24HUB device families)
• Position in the daisy chain: Determined by how devices are cabled, not a manual field
• Output Switch: Which return channels the device outputs

Output Switch Positions

For SD8/DL8 and SD16/DL16 devices, set the output switch position to match your physical device:

SD32/DL32 devices have fixed outputs (1-16) and don't require this setting.

Daisy-Chain Positions

When multiple stageboxes connect on the same AES50 port, their input channels are offset:

Set the position to match your physical cable order.

Adding StageConnect Devices (Basic+)

StageConnect uses a different topology than AES50 — devices chain from a single MASTER port on the mixer through each device's SLAVE/MASTER ports. Pick a StageConnect device from the Add Device dialog and cable it to the mixer's StageConnect port (or to another StageConnect device further down the chain), then set its properties in the device panel:

• Name: Descriptive name
• Device Type: DN4888, DN4816-I, DN4816-O, FLOW 4VIO, SC88, SC16-I, SC16-O, SC-U, or P24HUB
• Mode: Operating mode (depends on device type)

Supported StageConnect devices:

Note: StageConnect device configuration (any bus other than AES50-A) requires Basic tier or above. Free-tier projects are limited to a single device on AES50-A.

Personal Monitoring Stations — Powerplay 16 & 24 (Beta)

Wing Tools can label the Behringer Powerplay personal monitor mixers your musicians use, so each performer gets a printed legend of what every channel on their station is. You add the station like any other device and cable it to whatever feeds it — Wing Tools works out the rest.

To add one:

1. Add the station and pick Powerplay 16 (P16-M) or Powerplay 24 (P24) as the device type.
2. Cable it to its feed:
   • A P16-M connects to the ULTRANET Out of the stagebox that carries its monitor mix (SD8/DL8/SD16/DL16/SD32/DL32), or to a P24Hub.
   • A P24 connects to a P24Hub over StageConnect.

The channel names come entirely from your snapshot — you never type them in. Wing Tools follows the cable to the upstream device and reads the console's output routing, honouring each device's wiring:

• A P16-M on a DL16 reads that stagebox's AES50 outputs 33–48 (the WING's Powerplay send range). If you route BUS 3 to AES50-A outputs 33/34 and call it "IEM Drums", channel 1 of the P16-M shows IEM Drums.
• A P24 on a P24Hub reads whatever the hub's SOURCE SELECT distributes (StageConnect ch 1–24, or AES50 ch 25–48 / 33–48). You can daisy-chain P24Hubs over AES50 (each hub's AES50 B out to the next hub's AES50 A in); every hub forwards the same console channels, so P24s on a downstream hub label correctly. In the AES50 16-channel mode (ch 33–48) the P24's faders 1–8 are the eight mono channels 33–40 and faders 9–12 are the four stereo/dual groups 41–48 — the label follows this hardware mapping automatically.
• A P16-M on a P24Hub's ULTRANET Out shows what the hub actually sends over ULTRANET, which depends on the hub's SOURCE:
  • AES50 16-channel (ch 33–48) or ULTRANET source: the 16 channels pass through directly.
  • AES50 24-channel (ch 25–48) or StageConnect source: the 24 console channels are summed in consecutive pairs to 12 mono channels (25+26 → 1, 27+28 → 2, …). The label stacks both source names in each cell (e.g. KCK / SNR) so you can see what is summed onto each fader.

Monitor legend: stereo or mono

Wing Tools infers stereo groups from the snapshot: two channels fed by the left and right of the same stereo bus render as one stereo pair (e.g. 1/2 Keys (st)). By default a P16-M shows 16 mono strips and a P24 shows 12 stereo groups — but you can override it per device from the Monitor legend control:

Use Copy / Paste to reuse a setting on another station, or Apply to all to push it to every monitoring station in the project at once.

Note: Powerplay devices are Beta — their specs come from Behringer's documentation and haven't been verified on hardware yet.

Configuring the WING Mixer (Optional)

Add your WING mixer to include its local I/O on Device Labels:

1. Click + Add Mixer on the canvas toolbar
2. Select the mixer node and choose its model in the device panel:
   • WING Desk: 8 local inputs, 8 local outputs
   • WING Rack: 24 local inputs, 8 local outputs
   • WING Compact: 24 local inputs, 8 local outputs
3. Optionally give it a custom name

Note: A mixer with no model selected shows a misconfiguration warning triangle, since its physical layout can't be resolved.

Setting a Mixer's Snapshot

Each mixer needs a snapshot — it provides the channel names and routing that Signal Flow and Device Labels read. To set it, select the mixer in the Project Editor and use the Snapshot section of the device panel.

You choose how the snapshot is attached:

Wing Tools persists the snapshot's file name and the date it was added, shown in the device panel (File and Added) and on the mixer node — so you can always trace which snapshot a project ran on.

Tip: You can also set or change a mixer's snapshot when you open a project straight from the Routing Generator — it's no longer read-only there.

Linking Files

Beyond the main snapshot, you can link additional files to a project for organization.

Adding Files to a Project

1. Go to My Files
2. Select the file(s) you want to link
3. Click Move to Project or use the project dropdown
4. Select the target project

Removing Files from a Project

1. Open the project
2. View linked files
3. Click Unlink on the file you want to remove

Files are not deleted when unlinked; they return to your general file library.

Configuration Versioning

Projects track changes to your device configuration over time.

Creating a Version

When you make significant changes to your device configuration:

1. Click Save version in the Project Editor toolbar
2. Optionally add a note (e.g., "Added drum riser box")
3. Click Save

The new version is timestamped and stored.

Viewing Version History

1. Open the project in the Project Editor
2. Click Versions in the toolbar
3. See all saved versions with timestamps and notes

Restoring a Previous Version

To go back to an earlier configuration:

1. Open the Versions panel
2. Find the version you want
3. Click Restore
4. Confirm the restoration

The current configuration is replaced with the restored version. You can always create a new version before restoring if you want to preserve the current state.

Using Projects

Per-Project Actions

Each project card on the Projects page has a row of action buttons:

Project Selector in Tools

When using Routing Generator with Device Labels output:

1. Look for the Project dropdown in the toolbar
2. Select your project
3. Device configuration is automatically loaded
4. Generate Device Labels with your equipment setup

Generating Device Labels

With a project selected:

1. Go to Routing Generator
2. Select Device Labels as the output format
3. Your project's device configuration is pre-loaded
4. Upload or select a snapshot file
5. Click Generate

The generated PDF shows labels for all configured devices with channel names from your snapshot.

Project Limits by Tier

Project and device limits depend on your subscription:

Note: Basic tier shares Free's single-project limit — Basic's benefit for Projects is unlocking unlimited devices, all AES50 buses, and StageConnect on that one project. Premium is the first tier to unlock multiple projects.

Free Tier Limitations

Free tier users can:

• Create one project
• Add one device on AES50-A
• Generate Device Labels for that single device

This is perfect for simple setups with one stagebox.

Basic Tier

Basic unlocks, on your one project:

• Unlimited devices per project
• All AES50 buses (A, B, C)
• StageConnect device support
• Multiple devices in daisy chains

Premium Tier

Premium unlocks:

• 10 projects
• Everything in Basic on each of them

Pro Tier

Pro provides:

• Unlimited projects
• All Premium features
• Priority support

Next Steps

• Routing Generator: Generate routing documentation and Device Labels
• My Files: Learn about file storage and organization
• Signal Flow: Visualize your routing interactively

---

Questions? Check the Reference section for troubleshooting tips.