This repository has been archived by the owner on Nov 16, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 13
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Update sample code for version 1.7.0 release (#30)
- Loading branch information
Showing
5 changed files
with
68 additions
and
9 deletions.
There are no files selected for viewing
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
33 changes: 32 additions & 1 deletion
33
Samples/Android/Speech Devices SDK Starter App/example/participants.properties
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1 +1,32 @@ | ||
PARTICIPANTSLIST= | ||
# This file should contain voice signatures of participants in conversation. | ||
# | ||
# Format of the file is: | ||
# PARTICIPANTSLIST = <user1@voice_signature1><user2@voice_signature2><user3@voice_signature3>... | ||
# | ||
# You can create voice signatures of users by following instructions provided on | ||
# https://docs.microsoft.com/en-us/azure/cognitive-services/speech-service/how-to-use-conversation-transcription-service#create-voice-signatures-for-participants | ||
# | ||
# A voice signature has following format: | ||
# { "Version": <Numeric value>, "Tag": "string", "Data": "string" } | ||
# | ||
# So, your participants.properties file would look like following: | ||
# PARTICIPANTSLIST = <user1@\ | ||
# {\ | ||
# "Version": numeric_value,\ | ||
# "Tag": "string",\ | ||
# "Data": "string"\ | ||
# }>\ | ||
# <user2@\ | ||
# {\ | ||
# "Version": numeric_value,\ | ||
# "Tag": "string",\ | ||
# "Data": "string"\ | ||
# }>\ | ||
# <user3@\ | ||
# {\ | ||
# "Version": numeric_value,\ | ||
# "Tag": "string",\ | ||
# "Data": "string"\ | ||
# }> | ||
|
||
PARTICIPANTSLIST = |
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,2 +1,32 @@ | ||
PARTICIPANTSLIST= | ||
|
||
# This file should contain voice signatures of participants in conversation. | ||
# | ||
# Format of the file is: | ||
# PARTICIPANTSLIST = <user1@voice_signature1><user2@voice_signature2><user3@voice_signature3>... | ||
# | ||
# You can create voice signatures of users by following instructions provided on | ||
# https://docs.microsoft.com/en-us/azure/cognitive-services/speech-service/how-to-use-conversation-transcription-service#create-voice-signatures-for-participants | ||
# | ||
# A voice signature has following format: | ||
# { "Version": <Numeric value>, "Tag": "string", "Data": "string" } | ||
# | ||
# So, your participants.properties file would look like following: | ||
# PARTICIPANTSLIST = <user1@\ | ||
# {\ | ||
# "Version": numeric_value,\ | ||
# "Tag": "string",\ | ||
# "Data": "string"\ | ||
# }>\ | ||
# <user2@\ | ||
# {\ | ||
# "Version": numeric_value,\ | ||
# "Tag": "string",\ | ||
# "Data": "string"\ | ||
# }>\ | ||
# <user3@\ | ||
# {\ | ||
# "Version": numeric_value,\ | ||
# "Tag": "string",\ | ||
# "Data": "string"\ | ||
# }> | ||
|
||
PARTICIPANTSLIST = |
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 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