Відео

Currently no. Audio switch requires Google Fast Pair Service, but Android Authority has posted an article "Fast Pair now supports earbuds with Bluetooth LE Audio, but seemingly only on Android 15." www.androidauthority.com/fast-pair-bluetooth-le-audio-3480970/ We may see Audio switch working on LE Audio earbuds in the near future.

@dangerza Every time we activated the microphones on the LE Audio earbuds while playing stereo music, it became mono. It seems "1 channels, 16 bit, 32000 Hz (FM Radio Quality)" always applies when you use the built-in microphones and speakers on LE Audio earbuds simultaneously, at least in the current implementation of LE Audio.

@fdimb We haven't tested on any Linux setup. Can't say anything about it.

@RxMaxx What smartphone model are you talking about?

@@GadgeTweet-dn7gk Sony Xperia 5V

​@@RxMaxx Our test device, the Xperia 5V XQ-DE44, has been updated to Android 14 67.1.A.2.256, yet both LE Audio and Auracast still work on it as demonstrated in the video.

​@@GadgeTweet-dn7gk Broadcasting works, but listening to someone else's broadcast doesn't. There is no such option in the settings.

@RxMaxx There is no such an option in the settings. Auracast just functions as shown in the video. In our recent test, the Xperia 5V successfully received an Auracast broadcast from a Galaxy S24, and the S24 received a broadcast from the 5V. We've recorded the test and we can share it if you want.

@RxMaxx We've only been successful in using LE Audio on Intel Core Ultras and Qualcomm Snapdragon Xs. We doubt it would work on 13th/14th Gen Intel Cores.

@xyzzy12345 That's exactly what the manufacturers been working on.

@hebestreitfan6973 We've published another video demonstrating how LE Audio works on Windows 11. ua-cam.com/video/ZbPAUJiBVKA/v-deo.html We've discussed about the microphone quality in the video. But you may have to wait for GMAP implementation to achieve what you've hoped for. Please check the following link for further discussion. x.com/aborne25/status/1812081027734728797

@AV1461 We've provided the subtitles in case you can't hear over the music. The Pixel 8 Pro doesn't support Auracast. At least not for the moment. You may have to switch it to a Galaxy or an Xperia. You might want to wait for Android 15 to see if it brings the feature to the Pixel.

@@GadgeTweet-dn7gkJust to confirm. Neither Auracast nor the broadcast feature of Bluetooth 5.2 LE and older work on Google Pixel 8 Pro? So there is no way to play on two Bluetooth devices from this phone simultaneously as of now?

​@@AV1461 The broadcasting feature of LE Audio has been rebranded as Auracast. It's the first broadcasting standard for Bluetooth Audio, and not supported on any Pixel phones as of Android 14. Some manufacturers have implemented proprietary audio sharing features, such as Share audio with 2 sets of Apple/Beats headphones from an iPhone/iPad, or Dual audio with 2 sets of any Bluetooth Classic headphones from a Galaxy phone. But no such feature on Pixel phones. If you want to use 2 pairs of Bluetooth headphones on a single Pixel phone, you would have to use a transmitter.

@fdimb The Creative implementation of LC3plus is ULL, which supposedly provides lower latency and lower sound quality than standard LC3. We'll wait for some other implementations for the test. LE Audio expectedly produce clearer calls than Classic Audio, but we're still developing how we test and demonstrate it.

@@GadgeTweet-dn7gk thank you!!

Duplex mode works with the LC3 codec, but the quality is reduced, although the sound remains stereo. But for LC3+ the quality does not noticeably reduce! But the LC3+ has a shorter range. I mean headphones (output), it remains stereo in LE Audio. In classic mode, when using a microphone, the headphones play in mono. The microphone is mono in any mode.

@@RxMaxx When you select an LE Audio device as an input device on Windows 11, the call quality will be 1-channel, 16-bit and 32kHz. And I've never seen LE Audio devices using LC3plus for calls. What devices did you use then?

@@GadgeTweet-dn7gk I mean headphones (output), it remains stereo in LE Audio. In classic mode, when using a microphone, the headphones play in mono. The microphone is mono in any mode.

I don't think the grandson's old smartphone supports Auracast, though. Some HAs automatically join nearby Auracast stream when entered a broadcast mode. However she may encounter difficulties when she needs to join an encrypted Auracast stream, or one particular stream out of multiple streams. Then she has to go through the process demonstrated in this video.

@@GadgeTweet-dn7gk There are currently only three hearing systems that are prepared for Auracast: GN Resound Nexia, Signia IX and the Cochlear Nexus CI. None of these devices automatically switch to an Auracast stream. This was an idea from a time when a barrier-free operating concept for BLE audio was being sought. At that time, they only wanted to allow one Auracast station in the region. However, they quickly realized that they were tripping themselves up. An automatic system cannot decide which stream I want to listen to. And an automatic changeover would also violate users' right to self-determination, as they might want to have a side conversation but would be forced to listen to the Auracast stream by an automatic system. However, a barrier-free operating concept has not yet been found. And an Auracast-enabled smartphone at a price starting at 800$ does not promote accessibility either, but is socially marginalizing, especially since the Auracast-enabled hearing aids also cost an additional 3000-5000$. This cannot be paid for with a normal pension and older people in particular are disproportionately hard of hearing. Auracast is therefore not barrier-free and is also socially marginalizing.

