Hi, just wondering if you've heard anything new.
From what I understand the ability to utilize the aptx (LL) codec depends in part on what underlying chipset is implemented for the bluetooth unit. For example THIS USB DEVICE implenments a CSR (Qualcomm) BlueCore 8670 chipset wherein the provided Windows 10 drivers allows it to transmit aptx (LL).
In part to figure out if the 7th gen NUC's are capable of doing this, we need to know what bluetooth chipset is in use (generally CSR / Broadcom support aptX), and then to know if Intel's driver package allows for transmit of aptX-LL.
It does support APTX but it is an additional component provided by the OEMs as Intel does not include at standard (costs additional licensing fees).
Dell does publish it for some of its systems just look for "Intel 7265/3165/7260/3160 Bluetooth Audio Application (WBS/APTX)" but it is version 17.x and unlikely to work on the 8265 but does work on earlier cards. You could always try it?
Is this the same as the 8265? Could your staff try to install these drivers on a 7th gen NUC to see if it works w/ an aptX-LL device?
I was led to this information from here:
It seems like it works according to folks who posted, but then again I'm not sure if the bluetooth chipset within the Intel 8260 is the exact same as the 8265. Can you confirm this?
have you found out in the end? I wanted to replace my card with this one as well
Looks like we're in luck according to one user on THIS thread (post #15)
well, i just tested it on my new machine with 8265 and it works just as on the ones with 7260.
aptx logo and options for aptx in settings.
The below would be the link to install the drivers.
I'm just kind of baffled as to why Intel isn't cross-licensing WBS/APTX within their own drivers. It's disappointing to be honest for those of us who fork out $ and have to scrounge around for other manufacturer's outdated windows 8.1 drivers. Lots of bluetooth products support APTX, and if we're to believe in the concept of the wireless home, it's painstaking to pair on bluetooth using SBC for any video/media content and have >250ms lipsync delays.
hm. thats me.
Yes it is the same on 8265 as on 7260.
BUT.. What is strange is that I have an avantree BT transmitter\receiver that I tested and it reports that windows is aptx before installing these drivers.
I just got the NUC7i3BNH. I did have an 3,5 year old zotac id64 mini pc, but it stopped working and the shop refunded me the purchase price that was more than the nuc....
I have an avantree pair of Aptx-LL headphones. That device has different blinking patterns which shows what connection type is at play. single blue blink = SBC. Single White blink = AptX. Double white blink = aptX-LL (low latency).
@marjo Does your transmitter/receiver blink in that same pattern? If so, can you confirm whether it's connected on aptx-LL using the standard Intel Wifi/Bluetooth drivers for 8265 (sans the Dell drivers)?
My impression from prior threads and replies from Intel was that AptX wasn't supported/incensed in the driver package they provide, but maybe they just give a template answer without actually checking on Windows 10
too late now, but I did test it on 7260 before installing the aptx.
But as I remember if you go to properties on the BT device it would use ms driver from something like 2006 before, after the aptx install the controller information is intel 17.1.1530.31
On the Avantree I think it was two blue blinks for aptx, and it was correct when I tested it before first trying these aptx drivers.
I find it very strange that Intel would not get a license for aptx for the nuc line. Problem is that it would probably apply to all intel capable cards. But Dell managed it.
The aptx notification is also good, no guessing what is used.
I have read previous threads and standard reply is contact OEM, but now Intel is it.
The 8260 family supports A2DP via aptx .
Keep in mind that the audio profiles are natively supported by Microsoft (by the Operating System) as well as the Bluetooth low energy support .
I am trying to get some documentation about the BT-LL. Will share when I get it.
I hope this helps,
If it's in the A2DP spec, it's still often hard to determine what is preferentially used in Windows. The drivers often dictate which is used (e.g. between SBC, aptX, aptX-ll, AAC, FLAC) and what the default ordering based off what's in common between the transmitter and receiver (without so much as letting the end-user decide). This is where the problem lies... if you want highest fidelity audio, you probably want FLAC or AAC (will encounter lag), but if you want lipsync, you want aptx-LL ordered first. From what I've seen, AAC is preferential to apple ecosystem, I've rarely seen FLAC supported, and aptX is a maybe.
So my questions are:
1) What are all the supported codec formats of the 8265 transmitter w/ standard Intel drivers?
2) If the receiving device supports all the codec formats of the 8265, what is the ordering/preference of codec (in Windows 10)? (Some devices, such as the Avantree Audition Pro will blink alerting you to this, and I'm sure other lab testing hardware will tell you what the codec type is in use on bluetooth)
Please allow me some extra time to get some answers, this goes beyond my Intel Wireless knowledge since I support NUC products mainly.
I will get back to you as soon as possible.
It is been really hard for me to get answers for your questions and I apologize for that and for the delay in getting back to you.
Windows/ 10 currently does not support Aptx low latency, however, since this is an Operating System feature, I would recommend that you verify with Microsoft*.