mirror system audio with BT and USB in the same time not work

[Jobima1st]

it will be no sound if the dualsense connected with bluetooth and usb in the same time using mirror system audio

and now we have "Disconnect Bluetooth When Plugged In over USB" that problem is kinda fixed but I think it worth mention and fix the root cause of it anyway (since Disconnect Bluetooth When Plugged In over USB is kinda work around for it)

[hifihedgehog]

@Jobima1st Root cause found, measured on a live DualSense, and fixed. Issue #387 carries the full investigation and the implementation record, commit fe1df08, in the next build.

You were right that Quick Charge was a workaround, and your instinct about the root cause pointed at the right place. The silence is the pad's own firmware: while the Bluetooth link is up, a DualSense mutes its USB audio interface in both directions. We proved it with PadForge taken out of the loop entirely. A test tone played straight into the pad's Windows audio endpoint stays silent while both links are connected, and the pad's microphone endpoint delivers no data at all. Drop the Bluetooth link and the identical pipeline plays at full level. No program can unmute that interface from the PC side.

What CAN be fixed host-side is the half-finished transport switch that creates the situation. When you plug the cable in, SDL moves the pad's input to USB and removes the Bluetooth joystick, but it leaves the radio link itself up, and that lingering link is what mutes the audio. The fix finishes the job: whenever PadForge builds the wired audio path for a pad you have routed audio to (Mirror System Audio, sound macros, or DualSense persona audio), it drops the leftover Bluetooth radio link automatically, through the same mechanism Quick Charge uses. It fires once per plug-in, so if you deliberately reconnect Bluetooth while the cable is in, PadForge leaves your choice alone, the same promise Quick Charge keeps. Pads that never touched Bluetooth are unaffected.

So with the next build, the mirror keeps playing when you plug the cable in, with or without the Quick Charge checkbox. Quick Charge remains useful for what it was built for, charging without the radio burning power.

Two reports, two real defects, and this one arrived with the exact observation that mattered. Thank you for pushing past the workaround.

[Jobima1st]

thank you

now it disconnect BT even without "Disconnect Bluetooth When Plugged In over USB", is that ok?

[hifihedgehog]

Yes, that is the fix working as designed. The rule it follows: the Bluetooth link drops only when PadForge is about to play audio through the pad's wired path, because the pad refuses to play that audio while the Bluetooth link is up. The two connections cannot coexist with sound, so PadForge finishes the switch to the cable.

The boundaries, so you know exactly what to expect:

• It fires only for a pad you have routed audio to: Mirror System Audio, sound macros on the controller speaker, or DualSense persona audio. Plug in a pad with none of those and Bluetooth is left exactly as it was.
• It fires once per plug-in. If you reconnect Bluetooth afterward while the cable stays in, PadForge respects that and leaves the link alone (audio goes silent again in that state, since the mute is the pad's own firmware).
• "Disconnect Bluetooth When Plugged In over USB" still has its own job: it drops the link on any charge, audio or not, so the radio is not burning power while the pad charges.

Thank you for verifying it on your controller so quickly.