>> The problem is the latency on receiving BLE packets. The timestamp the
> device sends and the "receiver's clock" (ALSA Seq) will very quickly
> get out-of-sync, causing this timestamp to be invalid.
As the protocol requires sender and receiver to both maintain "clocks" which
are synced (no doubt with some allowance for drift and jitter), then in this
example it appears it is the sender that needs fixing.
> Thus we need somehow to set the event timestamp to any arbitrary value.
Is this fixing the issue, or breaking the standard?