[inworld] Allow Async delivery of timestamps info#3625
Merged
markbackman merged 1 commit intopipecat-ai:mainfrom Feb 13, 2026
Merged
[inworld] Allow Async delivery of timestamps info#3625markbackman merged 1 commit intopipecat-ai:mainfrom
markbackman merged 1 commit intopipecat-ai:mainfrom
Conversation
Contributor
Author
|
cc @cshape |
ianbbqzy
force-pushed
the
ian/inworld-async-timestamp
branch
2 times, most recently
from
8df1e36 to
062ed11
Compare
Codecov Report❌ Patch coverage is
🚀 New features to boost your workflow:
|
ianbbqzy
force-pushed
the
ian/inworld-async-timestamp
branch
from
062ed11 to
3e6acd3
Compare
ianbbqzy
force-pushed
the
ian/inworld-async-timestamp
branch
5 times, most recently
from
301e6e4 to
d3e569e
Compare
ianbbqzy
changed the title
markbackman
reviewed
Feb 12, 2026
Contributor
markbackman
left a comment
markbackman
left a comment
There was a problem hiding this comment.
Generally looks good! Just a few findings.
Also, you'll need to rebase to get the latest changes (should only affect imports).
markbackman
reviewed
Feb 12, 2026
* speed up first audio chunk latency
ianbbqzy
force-pushed
the
ian/inworld-async-timestamp
branch
from
d3e569e to
94f01af
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Please describe the changes in your PR. If it is addressing an issue, please reference that as well.
There might be requirements to keep the timestamp info synced with the audio chunks. E.g. if a response chunk
{audio_bytes: asdflksdafja}has the audio for "Hello", then the same response must also have{audio_bytes: asdflksdafja, timestamp_info: {... "Hello" ...}}, such as in some latency sensitive lipsync use cases.But IIUC, Pipecat doesn't really care about this because the timestamps and audios are emitted to two independent channels anyway. If my understanding is incorrect, I will refactor the PR to allow SDK users to configure
SYNCvsASYNCin case some have this requirement for backward compatibilityOfficial docs for this mode will be up shortly.