Gamepad indices do not match Windows / indicator LEDs

Running windows 10 with two 8bitdo sn30 pro usb, and two generic xbox 360 pads. These indicate which one is player 1 - 4 with the led lights.
P.c games on the system adhere to this (the game pad with player one indicated via LED are indeed player 1 or player 2-4 respectively)
the Mame plus command line version also adheres to this In fact all systems i have setup adhere to this. Apart from emuhawk.

Every emulator i set up using emuhawk detects the player 1 controller as x4 ,player 2 is x3, player 3 is x2, and player 4 is x1.

this is 100% backwards and is making the use of emuhawk impossible for me.
If i chose to use the emulators nativity (example) if i use snes9x.exe and configure that, it detects the controllers correctly.
i would prefer to use emuhawk as i prefer to edit an ini file via scripting as and when needed. and not all emulators support this. But currently i am having to use all the individual emulators rather than emuhawk because of this issue.

i cannot find any way to fix this behaviour in emuhawk.

Reproduce the reported setup on Windows 10 with two 8BitDo SN30 Pro controllers and two generic Xbox 360 pads, comparing EmuHawk with the native emulators. Trace how EmuHawk assigns controller indices and player numbers, then verify that the LED-indicated player order is preserved across supported emulators.