add start_stage to run-satellite #10
Merged
Conversation
This file contains 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
This was referenced Mar 27, 2024
|
Looks good, thank you! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 an optional
start_stageparam torun-satellite.The main use is in a "push to talk" feature I am preparing that allows a satellite to be "activated" from the server side. In this case the server will send
run-satellitewithstart_stage = asrto indicate that it wants the satellite to start a pipeline going directly to ASR (skipping vad / wake word / etc). More details will be provided in the corresponding PR inhome-assistant/core.But there could be other uses.
run-satelliteindicates that the server is ready to run pipelines, it makes sense to be able to specify specific properties of these pipelines.The param is optional, if
Nonethe satellite chooses the starting stage, as it happens now.