Haptics audio hum or buzzing

Useful Answer

If the haptics kit produces background hum or buzzing on the audio path, the most likely cause is power supply interference in the setup.

First isolate whether the noise is coming through the audio path:

A 3.5mm ground loop isolator can resolve the issue. This was reported as a complete fix in at least one real-world setup, and support had already heard the same recommendation from other users.

One isolator that worked well in the field:

This is a workaround rather than a firmware issue. The support explanation in the thread was that the kit had cost constraints during production, so a higher-end power supply was not included.

If the noise seems abnormal after the cable test, ask for a short video showing the noise and the power/audio setup. Support can then decide whether to replace the power supply or recommend the upgraded Noise Reduction Edition power supply.

Some faint high-frequency noise can be within normal range and may be masked by game audio. If the noise is mild but still objectionable to the customer, an upgraded noise-reduction power supply may reduce or eliminate it. Also confirm the foam buffer pads are installed correctly before treating a vibration or buzzing complaint as an electronics fault.

In Freshdesk ticket 31023, a customer with haptics-kit ringing/high-squelch noise confirmed that buying the upgraded power source fixed the issue and said it works great. Treat that as a confirmed outcome that the upgraded noise-reduction power supply can solve this specific ringing/whine branch for sensitive setups.

For PC/VR haptics setups, the haptics audio input may need the same game audio that is also going to the VR headset or main speakers. Windows may not send one app's audio to both outputs by default. A virtual mixer such as VoiceMeeter Banana can route audio to the VR headset and the 3.5mm haptics input at the same time; treat this as a PC audio-routing workaround, separate from hum or grounding diagnosis.

If a new power supply appears to cause a flash/crack sound and the entire controller becomes dead, stop treating it as a normal audio-hiss issue. Have the customer revert any haptics/spinner wiring back to the baseline Arcade2TV-XR setup and test on another PC. If Windows still only chimes, the board LEDs stay off, and the software cannot see the controller, escalate as a likely PCB or power-chain hardware failure rather than another noise filter issue.

Source Context

One customer reported that the ground loop isolator fully solved the hum problem. Another had speaker whine with USB to PC, wall power to both controller and haptics, and aux to headset; support recommended disconnecting the 3.5mm audio cable as the first isolation test, checking cable routing, and considering a replacement or upgraded noise-reduction power supply if the whine remained abnormal. A later customer resolved loud hum after rechecking all audio connections and cables. Another support exchange clarified that a small high-frequency whine can be normal but that the upgraded power supply helps sensitive setups. Freshdesk ticket 31023 later confirmed that the upgraded power source solved a ringing/high-squelch noise case. A VPX/VR user noted that VoiceMeeter Banana was useful for sending PC audio to both the VR headset and the haptics input. A separate thread showed that a suspected power-supply event can become a broader dead-controller PCB issue, so separate audio noise from actual power-chain failure.