If you are using the effects loop (Send/Return) on your REACTOR 50W/100W, you might notice that it seems to "stop working" or turn off when you switch to a different factory preset, even though your cables remain securely plugged into the hardware. You may find yourself having to unplug and replug the Return cable to get it working again.
This article explains how to keep the FX Loop active across your favorite presets, and why this behavior occurs.
How to fix it (Workaround)
To keep the FX Loop active when switching presets without having to replug your cables, you need to save the FX Loop's "Enabled" status directly to each preset using the REACTOR App. Follow these steps:
- Connect your REACTOR 50W/100W to the REACTOR App.
- Switch to the preset you want to use with your external pedals.
- In the app's signal chain view, locate the Send/Return (FX Loop) block and toggle it to Enable (On).
- Save the changes by selecting Assign to REACTOR.
- Repeat this process for any other presets you frequently use with your FX Loop setup.
The FX Loop status is stored individually for each preset. If you want the FX Loop to remain active after switching presets, each preset must be saved with the FX Loop block enabled. This applies even when using the REACTOR 50W/100W in Standalone mode (without the app connected).
Why is this happening?
- Preset-Based Settings (Not Global): Both the FX Loop's enabled/disabled status and its position in the signal chain are saved per preset on REACTOR 50W/100W, rather than as a global system setting.
- Jack Detection Event: When you physically plug a cable into the Send/Return jacks, the hardware temporarily activates the FX Loop for the currently selected preset. This does not automatically save the FX Loop as enabled for that preset.
- Default Factory Presets are "Off": Most default factory presets have the FX Loop block set to "Off" in their signal chain. When you switch to a new preset that does not have the FX Loop enabled by default, the loop will deactivate. Because the cable is already plugged in, no new "jack detection event" is triggered, making it feel like the loop has suddenly failed.