Best practice to drive 2 independent WLED instances from 2 separate Monitors?

[leivenn]

Hello,

I am looking for the correct way to configure HyperHDR for a dual-monitor setup where each monitor has its own dedicated LED strip (WLED).

My Hardware:

• OS/GPU: Windows 11 / RTX 4090
• Monitor 1: Samsung Odyssey G9 (5120x1440) (Direct HDMI)
• Monitor 2: Samsung TV 4K (3840x2160) (HDMI by USB-C Hub)
• Lighting Hardware:

  • WLED Device 1 (ESP32) (413 LEDs surround the screen) → Installed on Monitor 1 (G9).

    • 

  • WLED Device 2 (ESP32) (413 LEDs surround the screen) → Installed on Monitor 2 (TV).

    • 
• Screen layouts :
  • 

The Goal: I need to achieve independent control for both screens simultaneously on the same PC:

• Stream A: Capture only Display 1 and send data to WLED 1.
• Stream B: Capture only Display 2 and send data to WLED 2.

The Issue: I am currently unable to configure a different Software Screen Capture device for each HyperHDR instance. For example, I cannot assign \.\DISPLAY1 to the G9 instance and \.\DISPLAY2 to the TV instance simultaneously. It appears that the DirectX 11 grabber selection is not independent per instance: I am forced to use the exact same display source for both instances (e.g., if I change it on one, it seems to conflict or limit the other), which prevents me from driving the LEDs independently. Even with MULTI-MONITORS, it applies the combined images from the two screens to both instances in the same way.

The Question: What is the recommended configuration or workflow in HyperHDR to map a specific Display (DX11) to a specific WLED target independently? I need to ensure that what happens on the TV (Monitor 2) drives the TV LEDs, without mixing with the Ultrawide Monitor (Monitor 1) content.

Thank you!

[awawa-dev]

Hi
As you can read in the wiki, best practice is to avoid using WLEDs for our project. You can control two independent monitors with a single RP2040, e.g., an Adafruit Scorpio, in multi-segment mode and a single instance. Check out HyperSerialPico

[leivenn]

Hi,

Thank you for the suggestion regarding the RP2040 and HyperSerialPico. I understand that a wired USB solution offers superior performance and lower latency.

However, replacing the hardware is unfortunately not an option for me at the moment:

• Installation is fixed: Everything is already mounted behind the screens.
• Hardware limitations:
  • My G9 setup uses a raw ESP32 that is already wired, and I am not comfortable enough with soldering/electronics to rebuild it into a wired USB setup.
  • My TV setup uses a pre-made commercial ESP32 WLED box (plug & play), which I cannot easily modify.
    I really need to make this work with my current wireless WLED setup.

Could you please assist on the software side given these constraints?
Since the Dual-Instance DX11 selection seems to conflict (I can't assign Display 1 to Instance 1 and Display 2 to Instance 2 separately), is there an alternative configuration?

• Question: Is it possible to use a Single Instance in "Multi-Monitor" mode but route the data to two different IP addresses?
• Example: Map the left part of the captured area (Monitor 1) to WLED IP 192.168.x.A.
• Map the right part of the captured area (Monitor 2) to WLED IP 192.168.x.B.

If I could send specific parts of the capture to specific UDP targets from a single instance, that would solve my problem without needing a second instance.

Thanks for your understanding.

[leivenn]

Hi @awawa-dev,

Update: I followed your advice! I ditched the WLED setup and installed a Raspberry Pi Pico (RP2040). I successfully compiled the firmware with multi-segment support (Monitor 1 on GP2, Monitor 2 on GP3), and physically everything lights up correctly via the single USB connection.

The Issue: I am now stuck on the HyperHDR configuration side. Since I am using a single Pico (Single Instance), I assume I need to capture both monitors simultaneously to map the LED segments to their respective screens in the LED Layout.

However, in the Capturing Hardware tab (Windows DX11), I only see 'Display 1' or 'Display 2' (and Auto). I do not see a "Multi-monitor" or "Combined desktop" option.

The Question: How can I configure the DX11 grabber to feed the single HyperHDR instance with the video data from both screens at once? I need the full canvas so I can map the first segment of LEDs to the G9 and the second segment to the TV.

Is there a specific setting, a workaround, or a Wiki page I missed regarding dual-monitor capturing on Windows with a single controller?

Thanks!

[leivenn]

Update on my situation:

I switched to a different computer (Laptop with Intel Iris Xe Graphics) to test.
Good news: The "Multi-monitor" option is now visible and selectable in the DX11 grabber settings!

The new issue:
Although the multi-monitor capture starts, the canvas is broken. The preview shows a distorted image with a large black dead zone/offset (see attached screenshot), making it impossible to align my LED segments correctly.

I checked the logs and found this suspicious line, suggesting the grabber is being clamped to a tiny resolution despite my 5K+ setup (G9 + 4K TV):
[DX11_SYSTEM:MULTI-MONITOR|] (Grabber.cpp:276) Set new width: 512, height: 512 for capture

I tried changing the "Re-order mode" and resolution settings, but the black offset persists.
I have attached the full logs and the preview screenshot. Is this a known limitation with Intel Iris Xe drivers in multi-monitor mode?

https://pastebin.com/yaWsr0bh