--- title: Source Management description: Remap physical input source properties between I/O groups in your WING snapshots --- # Source Management (Basic) Source Management lets you remap physical input source properties between I/O groups in your Behringer WING snapshots. When you move a show between venues with different stagebox setups, use this tool to transfer gain, phantom power, phase inversion, names, colors, and other source settings from one group to another -- without manually re-patching every channel. > **Note**: Source Management requires a Basic, Premium, or Pro subscription. ## Overview The WING mixer assigns source properties (gain, phantom power, phase inversion, stereo mode, name, color, icon, and tags) to each slot in an I/O group. When you change venues -- say from a room with an AES50-A stagebox to one using only local inputs -- all your carefully configured source settings are stuck on the wrong group. Source Management solves this by copying source properties between groups. For example, you can copy everything from AES50-A slots 1-24 to LCL slots 1-8 and AES50-B slots 1-16, remapping your entire input list in seconds. The tool also updates channel source references and matrix direct patch references so your channels follow the sources to their new locations. ### Common Use Cases - **Venue change**: Move a show file from a venue with AES50-A stageboxes to one using AES50-B or local inputs - **Stagebox swap**: Migrate sources when replacing a damaged stagebox on a different AES50 port - **Input consolidation**: Combine sources from multiple groups into a single group after soundcheck - **Source backup**: Copy source configurations to a second group as a safety net ## Getting Started ### Prerequisites - A Basic, Premium, or Pro subscription - A WING snapshot file (`.snap`) -- either uploaded from your computer or selected from your [Files library](02-my-files.md) ### Basic Workflow 1. **Upload a snapshot** -- Drag and drop a `.snap` file, use the file picker, or browse your Files library 2. **Parse the snapshot** -- Click **Parse Snapshot** to extract source group data 3. **Select source and target groups** -- Choose which group to copy from and which to copy to 4. **Configure mappings in the CopyTable** -- Select which sources and properties to copy 5. **Set source actions** -- Choose whether to keep or reset original source slots 6. **Save as a remapping card** -- Review the before/after diff summary 7. **Add more remappings** (optional) -- Create additional cards for other group pairs 8. **Generate** -- Download the modified snapshot or save it to your Files library ## Source Groups The WING organizes physical and virtual inputs into source groups. Each group has a fixed number of slots with configurable properties. | Group | Display Name | Type | Typical Slot Count | Description | |-------|-------------|------|-------------------|-------------| | LCL | Local | Physical | 8 | Built-in local inputs on the console | | A | AES50-A | Physical | 48 | AES50 port A (stagebox) | | B | AES50-B | Physical | 48 | AES50 port B (stagebox) | | C | AES50-C | Physical | 48 | AES50 port C (stagebox) | | AUX | Aux Ports | Physical | 6 | Auxiliary analog inputs | | SC | StageConnect | Physical | 32 | StageConnect digital inputs | | AES | AES3 | Physical | 2 | AES3 digital inputs | | USB | USB Audio | Internal | 48 | USB audio interface inputs | | CRD | External Card | Internal | 64 | Expansion card inputs | | MOD | Internal Card | Internal | 64 | Internal processing card inputs | > **Note**: The actual slot count depends on your console firmware and connected hardware. The parser reads the exact count from your snapshot file. ### Group Capabilities Not all groups support every property. For example, internal groups like USB and CRD may not support gain or phantom power. When you select a target group that lacks certain capabilities, those property columns are automatically disabled in the CopyTable and a warning appears in the group selector. ## Selecting Groups After parsing your snapshot, the group selector appears with two dropdowns: 1. **Source Group** -- The group to copy properties *from* (e.g., AES50-A) 2. **Target Group** -- The group to copy properties *to* (e.g., LCL) Groups are listed in canonical WING order: LCL, AES50-A, AES50-B, AES50-C, AUX, SC, AES, USB, CRD, MOD. Each entry shows the number of populated source slots. Click **Configure Mapping** to open the CopyTable. ### Warnings The group selector shows warnings in two situations: - **Size mismatch**: When the target group has fewer slots than the source (e.g., copying 48 AES50-A sources to 8 LCL slots). Only the slots that fit are mappable; the rest are automatically disabled. - **Property mismatch**: When the target group does not support certain properties (e.g., copying phantom power settings to USB, which has no physical preamps). Unsupported columns are disabled in the CopyTable. ## CopyTable The CopyTable is the core of Source Management. It displays every source in the selected source group as a row, with columns for each copyable property plus control columns for source actions and reference updates. ### Table Layout ``` | ✓ | Source | Target | Name | Source Action | CH Refs | Direct Refs | Gain | Phantom | Stereo | ... | |---|-------------|-------------|-------|--------------|---------|-------------|--------|---------|--------|-----| | ✓ | AES50-A / 1 | LCL / 1 | Kick | Keep | ✓ | ✓ | 12 dB | +48V | Mono | ... | | ✓ | AES50-A / 2 | LCL / 2 | Snare | Reset | ✓ | ✓ | 8 dB | +48V | Mono | ... | ``` ### Column Checkboxes Each property column (Gain, Phantom, Phase Inv, Mute, Stereo Mode, Name, Color, Icon, Tags, Rcvc, Remote) has a checkbox in the header. Toggle it to include or exclude that property for all rows at once. Unsupported properties (based on the target group's capabilities) are disabled with a strikethrough label. ### Sub-Groups Sources are organized into sub-groups of 8 (1-8, 9-16, 17-24, and so on). Each sub-group header row provides: - **Group checkbox** -- Select or deselect all 8 rows in that sub-group - **Target offset dropdown** -- Remap the entire sub-group to a different target range (e.g., redirect sources 1-8 to target slots 9-16) > **Tip**: Use the target offset dropdown to quickly shift an entire block of sources. For example, if your kick drum moved from AES50-A slot 1 to LCL slot 5, set the offset for sub-group 1-8 to target 5-12. ### Row Controls Each individual row has: - **Checkbox** -- Include or exclude this source from the remapping - **Source label** -- Shows the source group and slot number (e.g., "AES50-A / 1") - **Target number** -- Editable field to set the destination slot. Defaults to the same number as the source. - **Property values** -- Displays current values (gain in dB, phantom on/off, name, etc.) Enabled columns appear in full contrast; disabled columns are dimmed. ### Disabled Rows A row is automatically disabled (grayed out, checkbox locked) when: - **No target slot**: The source number exceeds the target group's slot count (e.g., source 9 when the target group only has 8 slots) - **Claimed by another card**: The target slot is already used by a different remapping card ### Target Conflicts If two enabled rows in the same table map to the same target slot, a warning banner appears and the **Save Remapping** button is disabled. Resolve the conflict by changing one of the target numbers or disabling one of the conflicting rows. ### Full-Screen Mode Click **Full Screen** to expand the CopyTable to fill the entire browser window. This is useful for groups with many sources (e.g., 48-slot AES50 groups). Click **Exit Full Screen** to return to the inline view. ## Copyable Properties | Property | Description | Example Values | |----------|-------------|----------------| | **Gain** | Input gain in dB | 12 dB, -6 dB, 0 dB | | **Phantom** | +48V phantom power | +48V, Off | | **Phase Inv** | Phase/polarity inversion | On, Off | | **Mute** | Source mute state | On, Off | | **Stereo Mode** | Mono, Stereo, or Mid/Side | Mono, Stereo, Mid/Side | | **Rcvc** | Receive custom setting (AES50 only) | On, Off | | **Remote** | Remote assignment (AES50 only) | On, Off | | **Color** | WING UI color index | 0-15 | | **Icon** | WING UI icon index | 0-127 | | **Name** | Source display label | "Kick", "Snare Top", "Vox L" | | **Tags** | Comma-separated tags | "drums", "vocals" | ## Source Actions After copying properties to the target slot, you can choose what happens to the original source slot. The **Source Action** column provides three states: | Action | Description | When to Use | |--------|-------------|-------------| | **Keep** | Leave the original source unchanged (default) | When you want to preserve the source as-is, e.g., creating a backup copy | | **Reset** | Clear the original source to WING defaults (gain 0 dB, phantom off, empty name, etc.) | When you are *moving* a source and want to clean up the old slot | | **Swapped** | Automatically detected -- the source slot is also a target in another mapping | Displayed as a locked badge; you cannot reset a slot that is about to receive data from another mapping | ### Swap Detection When two remapping cards form a swap (e.g., Card #1 maps AES50-A/1 to LCL/1, and Card #2 maps LCL/1 to AES50-A/1), the tool detects that each source slot is also a target. These rows display a "Swapped" badge instead of a dropdown, and the source action is locked to "Keep" to prevent data loss. Same-card swaps are also detected. For example, if you remap LCL/1 to LCL/8 and LCL/8 to LCL/1 within the same card, both rows show "Swapped." > **Warning**: Never reset a source slot that is also being written to by another mapping. The tool prevents this automatically, but be aware of it when planning your remapping strategy. ### Bulk Source Actions - **Column header dropdown**: Set all non-swapped rows to Keep or Reset at once - **Sub-group header dropdown**: Set all non-swapped rows in that sub-group to Keep or Reset ## CH Refs and Direct Refs When you move a source to a different slot, any mixer channels or matrix direct patches that reference the old slot will still point to the old location. The **CH Refs** and **Direct Refs** columns fix this automatically. ### CH Refs (Channel References) When enabled for a row, the tool scans all 40 channels (CH 1-40) and 8 aux channels (AUX A1-A8) in the snapshot. Any channel whose input source matches the original slot (e.g., AES50-A.1) is updated to point to the new slot (e.g., LCL.1). **Example**: CH 15 has its source set to AES50-A.1. You remap AES50-A.1 to LCL.1 with CH Refs enabled. After generation, CH 15 now points to LCL.1. ### Direct Refs (Direct Route References) When enabled for a row, the tool scans all 8 matrix channels (MTX 1-8) for direct patch references. Any matrix direct input matching the original slot is updated to the new slot. **Example**: MTX 3 has a direct input of "A.5" (AES50-A slot 5). You remap AES50-A.5 to AES50-B.5 with Direct Refs enabled. After generation, MTX 3's direct input reads "B.5". > **Tip**: Keep both CH Refs and Direct Refs enabled (the default) unless you specifically want channels to stay patched to the old source location. ### Column-Level Toggles Both CH Refs and Direct Refs have column-level checkboxes in the header. Uncheck the column header to disable reference updates for all rows at once. Individual rows can also be toggled independently when the column is enabled. ## Remapping Cards Each time you save from the CopyTable, a **remapping card** is created. Cards are displayed in a grid below the group selector. ### Card Contents Each card shows: - **Header**: The source and target groups (e.g., "#1: AES50-A -> LCL") with Edit and Delete buttons - **Body**: A before/after diff table showing only the values that will change. "Before" values (red) are the current target slot values; "After" values (green) are the source values being copied in. - **Footer**: A summary badge (e.g., "24 sources, 6 changes, 2 CH refs, 1 direct ref, 1 reset") ### Managing Cards - **Edit**: Click Edit to re-open the full CopyTable with the card's previous state restored. All checkboxes, target numbers, and source actions are preserved. - **Delete**: Click Delete to remove the card and free its target slots for other remappings. - **Add Remapping**: Click the "+ Add Remapping" button to create a new card with a fresh group selector. > **Tip**: You can create multiple cards to handle complex migrations. For example, map AES50-A sources 1-8 to LCL 1-8 in one card, and AES50-A sources 9-24 to AES50-B 1-16 in another. ### Conflict Rules Target slots are exclusive across cards. Once a card claims a target slot (e.g., LCL/1), no other card can map to that same slot. If all slots in a target group are claimed, the group appears as "fully claimed" in the target dropdown and cannot be selected. Swap direction is allowed: Card #1 mapping A to B and Card #2 mapping B to A do not conflict because they write to different target groups. ## Generate Once you have at least one remapping card, the **Generate Modified Snapshot** section appears at the bottom of the page. ### Options - **Filename**: Set the output filename (defaults to "modified.snap") - **Download**: Check to download the modified snapshot file to your computer - **Save to Files**: Check to save the modified snapshot to your [Files library](02-my-files.md) You can enable both options to download and save simultaneously. ### How Generation Works When you click **Generate Modified Snapshot**, the backend: 1. Reads source values from the **original** parsed snapshot 2. Writes copied properties to target slots in the **output** copy 3. Updates channel source references (CH Refs) in the output copy 4. Updates matrix direct patch references (Direct Refs) in the output copy 5. Resets source slots marked with "Reset" source action 6. Returns the modified `.snap` file > **Important**: All reads come from the original snapshot, and all writes go to the output copy. This means swap operations (A to B and B to A) are safe -- both cards read from the unmodified original, so neither overwrites the other's source data. ## Mobile Support Source Management is fully responsive. On mobile devices: - The CopyTable displays a simplified view with Source, Target, and Name columns - **Property pills**: A horizontal toolbar of toggleable property pills replaces the column checkboxes - **Detail sheet**: Tap any row to open a bottom sheet with the full source details, source action dropdown, and reference toggles - Remapping cards stack in a single column for easy scrolling > **Tip**: Use the full-screen toggle on tablets to get more screen space for the CopyTable. ## Tips and Best Practices ### Plan Your Remapping First Before you start, map out which source slots need to go where. If you have a complex migration across multiple groups, sketch it out: ``` AES50-A 1-8 -> LCL 1-8 (drums) AES50-A 9-16 -> AES50-B 1-8 (guitars/keys) AES50-A 17-24 -> AES50-B 9-16 (vocals) ``` ### Use Reset for Clean Migrations When you are permanently moving sources to a new group and will not need the old slots, set the source action to "Reset." This clears the old slots so they do not confuse future users of the snapshot. ### Keep References Updated Unless you have a specific reason not to, leave CH Refs and Direct Refs enabled. This ensures your channel patches follow the sources to their new locations. Forgetting to update references is the most common source of "missing signal" issues after remapping. ### Verify with Signal Flow After generating your modified snapshot, upload it to [Signal Flow](05-signal-flow.md) to visually verify that all connections are correct. Trace mode is particularly useful for confirming that channels point to the right sources. ## Troubleshooting ### "No target slot" on some rows The target group has fewer slots than the source group. These rows cannot be mapped and are automatically disabled. Use the target offset dropdown in the sub-group header to shift mappings to valid target ranges, or accept that only a subset of sources can be transferred. ### "Claimed by Card #X" on a target slot Another remapping card already maps to that target slot. Either edit or delete the existing card to free the slot, or change your target number to an unclaimed slot. ### "Target group does not support: Phantom, Gain" The target group (e.g., USB, CRD) does not have physical preamps, so gain and phantom settings cannot be copied. Those columns are automatically disabled. The remaining supported properties will still be copied. ### Multiple sources mapped to the same target Two or more enabled rows have the same target number. The Save button is disabled until you resolve the conflict. Change one of the target numbers or disable one of the rows. ### Channel references not updating after generate Make sure the **CH Refs** column checkbox (in the table header) is enabled, and that the individual row checkboxes are checked. If you disabled the column header, all per-row checkboxes are overridden to off. ### Modified snapshot has no changes Check that at least one row checkbox and one property column checkbox are enabled. If all rows or all columns are unchecked, the card contains zero effective mappings and no changes are applied. ## Working with a live mixer Instead of a `.snap` file, you can read your source groups **straight from a WING on your network** and write your changes **back to the console** — no SD card, no file shuffling. This needs the small **WingBridge** helper running on the same computer (a download link appears in the *Connect to Mixer* dialog). ### Read from the mixer 1. Click **Connect to Mixer** (next to *Browse Library*). 2. Start the helper, then **Connect helper** and confirm the pairing words match on both sides (a one-time security check). 3. **Discover on LAN**, pick your console, and **Read sources**. Your source groups load just like a file would — but this is a **live, partial read**, not a snapshot, and nothing is saved. Configure your remappings as usual. ### Write back to the mixer When your remappings are ready, click **Apply to live mixer**. WingTools then: 1. **Reads the console again** and computes the *exact* changes your remapping makes — only the input fields that actually differ. 2. Shows a **preview table** of every change (input, field, *from → to*). **Nothing has been written yet.** 3. On your confirmation, writes those fields to the console and **reads them back to verify** each one landed. Only the changed input properties (name, gain, phantom, polarity, mute, stereo mode, colour, icon, tags) are written — nothing else on the console is touched, and no file is created. Any field that doesn't verify is reported so you can retry. > **Note:** Live writes apply input *properties*. Routing-reference updates (the > *CH Refs / Direct Refs* options) currently apply only to the downloaded file, > not to live writes. ### Undo, Redo & write history Every change WingTools writes to your console — from Source Management, WingGPT live edits, or anywhere else — is recorded, together with the value that was on the console *before* the write. You reach it from the **Mixer** menu in the top navigation bar (the bridge status dot), which has **Undo**, **Redo**, and **History** buttons whenever a mixer is connected. - **Undo / Redo** step back and forth through your changes. Undo writes the previous values back to the console; Redo re-applies them. (Undo *is* a write, so it needs Write Mode, just like the original change.) - **History** opens a timeline of everything written, newest first, with timestamps. From there you can: - **Undo to here** — roll the console back to any earlier point in one step. - **Revert this** — cherry-pick a single field to undo. This doesn't rewind the rest of your history; it's recorded as a new change on top of the stack. - **Checkpoints** — a labeled divider is added automatically before larger batches (e.g. *Source changes (12)*), and you can drop your own **Create checkpoint** marker before doing something risky. - **Clear history** when you're done. History is kept per mixer and survives a page reload. After a reload, items captured in the earlier session are marked with a divider and a *"may be stale"* note — the console could have changed in the meantime (a scene recall, another operator), so an undo of an old item writes the value WingTools last saw, then verifies it. ## Next Steps - **[Signal Flow](05-signal-flow.md)**: Visualize your modified snapshot to verify source routing - **[Routing Generator](04-routing-generator.md)**: Generate PDF documentation of your updated routing - **[My Files](02-my-files.md)**: Manage your snapshot files and generated outputs - **[Audio Engineer Guide](08-audio-engineer-guide.md)**: Best practices for WING console workflows --- **Questions?** Check the [Reference section](09-reference.md) for troubleshooting tips.