Troubleshooting

Change one thing at a time, and start with one question: do the relays click when you activate a Chain?

• Relays click: the ProPatch app reached the unit and the relays moved. Go to Relays click but no audio passes.
• No clicks: work through power, connection, and the Chain itself, in that order, starting with ProPatch does not appear in Wolffhound.

A click proves control, not audio. Keep monitors down while you troubleshoot, and turn off phantom power before changing a mic-level route.

Power indicator doesn't settle to green

Use only the included power supply; a lookalike can light the unit and let Wolffhound find it without switching relays. For what each indicator state means, see Hardware Reference. If the unit never reaches steady green, record the pattern and contact Wolff Audio support; don't keep power-cycling it.

ProPatch does not appear in Wolffhound

Symptom	Likely cause	Fix
No tab, Ethernet connected	Cable in the Dante jack	Move it to the Control jack.
No tab, no link lights	Bad cable or switch port	Reseat or replace the cable; try a known-good switch port.
No tab on macOS, link lights on	Local Network permission denied	System Settings › Privacy & Security › Local Network: allow Wolffhound.
No tab, Control cable in an audio interface's network port	That port isn't a normal switch	Connect to a network switch or directly to the computer.
No tab over USB-C on a recent Mac	Accessory prompt not accepted	Unplug and reconnect, then accept the prompt.
No tab over USB-C	USB network still starting	In System Settings › Network, wait for the USB Ethernet service to get an address.
Tab appears but stays blank	Page didn't load	Click ↻ to reload the tab, or quit and reopen Wolffhound.

A direct Ethernet cable to the computer works, but a switch is easier to diagnose. The Demo Device tab never controls hardware; select your unit's tab. See Wolffhound and the ProPatch App.

The ProPatch app shows disconnected

When the unit stops responding, a Disconnected banner appears under the header: "Changes will take effect when connected to unit name again." An OFFLINE popup may also appear: "ProPatch is not responding. Check USB/Ethernet cable."

Button	Result
CLOSE	Dismisses the popup this time.
HIDE	Stops the popup appearing. Turn it back on in System Configuration › PREFERENCES › Offline Warning Popup.

Don't make routing changes while disconnected; they are applied when the unit reconnects. To recover:

1. Confirm the unit has power and its tab is still in Wolffhound.
2. Check the Control Ethernet link or USB network service.
3. Wait a few seconds for the banner to clear.
4. Reload the tab if it doesn't.
5. Activate a simple Chain and listen for a click.

Chain does not activate and no relay clicks occur

Symptom	Likely cause	Fix
CHAIN INVALID	Missing Source or Destination, incomplete Node, or conflicting Port IDs	Complete the path; check every Node's Port Assignment reads Complete. See Chains.
Mult Chain won't activate	A Mult branch has no Destination	Add a Destination or remove the branch.
Conflict dialog appears	Another active Chain uses the same Port ID	Choose DEACTIVATE or CANCEL. For repeat conflicts, see Port ID Conflicts.
Chain switches off when another activates	Shared Port ID or Normal	Compare Port IDs (hold O); see Advanced Routing.
Everything goes quiet at once	MUTE ALL is on	Select UNMUTE.

Relays click but no audio passes

Symptom	Likely cause	Fix
Nothing reaches the Destination	Source or Destination itself	Connect them directly, without the ProPatch, and prove both work.
Signal on the wrong channel	Node assigned to the wrong Port ID	Hold O and compare every Port ID with the actual wiring.
Nothing through a DB25	Breakout reversed or wrong channel	Check snake direction and channel numbering. From Device and To Device are named from the unit's side; see Connecting Devices.
Works on rear, fails with front jack in use	Front and rear share a path	See Port ID Conflicts.
Signal leaves ProPatch but not heard	Interface, console, or DAW routing	Check routing before and after the analog path.
Processor seems missing	Processors bypassed	Press B on the selected Chain to restore them.

Still silent? Run the isolation procedures below.

Audio is missing after power-up

If audio is missing after power-up: confirm the Session, toggle one affected Chain off and on with monitors down, and contact support if it repeats.

Don't use a power cycle to recall routing; load a Session instead (Sessions, Files, and Backups).

A route fails only when a Mult is active

A large Mult can exceed the unit's internal routing paths, so the route doesn't engage.

1. Turn monitors down.
2. Switch off the suspect Mult and retest the plain route.
3. If it works, re-enable other Mults one at a time.
4. Export the Session, note the Port IDs, and contact support before relying on that Mult.

Files and backups

Symptom	Fix
Failed to export session	Try again. If it repeats, use Send to Support... with session data included.
Backup restore gives an unexpected state	Stop. Don't restore repeatedly; contact support with the backup file.
Session file won't import	Sessions (.propatchs) import from the Session menu; backups (.propatchb) restore from System Configuration › BACKUP. See Sessions, Files, and Backups.

For versions, updates, and firmware, see Updates and Firmware.

Windows limitations

On Windows, Undo (Ctrl+Z) and Ctrl+click to delete a Chain or Node don't work in the current ProPatch app. Delete from the Chain or Node ⋮ menu, and save Sessions often so you can Revert.

Isolation procedures

Loopback test

1. Patch one known interface output directly to one known interface input and confirm the test signal returns.
2. Put the ProPatch between the same two points.
3. Build a Chain with just that Source and Destination, no Processor.
4. Activate it: you should hear a click and get the signal back.

If the direct loop works and the ProPatch loop doesn't, check Port IDs and DB25 direction, then try a Port swap.

Port swap

1. Pick unused channels on another Port.
2. Move both directions of the suspect connection there.
3. Update every affected Node to the new Port IDs.
4. Retest the same Chain.

If a known-good Device works on one Port and fails on another after correct reassignment, record it and contact support.

Front-panel injection

1. Turn off phantom power and turn monitors down.
2. Create a Source Node for one front-panel input.
3. Route it to a known-good Destination and inject a test signal.

If this works, the unit is fine and the problem is in rear snakes, patchbays, or room wiring.

Contact support

1. Open App Info and select COPY.
2. From the Session menu, choose Send to Support..., fill in Name and Email, describe the problem, and turn on Include session data. See Sessions, Files, and Backups.
3. Include the unit model and serial number, Wolffhound version and release channel, operating system, connection type, indicator pattern, whether relays click, the smallest failing Chain with its Port IDs, and which procedures above you ran.

Don't open the chassis or move internal cards unless Wolff Audio asks you to. Keep the original packaging for service.