mirrors/pipewire
1
0
Fork 0
mirror of https://gitlab.freedesktop.org/pipewire/pipewire.git synced 2025-10-31 22:25:38 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions
pipewire/spa/plugins/bluez5/iso-io.h

56 lines
2 KiB
C
Raw Normal View History

bluez5: add spa_bt_iso_io that does the low-level part for ISO Add factored out helper for ISO socket I/O. ISO sockets need synchronization of writes and audio position for different stream fds in the same isochronous group, and it's easier to separate out the part that coordinates it.
2023-03-25 16:58:27 +02:00
/* Spa Bluez5 ISO I/O */
/* SPDX-FileCopyrightText: Copyright © 2023 Pauli Virtanen */
/* SPDX-License-Identifier: MIT */
#ifndef SPA_BLUEZ5_ISO_IO_H
#define SPA_BLUEZ5_ISO_IO_H
#include <spa/utils/defs.h>
#include <spa/support/loop.h>
#include <spa/support/log.h>
#include <spa/node/io.h>
bluez5: output silence if no data for some ISO sinks When a sink contributing to an ISO CIG does not have data, output silence for it, as long as at least one sink in the CIG is running. Only if writes to sockets fail, pause all streams to reset synchronization. This way we write exactly the same number of packets for each CIS at the same time, which probably is the best tested configuration in BT adapters and devices. We also don't then have to pause output if some sinks are not running or miss their timing, as we generate silence on the fly. When using iso-io, have it initialize the codec instance, and have media-sink uses that instance, so that silence and actual audio are encoded with the same codec.
2023-04-09 21:28:40 +03:00
#include <spa/param/audio/format.h>
bluez5: ensure capture target latency is uniform for an ISO group All BAP client sources in the ISO group should use same target latency, so that capture streams stay in sync.
2025-07-12 13:40:54 +03:00
struct spa_bt_decode_buffer;
bluez5: output silence if no data for some ISO sinks When a sink contributing to an ISO CIG does not have data, output silence for it, as long as at least one sink in the CIG is running. Only if writes to sockets fail, pause all streams to reset synchronization. This way we write exactly the same number of packets for each CIS at the same time, which probably is the best tested configuration in BT adapters and devices. We also don't then have to pause output if some sinks are not running or miss their timing, as we generate silence on the fly. When using iso-io, have it initialize the codec instance, and have media-sink uses that instance, so that silence and actual audio are encoded with the same codec.
2023-04-09 21:28:40 +03:00
struct spa_bt_transport;
bluez5: add spa_bt_iso_io that does the low-level part for ISO Add factored out helper for ISO socket I/O. ISO sockets need synchronization of writes and audio position for different stream fds in the same isochronous group, and it's easier to separate out the part that coordinates it.
2023-03-25 16:58:27 +02:00
/**
* ISO I/O.
*
* Synchronizes related writes from different streams in the same group
* to occur at same real time instant (or not at all).
*/
struct spa_bt_iso_io
{
bluez5: media-sink: resync ISO streams on playback start Resynchronize ISO streams on playback (re)start, so the stream positions are aligned immediately. This is better than relying on rate matching to correct any offsets.
2023-04-09 19:53:42 +03:00
uint64_t now; /**< Reference time position of next packet (read-only) */
uint64_t duration; /**< ISO interval duration in ns (read-only) */
bool resync; /**< Resync position for next packet; (pull callback sets to
* false when done) */
uint32_t timestamp; /**< Packet timestamp (set by pull callback) */
uint8_t buf[4096]; /**< Packet data (set by pull callback) */
size_t size; /**< Packet size (set by pull callback) */
bluez5: output silence if no data for some ISO sinks When a sink contributing to an ISO CIG does not have data, output silence for it, as long as at least one sink in the CIG is running. Only if writes to sockets fail, pause all streams to reset synchronization. This way we write exactly the same number of packets for each CIS at the same time, which probably is the best tested configuration in BT adapters and devices. We also don't then have to pause output if some sinks are not running or miss their timing, as we generate silence on the fly. When using iso-io, have it initialize the codec instance, and have media-sink uses that instance, so that silence and actual audio are encoded with the same codec.
2023-04-09 21:28:40 +03:00
bool need_resync; /**< Resync requested (set by pull callback) */
struct spa_audio_info format; /**< Audio format */
void *codec_data; /**< Codec data */
bluez5: add spa_bt_iso_io that does the low-level part for ISO Add factored out helper for ISO socket I/O. ISO sockets need synchronization of writes and audio position for different stream fds in the same isochronous group, and it's easier to separate out the part that coordinates it.
2023-03-25 16:58:27 +02:00
void *user_data;
};
typedef void (*spa_bt_iso_io_pull_t)(struct spa_bt_iso_io *io);
bluez5: output silence if no data for some ISO sinks When a sink contributing to an ISO CIG does not have data, output silence for it, as long as at least one sink in the CIG is running. Only if writes to sockets fail, pause all streams to reset synchronization. This way we write exactly the same number of packets for each CIS at the same time, which probably is the best tested configuration in BT adapters and devices. We also don't then have to pause output if some sinks are not running or miss their timing, as we generate silence on the fly. When using iso-io, have it initialize the codec instance, and have media-sink uses that instance, so that silence and actual audio are encoded with the same codec.
2023-04-09 21:28:40 +03:00
struct spa_bt_iso_io *spa_bt_iso_io_create(struct spa_bt_transport *t,
bluez5: iso-io: get BAP interval from dbus, not getsockopt For ISO server sockets, the QOS struct from getsockopt contains values with different meaning from ISO client socket. Get the values via DBus instead, which is right in both cases.
2023-04-06 23:02:44 +03:00
struct spa_log *log, struct spa_loop *data_loop, struct spa_system *data_system);
bluez5: output silence if no data for some ISO sinks When a sink contributing to an ISO CIG does not have data, output silence for it, as long as at least one sink in the CIG is running. Only if writes to sockets fail, pause all streams to reset synchronization. This way we write exactly the same number of packets for each CIS at the same time, which probably is the best tested configuration in BT adapters and devices. We also don't then have to pause output if some sinks are not running or miss their timing, as we generate silence on the fly. When using iso-io, have it initialize the codec instance, and have media-sink uses that instance, so that silence and actual audio are encoded with the same codec.
2023-04-09 21:28:40 +03:00
struct spa_bt_iso_io *spa_bt_iso_io_attach(struct spa_bt_iso_io *io, struct spa_bt_transport *t);
bluez5: add spa_bt_iso_io that does the low-level part for ISO Add factored out helper for ISO socket I/O. ISO sockets need synchronization of writes and audio position for different stream fds in the same isochronous group, and it's easier to separate out the part that coordinates it.
2023-03-25 16:58:27 +02:00
void spa_bt_iso_io_destroy(struct spa_bt_iso_io *io);
void spa_bt_iso_io_set_cb(struct spa_bt_iso_io *io, spa_bt_iso_io_pull_t pull, void *user_data);
bluez5: iso-io: track and apply corrections to tx latency Use TX timestamps to get accurate reading of queue length and latency on kernel + controller side. This is new kernel BT feature, so requires kernel with the necessary patches, available currently only in bluetooth-next/master branch. Enabling Poll Errqueue kernel experimental Bluetooth feature is also required for this. Use the latency information to mitigate controller issues where ISO streams are desynchronized due to tx problems or spontaneously when some packets that should have been sent are left sitting in the queue, and transmission is off by a multiple of the ISO interval. This state is visible in the latency information, so if we see streams in a group have persistently different latencies, drop packets to resynchronize them. Also make corrections if the kernel/controller queues get too long, so that we don't have too big latency there. Since BlueZ watches the same socket for errors, and TX timestamps arrive via the socket error queue, we need to set BT_POLL_ERRQUEUE in addition to SO_TIMESTAMPING so that BlueZ doesn't think TX timestamps are errors. Link: https://github.com/bluez/bluez/issues/515 Link: https://lore.kernel.org/linux-bluetooth/cover.1710440392.git.pav@iki.fi/ Link: https://lore.kernel.org/linux-bluetooth/f57e065bb571d633f811610d273711c7047af335.1712499936.git.pav@iki.fi/
2024-02-20 23:01:07 +02:00
int spa_bt_iso_io_recv_errqueue(struct spa_bt_iso_io *io);
bluez5: add spa_bt_iso_io that does the low-level part for ISO Add factored out helper for ISO socket I/O. ISO sockets need synchronization of writes and audio position for different stream fds in the same isochronous group, and it's easier to separate out the part that coordinates it.
2023-03-25 16:58:27 +02:00
bluez5: ensure capture target latency is uniform for an ISO group All BAP client sources in the ISO group should use same target latency, so that capture streams stay in sync.
2025-07-12 13:40:54 +03:00
void spa_bt_iso_io_set_source_buffer(struct spa_bt_iso_io *io, struct spa_bt_decode_buffer *buffer);
bluez5: iso-io: sync to ISO RX clock, align stream RX in group Align RX of streams in same ISO group: - Ensure all streams in ISO group have same target latency also for BAP Client - Determine rate matching to ISO group clock from RX times of all streams in the group - Based on this, compute nominal packet RX times, and feed them to decode-buffer instead of the real RX time. This is enough for sub-sample level sync. - Customise buffer overrun handling for ISO so that it drops data to arrive exactly at the target, for faster convergence at RX start The ISO clock matching is done based on kernel-provided packet RX times, so it has unknown offset from the actual ISO clock, probably a few ms. Current kernels (6.17) do not provide anything better to use for the clock matching, and doing it properly appears to be controller vendor-defined (if possible at all).
2025-09-07 17:04:08 +03:00
int32_t spa_bt_iso_io_get_source_target_latency(struct spa_bt_iso_io *io);
void spa_bt_iso_io_check_rx_sync(struct spa_bt_iso_io *io, uint64_t position);
int64_t spa_bt_iso_io_recv(struct spa_bt_iso_io *io, int64_t now);
bluez5: ensure capture target latency is uniform for an ISO group All BAP client sources in the ISO group should use same target latency, so that capture streams stay in sync.
2025-07-12 13:40:54 +03:00
bluez5: add spa_bt_iso_io that does the low-level part for ISO Add factored out helper for ISO socket I/O. ISO sockets need synchronization of writes and audio position for different stream fds in the same isochronous group, and it's easier to separate out the part that coordinates it.
2023-03-25 16:58:27 +02:00
#endif
Reference in a new issue Copy permalink