Datasets:
kkboy1
/
LeAudio

Dataset card Data Studio Files
xet
 Community
1
text
stringlengths
1
112
single device can manage both there are similar opportunities for the companies currently
making and installing telecoil loops where they will see their business open up to a far wider
range of customers it will need apps developers to be aware of how broadcast works to
provide the user interfaces
on which front it is important to point out that these applications will only happen when
silicon operating systems and application developers understand the full potential of
bluetooth le audio and include support for the features which enable these different use
cases in the early days some of these may not be possible as developers naturally concentrate
on releasing what they consider t o be t he most obvious applications over time as the market
learns and we get a critical mass of products the more complex use cases will emerge
hopefully with simple and intuitive user interfaces
combining bluetooth classic audio with bluetooth le audio
bluetooth classic audio implementations will not disappear in the short term the majority
of audio products in the market today use pre chipsets which arent upgradeable and many
products from tvs to cars have a life of ten years or more for at least the next five years
phones and most earbuds will support both bluetooth classic audio and bluetooth le audio
where both support the same use case such as with hfp and adp it will be up to the
implementation to decide which to use in phones that will largely be down to the individual
manufacturer and the silicon implementation products with a wider variety of stacks and
chapter bluetooth le audio applications
open source applications may be mor e diverse
the important point for developers is to make sure it works for the user whilst cap includes
handover procedures for moving from unicast to broadcast these only apply where both are
bluetooth le audio in the real world its equally possibl e that the transition may be from
adp to le broadcast and then back to le unicast or classic bluetooth for product
developers the rule must be to anticipate and allow any combination the bluetooth sig
runs regular unplugfests where developers can tes t their products with those from other
manufacturers as products start to incorporate more and more of the new features of
bluetooth le audio the se will be invaluable to ensure an interoperable ecosystem and a
degree of uniformity in user experience
concentrate on understanding broadcast
one of the learnings from developing the specification is how difficult the concepts of
broadcast are for anyone who is used to the peer topeer model of hfp and adp whilst
unicast includes a lot of new concepts see chapter to review them the acknowledged
packet model in a piconet is relatively familiar broadcast with a transmitter that is unaware
of whether anyone is listening to it and receivers which act totally independently and have no
state machine hav e been surprisingly challenging for many to take in adding bass alongside
the broadcast assistant and the delegation of scanning does seem to be a challenge to that
orthodox thinking
the examples in this chapter try to illustrate the flexibility which is allowed developers need
to understand the limitations that are imposed by broadcast that each big has a fixed
structure for all bises which may mean there are times when multiple bigs are more efficient
scanning and filtering broadcasts is all i mportant for a good user experience so the relevant
fields need to be supported and where appropriate configurable by users they must
understand the basic audio announcement the use of targeted and general announcements
by initiators and acceptors an d the meaning of the base structure the interaction between
broadcast assistant s and scan delegators and the use of the characteristics in bass are
fundamental to the sharing and authentication processes described above
finally anyone designing with bluetooth le audio should take time to understand and
implement the control features and appreciate the fact that they can be distributed between
multiple different devices these are all simple clientserver relationships but the contents
of each of the s ervices are very comprehensive and make the difference between a rich or a
basic user experience
although it is a basic le feature developers should also make sure they understand the role
of notifications in bluetooth le audio notifications are the m eans whereby server s ensure
that everything within the topology is up to date knowing when to expect them and what
to do if they dont arrive when expected which is normally to go and read the characteristic
is vital to provide a robust ecosystem whe re a user can pick and choose multiple products
section market d evelopment and notes for developers
from different manufacturers and have confidence that they will all work with each other
balanc ing quality and application
developers should not forget the difference between optional and mandatory in the
bluetooth le audio specifications in many of them v ery little is mandated many features
are mandated to be supported such as the mandated codec settings in bap and tmap but
that doesnt mean that an application needs to use them the mandat e is that if an application
chooses to use them they must be supported if theyre only optional and an application on
an initiator wants to use them the acceptor can reject that request it means that there is a
lot of flexibility in what a product c an do
having said that going off piste may impinge on interoperability as an example t he qos
settings in bap have been thoroughly tested and developers can be sure that every silicon
supplier will have made sure their implementation is interoperable so they should be used
however there will be times when physics gets in the way typically if you want to transmit
multi ple audio streams where you will begin to run out of airtime we know from a history
of audio development that consumers dont nec essarily want the highest quality they want
ease of use cds and streaming services became successful because they were easy to use and
the audio quality was adequate the companies that invented them understood that by being
brave and taking a step b ack from the audio quality treadmill they could provide an experience
that allowed them to win customers hearts bluetooth le audio has potential for new
compelling services which should be designed with that in mind the audio quality is there
when it is needed but so is a lot else
reinventing audio
in the last few decades the way we consume audio has become concentrated into the hands
of phone manufacturers and streaming services what actually renders it notwithstanding the
inordinate success of apples airpods and their competitors is largely the tail of the dog
hearables have added neat features but they havent really played any major part in the
development of the audio chain they remain a passive peripheral to the phone bluetooth
le audio s new topologies and distributed control features provide the potential for a new
generation of innovation where devices we have yet to imagine become an important part of
our lives at that point the hearables tail could start wagging the dog the aim of everyone
involved in th e bluetooth le audio development has been to provide the tools for a new
generation of innovation i hope this book has inspired you to think outside the box and
consider how that can be achieved
chapter glossary and concordances
chapter glossary and concordances
in this final chapter ive listed all of the specifications which comprise bluetooth le
audio the acronyms used in this book along with a list of all of the bluetooth le audio
procedures and sub procedures along with where they are defined i can only hope to
provide an overview of the specifications within this book these cross references should
help you navigate your way through the specifications