Well I was talking about something like Creative Zen Hybrid Pro headphones. support.creative.com/kb/ShowArticle.aspx?sid=200948 They can connect to an Auracast stream in a few seconds when entered Broadcast mode. It's a lot simpler than what we've demonstrated in the video. I assume there will be HAs with similar controls.

@@GadgeTweet-dn7gk If the headphones know the MAC address and other parameters of the Auracast transmitter, connecting to the stream is no problem. This is also the case with the previous TV streamers and hearing aids from the same company. Once paired, all you have to do is press a button on the hearing aid one to three times and you can hear the stream from your private TV streamer. But that's not the core problem. Auracast is supposed to be a technology without pairing: Broadcast. If there are several transmitters and streams in a public space, e.g. at an airport, then I have to use a smartphone app to select the stream that interests me at the time. And that's where the problems start for older people who weren't born with a smartphone in their hands. Let's take the example of a town hall where lectures are held or political events take place during an election campaign. If hearing assistance for the hard of hearing is solved via Auracast, all those who do not have a smartphone or cannot use it, e.g. for medical reasons, are excluded. Participation and involvement in social, cultural, political and religious life is no longer guaranteed for this large group of people. This is deeply undemocratic. Auracast for private use is ok, but as support for hard of hearing in public spaces is not ok.

@user-qj2hk7oi7r i.imgur.com/oHkvIOD.jpg 4 taps on MoerLab hearClear earbuds to enter Auracast (Broadcast) mode, and the earbuds will search and connect an Auracast stream. You can triple-tap them to switch to another Auracast stream if there are multiple streams nearby. You don't need a smartphone to browse through multiple Auracast streams.

Round-trip latency is the sum of output latency and input latency. Adding 80 msec to 83 msec will never give you the total latency for LE audio.

I understand your comment to mean that you are assuming an even higher latency. I have calculated very graciously. According to your information, Auracast is obviously even less suitable for assistive listening. This means that the Bluetooth SIG has raised false hopes for all hearing impaired people, who will now be bitterly disappointed. Moreover, Auracast is not barrier-free anyway, because an Auracast-enabled smartphone is always required in addition to new hearing systems. However, a smartphone is not a disability-related aid and is therefore not barrier-free. With Auracast, hearing and understanding are not only dependent on the hearing system, but also on a smartphone, its battery status and the user's ability to use it. According to a representative survey, more than half of people over the age of 65 do not use a smartphone, partly due to other disabilities. These people are therefore excluded from participation in social, cultural, political and religious life.

@@NorbertMuth When you experience audio delay over the video, it's output latency. We've subtracted the 29 msec from 83 msec to get the output latency from the LE Audio transmission. Hence the 54 msec will be the latency you should experience when you have the same setup as we do. We haven't tested Auracast for the latency, but usually lower bitrate values are used for Auracast broadcast than LE Audio Unicast. Auracast expectedly provides slightly lower latency with lower sound quality.

@@GadgeTweet-dn7gk The 29ms is the time the audio system needs without a codec process, so the 54ms is the time the LC3 needs to decode. But if I have a full process: an Auracast transmitter that has to encode and needs 43ms like the GN-Resound TV Streamer+ and the signal goes directly into a hearing aid and has to be decoded there with a very weak CPU, then the whole thing adds up to at least 100ms or more. That's definitely too much for the lipreading, on which the profoundly hard of hearing depend. An example: in-ear monitoring for stage musicians must not exceed 10ms, otherwise the musicians will lose their rhythm. (Source: A Shure webinar on wireless audio transmission.) For the hearing impaired, the maximum latency between seeing and hearing is said to be 20-30ms. If I'm watching a movie on a newer TV, I may be able to delay the video, but if I'm in a lecture, that's not possible, as understanding is limited. But nevertheless: I think your work is great and you are only the testers for the technology, not the designers.

Whatever the audio signal must be decoded to PCM and handed over the Bluetooth module inside the smartphone. The Bluetooth module encodes it to LC3 and transmits it over the BLE radio. Then the earbuds receive, decode, and convert it to analog signal before outputting it. The 54 msec includes this whole process of the LE Audio transmission. According to ITU-R BT.1359-1, detectability thresholds in sound/picture timing are about +45 ms to -125 ms, and acceptability thresholds are about +90 ms to -185 ms. I wonder how you tested if 100 ms is too much for the lipreading.

I don't think so.

@FrostArchon No. Currently I have no access to a Galaxy S23 Ultra to check.

I've got a chance to try a Samsung Galaxy S23 Ultra. ua-cam.com/video/DwDbAv8XB5k/v-deo.html When you connect an LE Audio device to it, you'll find the LE Audio toggle switch in the device detail. You can use LE Audio/LC3 if you turn the toggle on.

Unfortunately the S23 doesn't allow the buds 2 pro to operate in LE Audio mode for some reason. When using the S23 with Buds 2 Pro it locks you to only use their samsung scalable codec.@@GadgeTweet-dn7gk

superpowered.com/latency