Lines Matching +full:reject +full:- +full:broadcast

9 The Acceptor will typically be a resource-constrained device, such as a headset, earbud or hearing
20 .. code-block:: console
23    cap_acceptor --help
24    cap_acceptor - Bluetooth CAP acceptor shell commands
27                     [rank <int>] [not-lockable] [sirk <data>]
33                     reject, oob>
39 ------------------
42 :code:`bt adv-data` or :code:`bt advertise` must be called again to set the new advertising data.
46 .. code-block:: console
52 ------------------------
56 .. code-block:: console
66 The Initiator will typically be a resource-rich device, such as a phone or PC. The Initiator can
69 stream control procedures on sets of devices, either ad-hoc or Coordinated, and thus provides an
77 The CAP initiator also supports broadcast audio as a source.
79 .. code-block:: console
81    uart:~$ cap_initiator --help
82    cap_initiator - Bluetooth CAP initiator shell commands
111      ac_12             : Broadcast audio configuration 12
112      ac_13             : Broadcast audio configuration 13
113      ac_14             : Broadcast audio configuration 14
120 --------------
124 .. code-block:: console
132 .. code-block:: console
175 .. code-block:: console
186 .. code-block:: console
191 When doing broadcast
192 --------------------
194 To start a broadcast as the CAP initiator there are a few steps to be done:
197 2. Create and configure a broadcast source
200 The following commands will setup a CAP broadcast source using the 16_2_1 preset (defined by BAP):
203 .. code-block:: console
207    bt adv-create nconn-nscan ext-adv name
208    bt per-adv-param
209    bap preset broadcast 16_2_1
211    bt adv-data discov
212    bt per-adv-data
216 The broadcast source is created by the :code:`cap_initiator ac_12`, :code:`cap_initiator ac_13`,
217 and :code:`cap_initiator ac_14` commands, configuring the broadcast source for the defined audio
218 configurations from BAP. The broadcast source can then be stopped with
221 The metadata of the broadcast source can be updated at any time, including when it is already
227 .. code-block:: console
230    CAP Broadcast source updated with new metadata. Update the advertised base via `bt per-adv-data`
231    bt per-adv-data
233 The :code:`bt per-adv-data` command should be used afterwards to update the data is the advertised
234 BASE. The data must be little-endian, so in the above example the metadata :code:`03020400` is
242 The Commander will typically be a either co-located with a CAP Initiator or be on a separate
243 resource-rich mobile device, such as a phone or smartwatch. The Commander can
246 information about broadcast sources to CAP Acceptors or coordinate capture and rendering information
255 .. code-block:: console
257    cap_commander --help
258    cap_commander - Bluetooth CAP commander shell commands
269      broadcast_reception_start : Start broadcast reception with
273      broadcast_reception_stop  : Stop broadcast reception <src_id [...]>
274      distribute_broadcast_code : Distribute broadcast code <src_id [...]> <broadcast_code>
282 --------------
287 .. code-block:: console
296 .. code-block:: console
315 .. code-block:: console
347 .. code-block:: console
381 .. code-block:: console
417 .. code-block:: console
446 Starting and stopping broadcast reception
449 .. code-block:: console
459    Starting broadcast reception on 1 connection(s)
460    Broadcast reception start completed
462    Stopping broadcast reception on 1 connection(s)
463    Broadcast reception stop completed
465 Distributing the broadcast code
468 .. code-block:: console
478    Starting broadcast reception on 1 connection(s)
479    Broadcast reception start completed
481    Distribute broadcast code completed