Lag playback by a few frames, and send the first frames as a burst when
starting. The hope here is to trade playback latency for less stuttering
when transmission is delayed due to reason or another.

Read controller timing from kernel using an ioctl, and use that
information to rate match to keep the latency between us sending an SDU
to the socket, and controller completing it constant.

Provide our own BAP ISO packet sequence numbering to the kernel for it
to use.

Add basics for rate matching.

P V authored 2 years ago and P V committed 2 years ago

We need to acquire and release all transports in the same CIG at the
same time.

Due to current kernel ISO socket limitations, this cannot be done one by
one.

P V authored 2 years ago and P V committed 2 years ago

Now that sinks/sources can do transport acquire asynchronously, remove
the workaround that made it synchronous.  Do release still synchronously
however.

P V authored 2 years ago and P V committed 2 years ago

Sinks/sources now expect transport state is set on acquire+release.
It doesn't need to be done async, so do it still synchronously.

P V authored 2 years ago and P V committed 2 years ago

The sinks/sources now expect transport state is set in acquire and
release.  It does not need to be async, so we still do it synchronously.

P V authored 2 years ago and P V committed 2 years ago

Change A2DP/BAP transport acquire and release to be async.

Since BlueZ acquiring ISO sockets blocks until all sockets in same CIG
are acquired, BAP transports must be acquired asynchronously.

P V authored 2 years ago and P V committed 2 years ago

Allow asynchronous changes in transport state in the sinks/sources.

Also allow transport acquire to be actually synchronous, in this case it
must set transport state during acquire call.

Separate driver start/stop from transport start/stop.

Check if we already are connected and return -EBUSY to avoid
crashing.

Fixes #3091

Add option bluez5.roles that selects which endpoints (A2DP, BAP, HFP,
HSP) will be enabled.

This extends and deprecates bluez5.headset-roles.

Emit any remove node events before resetting initial profile.  It
indicates to the session manager that nodes if any went away before
device disconnected.

Usually the profile is removed first which removes the nodes. This
depends on ordering of events from bluez, which apparently can be
different depending on how remote device disconnects.

Add the current fill level to the last known latency measurement right
before de do the rate matching. This improves accuracy of the matching.

The capture delay calculation had the wrong sign, making the resampler
go in the wrong direction and causing pitch changes.

Fixes #3093