Hello,
One customer is using Azure speech to text SDK 1.12.1. They complained that noise or silence are mis-recognized as "S", which as a result trigger the downstream component like NLU to act unexpectedly.
Below is NBest:
{
"DisplayText":"S",
"Duration":20900000,
"Id":"718b20d216f542d6beee087ba793b752",
"NBest":[
{
"Confidence":0.11938265,
"Display":"S",
"ITN":"s",
"Lexical":"s",
"MaskedITN":""
},
{
"Confidence":0.118968755,
"Display":"M",
"ITN":"m",
"Lexical":"m",
"MaskedITN":""
},
{
"Confidence":0.11897701,
"Display":"H",
"ITN":"h",
"Lexical":"h",
"MaskedITN":""
},
{
"Confidence":0.1189549,
"Display":"L",
"ITN":"l",
"Lexical":"l",
"MaskedITN":""
},
{
"Confidence":0.11928433,
"Display":"At",
"ITN":"at",
"Lexical":"at",
"MaskedITN":""
}
],
"Offset":4400000,
"RecognitionStatus":"Success"
}
Since these NBest candidates confidence score is low as 0.11, is there any suggested confidence threadhold for customer to ignore low confidence result? like 0.2 ?
Thank you.