I tried out my Bose QuiteComfort II noise cancelling wireless headphones. They work, but the ASIO drivers all give me unacceptable latency, including ASIO4All. I use an M-Audio M-Track interface with plugged in headphones using the M-Audio ASIO driver - latency is almost imperceptable. So, no wireless headphones for playing on my keyboard with Music Maker.
>> the ASIO drivers all give me unacceptable latency, and >> plugged in headphones using the M-Audio ASIO driver - latency is almost imperceptable.
Hmmmm... It appears these are the earbuds -- is that what you have? The specs on the Bose site show BT 5.3, but don't mention latency, which makes me think these are "regular" latency. I'm guessing @johnebaker 's BT 'phones are low-latency, and that's why they work. ( @johnebaker can you confirm that?)
I learned about BT latency when searching for BT 'phones for my non-BT TV. Apparently regular BT audio is delayed by several milliseconds (I don't know enough about the technology to say why). If you're listening to music from your phone, it's not a problem. But when voice and lip movements are out of sync, it gets frustrating very quickly. The solution is to switch to a low-latency product. I ended up with a low-latency transmitter/headphone combo (which turned out to have such crappy sound I returned it).
As it happens, both JBL and Bose BT products seem to use an app for additional config and update functions. Me, I use an old clamshell phone, which makes things a little awkward here. I've found a couple of Sennheiser RF (not BT) headphones on Amazon, that I'm looking at. I don't think latency is an issue with these 'phones. And no apps. :-)
When I posted my question, I hadn't really thought through what I meant by the word "latency". I knew about BT latency, but I think had some more general fuzzy idea about possible delays with wireless reception.