Open
Conversation
3DRX
force-pushed
the
feat/spatialreal_avatar
branch
2 times, most recently
from
3a11a12 to
9136884
Compare
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
livekit-plugins/livekit-plugins-spatialreal/livekit/plugins/spatialreal/avatar.py
Show resolved
Hide resolved
livekit-plugins/livekit-plugins-spatialreal/livekit/plugins/spatialreal/avatar.py
Show resolved
Hide resolved
3DRX
force-pushed
the
feat/spatialreal_avatar
branch
from
9136884 to
15b4cec
Compare
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
3DRX
force-pushed
the
feat/spatialreal_avatar
branch
from
15b4cec to
840bac3
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.
This PR adds SpatialReal avatar plugin, we've been developing it for a while at https://github.com/spatialwalk/livekit-plugins-spatialreal, and publish packages to https://pypi.org/project/livekit-plugins-spatialreal.
Our example project can be found at https://github.com/spatialwalk/avatarkit-voice-agent-demo/tree/main/livekit-agents. For a deployed demo, please checkout SpatialReal playground, which is built using livekit agents and SpatialReal avatar using this plugin.
This plugin have https://pypi.org/project/avatarkit/ as dependency, which is our python SDK, it's a thin layer that handles websocket connection and protobuf messages.
During this PR I also make changes according to the ai review, I personally tested these changes from the example project with no regressions found.
Another thing I'd like to discuss is pypi package transfer, I think it is good for developers (less confusion) if we can still publish release to the same pypi package afther this plugin gets merged, and we are willing to transfer the ownership of the pypi package to livekit organization. Please let me know what should I do :)
We have early adopters shipping SpatialReal avatar in production using other integration methods for months, and recently we have developers using this plugin in their product for about a week, during the process we've fixed all known issues.