Alternative A2DP Driver FAQ

Operating System

Windows 10 Version 1903 to Version 22H2 (x64 only), Windows 11 Version 21H2 to 22H2 (x64 only)

OS Boot Loader

Windows standard boot loader. (3rd party boot loaders are not supported)

Bluetooth Stack

Windows 10/11 inbox Bluetooth Stack

1. Download the installer from the download page.
2. Double-click on the downloaded installer file and follow the instruction.

After installing the package to your PC following the "How to install the Alternative A2DP Driver package?" section, all of your Bluetooth audio devices are still controlled by the Windows inbox A2DP driver.

The next step is installing the Alternative A2DP driver to your audio device(s).

1. Select the device in the left pane.
2. Select "Alternative A2DP Driver" from the "Device Driver" drop-down list.
3. Click on the "Install" button.

After the trial period expires, your Bluetooth headphones will connect to your PC, but you don't hear any sound from them. You will also see an expiration message in the app.

In theory, as long as your Bluetooth adapter supports EDR (Enhanced Data Rate, 2/3Mbps data transfer), it should be ok. And, unless you are using a VERY old (like more than ten years old) adapter, it should support EDR.

That said, if you try very high bitrate (such as LDAC HQ, which uses more than x3 bitrate compared to the SBC and AAC), you will need to minimize the interference with other radio and Bluetooth traffics. Also, a high-power transmission (Class 1) adapter will help stabilize the streaming.

Please see another FAQ topic: How can I improve Bluetooth streaming stability? for the complete list of recommendations.

Back in the day, Windows' out-of-the-box Bluetooth support was very limited and did not include A2DP support. To use A2DP, you had to install a 3rd party driver. But, that's history. Windows 10/11 supports A2DP out-of-the-box, and you no longer need to install a 3rd party driver. More importantly, the 3rd party drivers used in the past are too old and not fully compatible with Windows 10/11 and shouldn't be installed.

If you see this message, it means that you have such an old A2DP driver installed on your PC. Please uninstall such driver before using Alternative A2DP Driver.

We cannot provide instructions on how to remove such a driver, as the necessary steps may vary depending on which 3rd party driver you have installed. If you don't know how to remove it, please find someone around you who can help you.

As the name suggests, the critical component of the Alternative A2DP Driver is a "driver" (a special software that can directly access hardware). Microsoft Store doesn't allow to publish a package that contains a "driver". Therefore, Alternative A2DP Driver cannot be distributed through Microsoft Store.

The type of license we currently offer is perpetual. You pay once and the license is valid forever.

IMPORTANT: This does not mean that the software is guaranteed to work with future versions of the operating system.

No. The license is a single PC license. So, you need a valid license for each computer.

However, we do offer a discount for additional licenses. When purchasing a license for an additional computer, please use the "Discount for additional license" section of the license purchase page.

Unfortunately, the license is tied to the specific hardware (more specifically, to the motherboard) and is not transferable to another computer. This restriction applies regardless of the reason for replacing the hardware.

We wish we could make it transferable, but that would require a lot more resources (development effort and maintenance) and thus increase the license fee.

So we decided to keep it simple and instead offer a substantial discount on the replacement license. We hope this makes up for the lack of transferability. If you want to take advantage of this, please start the license purchase process from your new computer and look for the “Discount for additional license” section (bottom half of the license purchase page). The current price for an additional license is $1.99. We hope you will consider this as a small fee for issuing a replacement license.

First of all, thank you for purchasing the license.

You should receive a license file in an email from support@bluetoothgoodies.com shortly after the payment is completed. If you do not receive the email within an hour, please:

1. (If you paid with PayPal) Check the PayPal transaction status.

Please check the email from PayPal or log in to your PayPal account and check the transaction status first. Sometimes the transaction remains in "pending state" for some time (up to a few days). If this is the case, we cannot issue a license until the status changes to "complete".

2. Make sure you are looking at the correct mailbox.

If you paid with PayPal, the license file will be sent to your PayPal account's email address. This may be different from the address you usually use. Please log in to your PayPal account and check your account profile if you are not sure.

3. Check if the email was mistakenly marked as a SPAM mail.

The vast majority (>99%) of the license delivery emails make it to the inbox. Unfortunately, some of them are misclassified as SPAM mail (this seems to happen more often with smaller email providers and self-managed email servers). So please be sure to check your Junk/SPAM folder before contacting us.

4. If you don't find it in your Junk/SPAM folder, please contact us at support@bluetoothgoodies.com.

Please be sure to:

