Skip to content
Sign in
Open Ticket
  • There are no suggestions because the search field is empty.

Miracast Touchback Known Issues & Limitations

This article applies to ScreenBeam 1xxx-series and 960 products.

While Miracast Touchback provides an excellent wireless interactive experience, several known limitations may impact touch accuracy or performance. Below are the most common issues, causes, and recommended workarounds.

1. Touch Point Misalignment (Touch Offset / Touch Not Accurate)

Symptom:
Touch or pen input appears “off,” meaning the interaction does not align with where you touch on the display.

Cause:
This typically occurs when the Windows desktop resolution being projected (Duplicate or Extend mode) does not match the native resolution of the interactive touchscreen. When the aspect ratio or scaling differs, the OS cannot correctly map HID input coordinates.

Solution:

  • Set the Windows display resolution to match the native resolution of the touch display (commonly 1920×1080 or 3840×2160).

  • If using Duplicate mode, choose “Change resolution to match external display” when prompted.

Tip:
Touch alignment issues are nearly always resolved by matching the output resolution to the panel resolution.

2. Touch or Pen Input Feels Delayed or Laggy

Symptom:
Touchback gesture delay, slow inking, or inconsistent multi-touch response.

Causes:
Depending on connection type:

  • Miracast P2P (Wi-Fi Direct): Wireless congestion or interference on the operating channel.

  • Miracast-over-LAN: Weak Wi-Fi connection, AP roaming, high network latency, or rate throttling on enterprise WLANs.

Solution for Miracast P2P:

  • Manually configure the ScreenBeam to use a clean 5 GHz non-DFS channel (e.g., 165).

  • Keep the presenting laptop within 15–25 feet of the receiver.

Solution for Miracast-over-LAN:

  • Ensure the PC is on a stable 5 GHz Wi-Fi connection with strong signal strength.

  • Reduce roaming aggressiveness on the WLAN adapter.

  • Use enterprise APs configured for multicast/unicast optimization.

Tip:
Touch delay almost always improves after controlling the wireless channel or improving the client’s Wi-Fi stability.

3. Pen Pressure Sensitivity Not Detected (Optional note)

Some displays send only basic HID touch data. If the panel does not support stylus pressure over USB, inking apps may behave as if using a simple finger-touch input.

Solution:
Confirm whether the display supports HID Pen or Active stylus mode and update firmware if available.

4. Touchback Not Working at All

This is usually caused by lack of USB connectivity between the ScreenBeam and the IFP.

Solution:

  • Ensure the USB Type-B or USB-C upstream from the display is connected to the ScreenBeam USB port.

  • Replace the cable if the display has intermittent detection.

  • Confirm “Allow input from this device” is turned on in Windows.

  • Ensure client TCP Port 50000 is allowed for Miracast User Input Backchannel (UIBC).

5. Touchback Not Supported Over Some Corporate VPNs

VPN clients often disable Wi-Fi Direct interfaces or block Miracast system traffic.

Workaround:
Disconnect VPN before connecting to ScreenBeam.