You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The pipeline is already configured to work with Language models, and users won't have to change anything for that to work.
However, if they wanted to switch and work with Acoustic models, within the SpeechTestDataCI workflow, users must set the environment variable CUSTOM_SPEECH_MODEL_KIND to be Acoustic. We already describe to the user how to set this in Advanced customizations.
They also need to set the proper paths to their data.
Solution
We should note this earlier in the solution, probably step 3 when they're looking at their data for the first time. Plus this will not impact their initial baseline run. The first mention of language vs. acoustic models is in the intro to step 3, so here would be a good spot to go even further.
The text was updated successfully, but these errors were encountered:
In v3 of Custom Speech, models can be comprised of:
However, in v2 (current) they can only be:
The pipeline is already configured to work with Language models, and users won't have to change anything for that to work.
However, if they wanted to switch and work with Acoustic models, within the SpeechTestDataCI workflow, users must set the environment variable
CUSTOM_SPEECH_MODEL_KIND
to beAcoustic
. We already describe to the user how to set this in Advanced customizations.They also need to set the proper paths to their data.
Solution
We should note this earlier in the solution, probably step 3 when they're looking at their data for the first time. Plus this will not impact their initial baseline run. The first mention of language vs. acoustic models is in the intro to step 3, so here would be a good spot to go even further.
The text was updated successfully, but these errors were encountered: