xitanul Posted March 13 Posted March 13 Hello. It took me a while to understand why my microphone was crackling when I was using Big Box but I finally found the culprit (thanks to the AI), the crackling is disappearing when I totally disable controller detection in Big Box. It seems like Big Box’s HID Polling/Controller Scanning is saturating my USB bus or creating DPC latency spikes that conflict with my USB microphone even when the software is in the background, any solution if I want to keep gamepads enabled ? What I have already tested (without success): Changed Process Priorities (Big Box to "Below Normal", OBS to "Above Normal"). Locked Big Box at 60 FPS and disabled all overlays (Nvidia/Discord). Matched sample rates (all devices set to 48kHz/16-bit) Changed USB ports (tried USB 2.0 and 3.0). Set Windows Power Plan to "High Performance" (Minimum CPU state at 100%) and GPU at high performance. Tried both Windows Media Player and FFmpeg video engines in Big Box. My setup: Windows 10 (22H2) LaunchBox/Big Box (13.26-beta-2) Samson Meteor USB Microphone Controller: [8bitdo adapter + SNES classic controller] Inte core i5-4460 RTX 4060 16GB DDR3 ASROCK B85 pro 4 Quote
xitanul Posted March 20 Author Posted March 20 I could use Joytokey to use keyboard keys on my gamepad but this means I have to launch it everytime, not very practical. Quote
xitanul Posted Thursday at 03:48 PM Author Posted Thursday at 03:48 PM (edited) I will go without gamepad I guess, also need to do extra steps to avoid gamepad reconnectinng if you plug it when Big Box is already launched. Open the BigBoxSettings.xml file with Notepad (or Notepad++). Search (Ctrl+F) for the tag: <EnableGamepad> Change the value between the tags to "false": <EnableGamepad>false</EnableGamepad> (Optional but recommended): Also find the <EnableAllControllers> tag (if present) and set it to false as well. Save the file, close it, then right-click on it > Properties, and check the Read-only box. Click Apply. One more step, just in case: InputBindings.xml If Big Box is still resisting after locking the global settings, it's because the application is forcing the controls to read via its dedicated shortcut file. Still in the LaunchBox\Data\ folder, find the InputBindings.xml file. Delete it completely (make sure both LaunchBox and Big Box are closed). The next time you launch the application, it will generate a blank file which, combined with your read-only locked BigBoxSettings.xml file, should never again scan or "pollute" the HID inputs of your controller when you hot-plug it. Edited Thursday at 03:48 PM by xitanul Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.