Cannot get IPAC and controllers to work together.

First and foremost consider this:

• Only RetroArch bugs should be filed here. Not core bugs or game bugs
• This is not a forum or a help section, this is strictly developer oriented

Description

Cannot get ipac-4 and controller to work properly , spent weeks trying.
[Description of the bug]

Expected behavior

I have an ipac-4 in keyboard only mode functioning in dinput and 2 wireless xbox 360 controllers that should have no conflicts in xinput mode. My controllers and IPAC work properly in MAME
[What you expected to happen]

Actual behavior

When controllers are used with xinput drivers they are never responding even though retroarch says they are connected and configured
[What is actually happening]
It seems there is some driver conflict and cant get the ipac and xbox 360 wireless controllers to work at the same time.

Im running this setup on win 10 64, i5 3570k 16gb ddr3, gtx 1060 6gb. This system is in an arcade cab I recently rebuilt.
Years ago on an older retroarch build I had this same IPAC4 and these same xbox 360 wireless controllers with same official microsoft wireless receiver working perfectly fine with no hasstles or special setup but ever since rebuilding my cab and updating to newest retroarch build its been a nightmare.
Ive tried everything and even resorted to starting from scratch with a fresh install of retroarch and launchbox and reconfiguring 8tb of games but I still have the issue.

At first my ipac seemed to take priority and was the only thing I could get working. I tried every driver for the ipac and the controllers. At one point I switched controller driver to sdl2 and this would somehow cause the ipac to have an error when launching a game for a second, which allowed the controllers to load in using input ports 1 and 2 and then the ipac would use a fallback and then controllers and the ipac (my arcade controlls) could both be used so I could choose whether to play a game with arcade controls or the controllers. This works perfectly in mame and other standalone emulators but in retroarch I could only get it to work with this hack workaround.

Thats when I tried a fresh install of everything.
I even been testing retroarch directlly....no frontend or any other variables.

Ive removed the microsoft drivers and let them re-install, ive deleted and started fresh with retroarch a dozen times, Ive tried all driver combinations, Ive set my ipac to ports 1 and 2 and controllers to 3 and 4, ive reversed it setting controllers to 1 and 2 and ipac to 3 and 4, ive configured and reconfigured all a few dozen times, ive saved controller profiles, deleted controller profilles, ..... Ive re-installed retroarch with only the ipac connected and it worked fine untill I plugged in controllers then the controllers wouldnt work. Ive re-installed retroarch with only the controllers plugged in and they worked fine untill I plugged the ipac in and now none of them work.
Ive tried using a third party utility to set and order usb devices in win 10...that didnt work so removed it.
Ive posted this issue on arcadecontrol forum, retroarch forum, launchbox forum, r/cade reddit, r/retroarch reddit, r/launchbox reddit........ Everyone says that my ipac and controllers should not have any conflict in retroarch but besides that I cant get any help or suggesstions.
I dont know what else to try at this point. Ive been working on this arcade cab software setup for over a month and this issue is whats dragging it on so long. In mame I just map my controls on the ipac and on the controllers and no issues at all but Ive tried everything in retroarch with no luck. Please help

Bisect Results

[Try to bisect and tell us when this started happening]

Version/Commit

1.9.0

• RetroArch: [version/commit]

Environment information

• OS: [The operating system you're running]
• win 10 64
• Compiler: [In case you are running local builds]

Start by reproducing the setup on Windows 10 with the IPAC-4 in keyboard mode and the wireless Xbox 360 controllers in XInput mode, then compare the XInput and SDL2 driver behavior described in the report. No source files or tests are named; done means both device types remain usable together in RetroArch without the reported fallback workaround.