Bluetooth Tweaker License File
Dallas Themshirts
And here comes the problem stated in the title of this article. Windows, for whatever dumb reason just pick codecs almost on random at this point. Most bluetooth audio devices these days support SBC and AAC codecs, of which AAC is superior. However, there are also AptX from Qualcomm and LDAC from Sony, both superior to AAC and especially SBC which just sounds horrendous in comparison.
Turns out even Linux has Bluetooth in better state. Using Pipewire Audio subsystem and you can use any codec in a matter of 2 clicks. Not only I could use AptX easily on my laptop paired with SounPeats TrueAir 2, I could even select SBC XQ on the other where I had AirPods 2 paired with it. AirPods only support SBC and AAC, no LDAC or AptX, but still, seeing SBC with higher quality profile (XQ probably stands for Xtreme Quality) which sounds way better.
A few months ago Windows 10 introduced update 1803, which changed the volume control for bluetooth devices. My Augustus EP650 bluetooth headphones used to have separate volume control on the desktop and on the device itself (e.g. you could make the Windows volume very loud, but the device volume very quiet, for an average final volume). After the update both volumes are now linked and change together.
Windows bluetooth dev here - if anyone can't control their BT speaker/headphones volume from the PC after the update, can you share a product link to what device you're using? We added "absolute volume" in the last update which lets the Windows volume slider directly control the local volume of BT speakers/headphones who support it.
To use reg file; copy and paste this code to new notepad file and save it to DisableAbsoluteVolume.reg (you have to enable show file extension otherwise your file will be DisableAbsoluteVolume.reg.txt and it is text file) Now you can double click to this file and click yes to use it.
Windows makes it unnecessarily hard to identify the audio codec used by the Bluetooth A2DP profile, but there is a way. This post shows how to check if your connection makes use of aptX, LDAC, or some other more advanced codec, or if it falls back to SBC.
Close all the default charts and tables in the main area by clicking the x in the upper right corner. Then double click the preview chart below System Activity in the upper left corner. The window should now look like this:
We are only interested in the second event with the task name A2dpStreaming. Unfortunately, the default columns do not have any meaningful information for us, and WPA makes it really quite hard to get to the interesting fields.
De-select the fields Id, Process, Cpu, and ThreadId. From the left column drag and drop the fields 4 through 6 (Field 4, Field 5, Field 6) to the main area below the golden bar. It should look like this:
Looking once again at my values, we see in the tables above that a standard codec ID of 0xFF indicates a vendor-specific code. We can learn from the corresponding table that the vendor ID 0x004F and the vendor codec ID 0x01 stand for the aptX codec. This proves what I had suspected in my original article: Windows 10 supports aptX.
Ok, now I made sure to play longer periods about 3 min in total. I was switching the output device. Using different players. And then made sure to disconnect the bluetooth device and disable bluetooth before finally stopping the capturing of events.
Dear Helge,
Thank you for this article. I have the latest Windows 10 and a two month old motherboard with BT5.0 built. But my BT headphones sound horrible with Windows. They sound excellent wired in and very good via BT on my phone. Why does Windows sound glaringly horrible, and what can I do about it? Not clear how following the instructions in this article would help.
Appreciate the help.
Not sure which headphone you have, but it is most definitely a bluetooth Codec issue.
Windows 10 Support SBC (low quality), AptX( medium high quality) by default, plus any additional codec support comes with your bluetooth adapter.
Most androids support SBC, LDAC(high quality), some support AptX and AptX HD (The high quality version of AptX)
There is no good solution to your problem. These codecs are often intellectual properties of their makers, and they charge money for having those supports. Your best bet would be buying a USB bluetooth adapter that supports the higher quality Codec your headphone supports.
Dear Helge,
thank you for this great article.
I have 0 in all 3 fields. Does that mean that my connection is using SBC? I am testing a pair od Sony WF-1000XM3 earbuds and was expecting APTX :(
Thanks,
Rob
IF you read through the comments you will see several people with the same problem had succes when they un-paired, started logging and then re-paired their device, then started to play music and logged for like a minute.
Thanks for the guide. Just to add on for other passersby: Another way I stumbled over is looking at the bluetooth traffic in Wireshark. The Microsoft Bluetooth test platform ( -us/windows-hardware/drivers/bluetooth/testing-btp-software-package) makes that super simple. It contains a tool btvs.exe which captures the bluetooth traffic and makes it available to wireshark in realtime (see -gb/windows-hardware/drivers/bluetooth/testing-btp-tools-btvs#usage-for-wireshark-on-separate-machine). That makes it easy to see the handshake, all the device capabilities as well as the actual codec stream later. Wireshark comes with matching protocol disectors so even without knowing much about bluetooth it was easy to follow as wireshark spells it out for you. Maybe a bit overkill for this but very interesting to play with.
This article explains how to install a Samba v4 Active Directory domain controller in a Docker container. It's part of a mini-series about running Samba Active Directory and file server service on a home server.
Windows 10 allows you to pair your PC or laptop with other devices like smartphones, tablets, wireless mouses and keyboards. If your PC or laptop has the bluetooth hardware installed, you can connect any of your wireless devices to that PC using the bluetooth protocol. Today, we'll see how to add the useful Bluetooth context menu to the Desktop in Windows 10. This will allow you to access all the bluetooth features much faster.
To access Bluetooth from the context menu in Windows 10, you need to apply a special Registry tweak which will add bluetooth options to the Desktop's right-click menu. Before you continue, ensure that you are signed in as Administrator, otherwise the tweak won't be applied.
Obviously, you need Bluetooth hardware installed and configured properly in order to get the context menu items working.
Double quotes are important to ensure that the file will get the "*.reg" extension and not *.reg.txt. You can save the file to any desired location, for example, you can put it in your Desktop folder.
Tip: Winaero Twеaker is essential software for every Windows 10, Windows 8 and Windows 7 user. It allows you to customize the appearance and behavior of the operating system in a flexible way.
Try Winaero Twеaker now!
Hello, I have Sennheiser MOMENTUM Wireless M3 headphones. These headphones support aptx and aptx low latency bluetooth codecs, but unfortunately, they connect to my laptop by AAC codec, which causes big delay.
So can you help me, and tell how to install or enable the aptx/aptx low latency codec?
Attaching the screenshot from Bluetooth Tweaker
Hi,I'm not an expert,I only know some basics but I need help with something,Poweramp downsamples sample rate to 44.1 khz when with other players I can achieve 48 khz,thing is this,my phone in other player achieve 48 khz with aptx (non hd) of my Bluetooth earphones but when I go to Poweramp it downsamples to 44.1 ,why? Aptx support 48 khz and my phone supports higher than. 48 too ,I want to achieve bit perfect with my Bluetooth earphones with aptx codec since my files are 16 bit wav and 48 khz ,again why does it downsamples?
Poweramp automatically chooses the target BT codec sample rate (44.1kHz in your case). That rate is specifically reported by bluetooth stack and used by audio flinger. Forcing 48kHz means double resample for 44.1kHz tracks.
IF my phone SUPPORTS 48 khz and/or higher and SUPPORTS APTX and in earphones have APTX with max sample rate at 48 then why Poweramp downsamples it? Basically what I see is I should play 48 wav with no problems and resampling
I know this is off topic but since you guys are experienced audiophiles I have a doubt please explain,I read when you match Dolby contents ac3 file plus a device compatible dolby it enhances the experience a lot ( I know its kinda obvious) but is it totally true? Because my phone has Dolby Atmos preinstalled and when I turn it on with songs converted to ac3 it sounds so awesome,like surround effects on songs are more defined and the song sounds quite impressive!
AC3 is a file extension for surround sound audio files used on DVDs format. The AC3 file format was created by Dolby Labs for use in a Dolby Digital audio on DVD, Blu-ray and other digital video formats. AC3 stands for Audio Coding 3.
AC3 increases fidelity over its previous surround sound standard, Pro-logic, with independent tracks for each of the 6 speakers, a 16bit sampling at 48khz rate compressed by 10- 12 times, making for a total bit rate of 384kbps.
ff7609af8f