BuildSpeaker
Trains Media Server to recognize a speaker.
You can only run this action after creating a speaker (using the action NewSpeaker) and adding audio samples for training (using the action AddSpeakerAudio).
Type: asynchronous
Parameter | Description | Required |
---|---|---|
database
|
The name of the database that contains the speaker. | Yes |
identifier
|
The identifier of the speaker that you want to train Media Server to recognize. | Yes |
numparallel
|
The maximum number of threads to use to complete the training (default 1), subject to the limit specified by MaxNumParallel. |
No |
Example
/action=BuildSpeaker&database=news&identifier=newsreader1
Response
This action is asynchronous, so Media Server always returns success accompanied by a token. You can use this token with the QueueInfo action to retrieve the status of your request.
The following is an example response from the QueueInfo action. Each audio
element describes an individual audio clip.
<autnresponse> <action>QUEUEINFO</action> <response>SUCCESS</response> <responsedata> <actions> <action> <status>Finished</status> <queued_time>2021-Feb-09 12:38:34</queued_time> <time_in_queue>0</time_in_queue> <process_start_time>2021-Feb-09 12:38:34</process_start_time> <time_processing>34</time_processing> <process_end_time>2021-Feb-09 12:39:08</process_end_time> <build> <audio> <index>1</index> <label>afb0009fcc61e3c1be8a100431a896b5</label> <status>trained</status> </audio> </build> <database>news</database> <identifier>newsreader1</identifier> <numaudio>1</numaudio> <numtrained>1</numtrained> <token>...</token> </action> </actions> </responsedata> </autnresponse>