WACUP

General => General Discussion => Topic started by: TheFonz on December 08, 2019, 09:55:32 PM

Title: [RESOLVED | DISABLE GEN_WIN10SHELL.DLL] Bluetooth Headset & Auto Pause
Post by: TheFonz on December 08, 2019, 09:55:32 PM
My bluetooth headphones have an auto pause function if they are removed from my ears. The only problem is one of the buds is malfunctioning and thinks I've removed the ear bud when I haven't.
This causes WACUP to pause. In WinAMP OG it would not auto pause.
I am trying to find the setting to stop this from happening, I can't find it anywhere, nothing is jumping out at me - Hopefully there is such a setting I can disable.
(on Windows 10)

Cheers
Title: Re: Bluetooth Headset & Auto Pause
Post by: dro on December 12, 2019, 10:45:50 PM
What output plug-in are you using under WACUP? As it's not something I'm aware of being directly coded into WACUP (especially if out_ds is the plug-in being used which hasn't been altered from what 5.666 uses) & it might be more down to the output plug-in &/or how the interaction with the OS/audio driver works.

Alternatively it might require selecting the specific device in the output plug-in config but I'm not sure what else is going on as I've no bluetooth devices to even try to replicate the issue.

-dro
Title: Re: Bluetooth Headset & Auto Pause
Post by: TheFonz on January 20, 2020, 11:24:56 PM
I only have Nullsoft DirectSound Output v2.64 (out_ds.dll) enabled and bluetooth is still pausing WACUP.
Not sure what else I can do :(
Title: Re: Bluetooth Headset & Auto Pause
Post by: dro on January 27, 2020, 03:20:42 PM
I don't know either unless there's some OS / driver option or somehow a compatibility mode is being applied without realising. Maybe someone else who uses bluetooth can help out.

-dro
Title: Re: Bluetooth Headset & Auto Pause
Post by: TheFonz on February 21, 2020, 12:23:21 AM
Resolution is to disable gen_win10shell from the General Purpose plugins.
Title: Re: Bluetooth Headset & Auto Pause
Post by: dro on February 21, 2020, 12:48:55 AM
Specifically what's going on is that the bluetooth device/driver when the issue occurs is triggering an OS wide notification of a playback change event & because WACUP has the means to detect & handle that (via the gen_win10shell.dll plug-in), that's why it would react & a Winamp install won't (since it doesn't support the API involved).

Main thing is we finally worked out what was going on :)

-dro