Hi guys, I'm new here but I've been using Dolphin for a really long time and until now I never found an Issue which wasn't in the forums/wiki/elsewhere.
This one is kinda tricky to reproduce, but I'll try to explain:
I have a Plantronics Gamecom 780 Headphones which has 7.1 Dolby Surround function (via software and physical button)
So, the problem is... whenever I use Dolphin and hit the update button in Wiimote (to detect and sync connected Wiimotes obviously) this makes the same function as hitting the Toggle button of my headphones.
Then...
1. Every time a new controller is connected and detected, it will toggle the sound.
2. Even if it doesn't finds any controller, it will toggle the sound
3. If continuous scan is activated, it will continuously toggle sound on and off until I deactivate that function or close Dolphin
On a side note, I tested this with previous version I still had (various releases of 3.0 version) and none popped up this issue. This issue popped up on 4.0+ version (haven't tested on 3.5)
My Bluetooth dongle stopped working yesterday, so I don't have Bluetooth connection at the moment (but still, the issue occurs, so is no a problem with the dongle)
If you guys need extra info, or I should be posting this somewhere else, I'll appreciate any help.
This one is kinda tricky to reproduce, but I'll try to explain:
I have a Plantronics Gamecom 780 Headphones which has 7.1 Dolby Surround function (via software and physical button)
So, the problem is... whenever I use Dolphin and hit the update button in Wiimote (to detect and sync connected Wiimotes obviously) this makes the same function as hitting the Toggle button of my headphones.
Then...
1. Every time a new controller is connected and detected, it will toggle the sound.
2. Even if it doesn't finds any controller, it will toggle the sound
3. If continuous scan is activated, it will continuously toggle sound on and off until I deactivate that function or close Dolphin
On a side note, I tested this with previous version I still had (various releases of 3.0 version) and none popped up this issue. This issue popped up on 4.0+ version (haven't tested on 3.5)
My Bluetooth dongle stopped working yesterday, so I don't have Bluetooth connection at the moment (but still, the issue occurs, so is no a problem with the dongle)
If you guys need extra info, or I should be posting this somewhere else, I'll appreciate any help.