Support

First check the source. In a host, confirm the channel has audio before RMXY-1 and that monitoring is on. In standalone, choose an available input and output in Settings and allow microphone access if that input needs it. No Input intentionally supplies silence.

Then release BRAKE, clear any held gesture, and check the master dry/wet. If the looper is at 100% wet, make sure it holds a playing loop.

Check that the effect is powered on, that the parameter has a target on the axis you are moving, and that the target differs from Base. Also check the effect mix and master dry/wet.

If you just used the looper, check Bypass Dry: with it on, live input intentionally skips the chain.

Turn Hold off and clear any motion loop. Then check scene Decay, reverb and delay tails, feedback, Freeze and generator Base levels. BRAKE is the quickest recovery in performance.

In AUv3, check the host tempo and that its transport is running. In standalone, check the BPM and the Clock Sync source in Settings → MIDI & Sync. Bluetooth and AirPlay outputs add latency that can make correct timing feel late.

The host controls audio routing, recording, transport, background audio and session saving. Check the host's input, monitoring and effect settings. The standalone app does not currently play audio in the background.

Standalone does not currently accept incoming MIDI control. Load RMXY-1 as an AUv3 in AUM or another compatible host and map your controller to RMXY-1's exposed parameters there.

Confirm the output route, the receiver's channel and CC or Note mode. For CC, check the receiving instrument's own assignment. A MIDI connection is not an audio connection: the instrument needs its own audio route.

Reduce the chain load and try a larger I/O buffer, or the equivalent host setting. For delayed monitoring, avoid wireless outputs when timing matters.

Scene and program files hold setup data, not recorded audio or motion loops. Use your host's session and recording features to keep audio.