• Confirm and mention that you have checked your SPAM/Junk mail folder.
• Send the email from the email address you used to purchase the license.
• If you have another email address that we can reach (preferably with different email provider/domain), please mention that.

Usually, resending to the same address doesn't work well. If you have a different email address, this would increase the chance of successful delivery.

We will get back to you as soon as possible. Please allow up to one business day for our response.

In some cases, the license delivery email bounces back (this usually happens if you misspelled your email address). If this happens, we will:

1. Retry two more times to make sure that this is not a one-time error.
2. And, wait for two days for you to contact us.
3. If we cannot reach you in two days, we will cancel the license and issue a full refund.

Once this happens, we will refuse to sell the license to the same email address to avoid repeated failure.

If it has been less than two weeks since you purchased the license file, we can resend it to you free of charge. Please contact us from the email address where you used to receive the license file.

Otherwise, you can request to reissue a license for a small fee. Please start the normal license purchase process. Once you are on the license purchase page, please use the "Discount for additional license" section at the bottom half of the page. The current price for an additional license is $1.99.

The current version (version: 1.0.5) has the following limitations.

• Error recovery is minimal.

If something goes wrong during the CODEC configuration process, which usually happens when the device is connected, Windows recognizes the device is "connected", but the device does not work as an audio device.

If this happens to you, please turn off the device, wait for the OS to recognize the device's disconnection, then turn it on and attempt reconnection. If the problem persists or occurs frequently, please send feedback using the in-app feedback page.

• WASAPI exclusive mode and pull (aka. event-driven) mode cannot be enabled simultaneously.

You can enable exclusive mode or pull mode, but not both simultaneously. If your media player application does so, you will probably not hear any sound.

This limitation was resolved in version 1.0.5.

As you can see in the app's user interface, there are many options for A2DP CODEC configuration. All devices that claim compatibility with A2DP specification have to implement those options properly, and the manufacturers should test whether those options work before they ship the devices.

But, historically, PCs and phones used only one setting (44.1 kHz sampling frequency, Joint Stereo, block size 16, loudness allocation, eight subbands), and the device vendors never tested their products with other settings. I suspect many of them don't even have a way to test their devices. So, you are probably the first person to try different configurations, and there's a good chance you will find out they are not working.

If you encounter the issue, please try the following:

• Click on the "Load safe parameters for the CODEC" button and load the most commonly used parameters.
• Turn the device off, then on, and reconnect.
• Check if the device is working correctly.

If the device works with the safe parameter and has a problem with others, it's most likely an issue with the device. Please DO NOT report such an issue unless you have a good reason to believe that this is a driver issue. When you report such an issue, please include:

• The reason why you think/suspect this is a driver issue, and
• Mention that you've read this FAQ.

This will help your feedback to get the proper attention.

This problem occurs because the Windows inbox A2DP driver refuses to unload when it is nicely asked to unload.

Unfortunately, we cannot change the behavior of the Windows inbox A2DP driver, but instead of rebooting the system, you can shortcut the process by toggling the Bluetooth radio off and on from the Windows Bluetooth control panel. It will force the Windows inbox A2DP driver to unload and allow the Alternative A2DP driver to take over.

Software volume control (the volume control from the Windows user interface) may not work with some devices. We are working on this issue and hope to resolve it in a future release, but if you are experiencing this problem, please try the following workarounds:

1. If you have not restarted your PC since installing the Alternative A2DP Driver for this device, please do so.
2. If restarting does not help, try using one of the remote control buttons on the device (such as play, pause, ff, and rew). Volume control may begin to work.

This problem was fixed in the version 1.0.5.

Both Windows Sonic for Headphones and Dolby Atmos for Headphones support only a limited wave format. (This is a limitation of each spatial sound implementation, not a limitation of the Alternative A2DP Driver.) For example, as of this writing in February 2023, Dolby Atmos for Headphones (Windows 10 version) does not support 88.2/96 kHz formats.

Therefore, if you need to enable this feature, be sure to select the formats supported by each spatial sound implementation.

aptX

aptX (original/classic) and aptX-HD support may be added in the near future. However, other variants, including LL and Adaptive, are not included due to patent/licensing reasons.

MPEG AAC

AAC is also patent-protected. But there's a well-established licensing system. So it's possible to add AAC to the Alternative A2DP Driver. However, I have the following concerns/questions:

• To license this CODEC, I have to pay the license fee to the patent holder. This adds about $2 to the cost of the Alternative A2DP Driver.
• The CODEC implementation may not be as good as Apple's (should be similar quality to Android's).
• Given that Windows 11 supports AAC (at no additional cost to the user), and that more than half of the Alternative A2DP Driver users have upgraded to Windows 11 (and increasing), I wonder if there is enough demand for AAC support.

