[v1.9.1 RM10] Adaptive view mode ignored when Transfer = Direct — plus the full fix for viewer not scaling / stuck at 1080p

Device: Comet Pro (GL-RM10)
Firmware: V1.9.1 release1
Client: GLKVM desktop app on Windows; controlled device is a Mac Mini (macOS)

Summary
After updating to v1.9.1, the viewer stopped expanding the remote screen to fill the window. The video would shrink to fit a smaller window but would not scale up past its native size, leaving large dead-space borders. It had worked perfectly before the update. Tracking this down turned out to involve four separate settings across two devices, so I'm posting both the bug and the complete fix for anyone else hitting this.

Bug: View = Adaptive is ignored when Transfer = Direct
With Settings → Video → View set to Adaptive and Transfer set to Direct, the video renders at native pixel size and will not upscale to fill the viewer window (status bar showed "Direct H.264 - 1920x1080"). Switching Transfer to WebRTC immediately restored correct Adaptive scaling — the video fills and resizes with the window as expected.

Either Adaptive should work under Direct, or the UI should indicate that View modes don't apply to Direct transfer. Right now the setting silently does nothing, which is very hard to diagnose. (It's possible the update switched my Transfer mode to Direct as a new default — the behavior changed overnight without me touching settings.)

Repro:

  1. Settings → Video → View: Adaptive
  2. Settings → Video → Transfer: Direct
  3. Resize viewer window larger than the remote resolution → video stops growing at native size, dead space around it
  4. Change Transfer to WebRTC → scaling works correctly

Second issue: EDID changes don't take effect on macOS without a reboot
Separately, I wanted the stream above 1080p. Changing the EDID preset to 3840x2160/GLKVM/30Hz did nothing at first — the Mac kept outputting 1920x1080, and System Settings → Displays still identified the display as "Lontium semi" with no modes above 1080p even with "Show all resolutions" enabled. macOS caches the EDID and only re-reads it on a hot-plug event. Cycling the EDID preset (change to a different preset, wait for the screen to blank, change back) and/or rebooting the controlled Mac forced a fresh EDID read, after which the higher resolutions appeared and the stream came up at the new resolution.

Suggestion: have the docs (and ideally the console UI near the EDID setting) note that macOS in particular requires a re-plug/reboot of the controlled device after an EDID change.

Complete checklist for anyone with a letterboxed / 1080p-stuck viewer:

  1. Settings → Video → View: Adaptive
  2. Settings → Video → Transfer: WebRTC (Adaptive is ignored under Direct on v1.9.1)
  3. Settings → Video → EDID: pick the resolution you want the controlled device to output
  4. On the controlled device, select the new resolution in its display settings — on macOS, cycle the EDID preset or reboot first so it re-reads the EDID

Happy to provide logs or screenshots if useful.

Regarding the second question, is your macOS device using a Type-C to HDMI hub to connect to the KVM? Have you tried unplugging and replugging the hub to see if it resolves the issue?

Thanks for your feedback; this issue will be resolved in the next version.