So, if you need a version with AAC support, even if it costs $2 more than the regular version, please send me feedback using the in-app feedback form. I would especially appreciate if you could explain why using Windows 11 AAC support is not an option for you.

In the meantime, I recommend trying SBC with high bitpool. If you compare SBC to AAC at the same bitrate, there is no question that AAC sounds better. But if your setup can handle high bitrate transmissions stably, high bitrate SBC often sounds better than lower bitrate AAC. Please see another FAQ topic: Increase the bitrate for better sound quality.

One of the reasons why you hear the stuttering/choppy noise is the high rate of data re-transmission between your PC and headphones due to the poor radio condition. When there is too much re-transmission, some media packets are not received by the headphones on time, and as a result, you will hear stuttering/choppy noise.

One of the solutions for this issue is to reduce the amount of media data that needs to be transmitted (by slightly decreasing the audio quality). Please move the "Bitpool" slider to the left (decrease the bitpool value) while you are playing audio and see if the noise is reduced.

There are two ways to increase the bitrate of SBC CODEC.

Method 1: Use Dual Channel mode instead of Joint Stereo mode — Guaranteed to work by the A2DP specification, but not so efficient

The first way is to use the Dual Channel mode instead of the commonly used Joint Stereo mode. Due to the peculiarity of how the A2DP specification is defined, a device that supports maximum bitpool N (this bitpool number is assigned to combined left and right channel) is required to support the same maximum bitpool number N in Dual Channel mode, where each channel is encoded into that bitpool N. So, the resulting bitrate will double if you use the Dual Channel mode. Sounds too good to be true? Of course, there is a catch. Because the Dual Channel mode encodes the right and left channels independently without taking advantage of the correlation between the channels, it cannot compress the data as efficiently as the Joint Stereo mode. For example, when you compare Joint Stereo mode at bitpool 2 * N and Dual Channel mode at bitpool N, they yield (almost) the same bitrate, but the Joint Stereo will sound better.

Please also note that if you switch from Joint Stereo to Dual Channel without changing the bitpool number, the resulting bitrate may be too high to transmit stably due to the error and re-transmission.

Method 2: Use Joint Stereo mode with a higher bitpool number — May work with many, but not all headphones

The other way to increase the bitrate is to simply increase the bitpool number while still using the Joint Stereo mode. Most devices limit the maximum bitpool number to 53 (or even lower), but some allow a higher bitpool number. If your device is one of them, you can safely increase the bitpool number (slide to the right) and see how far you can go.

For the devices with a maximum bitpool number of 53 or lower, the Alternative A2DP Driver provides an option to override (ignore) that limitation and let you try a higher bitpool number.

Windows inbox A2DP driver supports only 44.1 kHz sampling frequency for SBC CODEC. So, if you listen to the contents encoded with 48 kHz sampling frequency, you are forced to down-sampling.

On the other hand, Alternative A2DP makes all sampling frequencies supported by your audio device available to the media player app. So, if the media player app can dynamically switch the sampling frequency based on its source, you can eliminate the audio quality loss due to the down-sampling.

Please follow the instructions below to enable this feature.

Alternative A2DP Driver setting

First, you need to configure the Alternative A2DP Driver to use both 44.1 and 48 kHz sampling frequencies.

It is recommended NOT to enable other sampling frequencies (i.e., 16 and 32 kHz) unless you really want to use them.

(optional) Verify the above setting is working

1. Connect your Bluetooth audio device to your PC.
2. Type mmsys.cpl into the Windows search box and hit ENTER to start the legacy Sound control panel.
3. Select the Playback tab (which should be selected by default), look for the Bluetooth audio device, and double-click on it to open the Headphones Properties dialog box.
4. Select the Advanced tab and check the drop-down list in the Default Format section. You should see "2 channel, 16 bit, 44100 Hz (CD Quality)" and "2 channel, 16 bit 48000 Hz (DVD Quality)". If you do, the driver is working fine.

NOTE: This drop-down list is supposed to let the user select the audio stream format when this audio device is used in the Shared Mode, but it does not seem to be working on recent Windows 10 and 11. The cause is unclear at this point, but it seems to be an issue with Windows 10 and 11.

Media player app setting

The media player app has to support the Exclusive Mode (and please note that not all media app does) so that it can change the sampling frequency of the audio device. (When the device is used in the Shared Mode, the sampling frequency is controlled by the System Mixer, and media player apps cannot control it.) Please also note that, by definition, in the Exclusive Mode, your audio device is exclusively controlled by that media app, and the output from other apps (including the system sounds) cannot be played on the same device.

Following are some of the apps that support Exclusive Mode and how to configure them for the dynamic sampling frequency change.

Kodi

1. Navigate to the "Settings" > "System" > "Audio" page.
2. Set the settings level (at the bottom-left corner) to "Advanced" or above.
3. Select "WASAPI: Headphones (...)" or "WASAPI: default" for the "Audio output device."
4. Select "Best match" for "Output configuration" (this setting item does not show if the setting level is "Basic" or "Standard").

MPC-BE

1. Navigate to the "View" menu > "Options ..." to open the "Options" window.
2. Select the "Audio" node in the left pane.
3. Select "0. MPC Audio Renderer" for the "Audio renderer" drop-down list.
4. Click the "Properties" button to open the "Properties" dialog box.
5. Select "Exclusive" for the "WASAPI mode" drop-down list, and enable the "Allow bit exact output" checkbox.

MPC-HC

1. Navigate to the "View" menu > "Options ..." to open the "Options" window.
2. Select the "Playback" > "Output" node in the left pane.
3. Select "MPC Audio Renderer" for the "Audio Renderer" drop-down list.
4. Select the "Internal Filters" > "Audio Renderer" node in the left pane.
5. Click the "MPC Audio Renderer Settings" button to open the "Properties" dialog box.
6. Select "Exclusive" for the "WASAPI mode" drop-down list, and enable the "Allow bit exact output" checkbox.

Under the ideal condition (no transmission error/retransmission), Bluetooth can, theoretically, transmit up to ~1.5Mbps (assuming all time slots are filled with 2-DH5 packets) of the streaming data. But, in reality, radio signals are distorted by interference, and data needs to be retransmitted. As a result, the effective bitrate is much lower than that. If you are trying to use high-bitrate CODEC settings (such as SBC bitpool above 100, LDAC with HQ quality), you may need to pay attention to the following factors:

1. Minimize radio interference to reduce the retransmission
• Do not use 2.4GHz radio, such as 2.4GHz WiFi

Use 5/6GHz WiFi or wired Ethernet instead.

• If you have to use 2.4GHz WiFi, consider using a WiFi/Bluetooth combo adapter instead of separate adapters

WiFi and Bluetooth adapters communicate with each other and minimize interference in a combo adapter. They do not communicate with each other if you use separate adapters and cause more interference.

2. Use high transmission power Bluetooth adapter

Bluetooth devices are classified into three power classes. Most Bluetooth adapters used for PC are either Class 1 (high power) or Class 2 (medium power). A Class 1 adapter gives you a more stable connection at a high bitrate. As of this writing, there is no easy way to tell if your adapter is Class 1 or Class 2, but here is a rule of thumb:

• Most integrated (the adapters integrated into the laptops and the desktop's m2 slot) adapters are Class 1.

• External USB dongles are a mix of Class 1 and Class 2 (unless advertised as Class 1, the chance is it's Class 2). Please check with the manufacturer of the adapter.

3. Maximize the time slot used by other Bluetooth devices

If you connect other Bluetooth devices, such as a keyboard, mouse, and touchpad, they eat up the time slots that can be used for audio streaming. The amount of data those devices send is relatively small, but their impact is not negligible as they send the data frequently.

Those devices may need to be turned off while high-bitrate audio streaming is happening to free up the time slots usable for audio streaming. (Or, if you use the high-bitrate audio streaming regularly, you may want to consider switching to the mouse/keyboard that uses non-Bluetooth wireless technologies.) Please note that those devices still consume timeslots while they are idle as long as they are connected to your PC.

4. TWS specific issues

Last but not least, TWS headphones are not good at receiving high-bitrate streams. You usually start hearing choppy sounds at a lower bitrate compared to regular headphones. This is because:

• Due to their smaller size, they don't have good antennas. It causes more data corruption and ends up with more re-transmission.
• Earbuds need to communicate with each other, and that is done using the Bluetooth time slots otherwise used to receive the streaming packets.

For example, LDAC HQ (990kbps) with TWS is not impossible, but for that to work without choppy noise, you need to clear all other issues listed above.

Here's the list of the links to some of the information.

• A2DP specification (Bluetooth SIG)

  Definitive definition of what every A2DP device has to support/implement.

• Audio quality of SBC XQ Bluetooth audio codec
• Bluetooth stack modifications to improve audio quality on headphones without AAC, aptX, or LDAC codecs

  Explain SBC CODEC with high bitpool option.