When testing in python, each identification request would take eight to nine seconds to get a response. Is this due to the Internet or the identification model processing itself would take that long? And is there any way to get a response faster? Thank you.

I am trying to build a system that has should be able to recognize all the speakers and the speeches each speaker has spoken.
I was trying to build the solution using “Speaker Recognition API”. I am passing the voice/audio stream to identification API and able to know who are the speakers there; but didn’t find a way to know who spoke what.
Is there any way to know who spoke what using “Speaker Recognition API” as it is required for my solution?
Reference to any other APIs Microsoft is building will be really helpful

Operation status api always return status failed and message Speaker Invalid, please give the solution to this problem. audio are recorded exactly same as specifies the document.

{"status":"failed","createdDateTime":"2018-05-25T09:07:19.4685571Z","lastActionDateTime":"2018-05-25T09:07:20.3782489Z","message":"SpeakerInvalid"}

It is not clear about how to apply speaker recognition API on Android. It would be better for providing Sample Android app.

Rather than offer the APIs at Microsoft, then send the user to GitHub, then hope the user can follow the various installation processes/steps, simply allow the user to download directly from Microsoft and include the newly generated key in the downloadable source code. This way, you control the entire process and don't have to worry about unzipping, npm installs, key issues etc.

Please add the italian language. Thanks for your support.

I know Denmark is a small country, but there are still a need for support in Danish

The "How To" aspect of Speaker Recognition API documentation is missing. The "How To" documentation for Face API is well documented in a step by step fashion. However its missing here for the Speaker Recognition API.
Second part of my question is - can I send the *.wav file directly to the endpoint URL when using the API or should it be converted to multipart-form data or application octet-stream data?

Is there any plans to later support more than 10 profiles in the requests to identify speaker voices?

I am curious as to the technical limitations of the identification service. Is there plans in the future to make this a reliable service to make voice signature profiles out of?

I wanna create a login functionality with speaker recognition for multiple user in single device. It's mean user can login every-where using web Portal like as face recognition(findSimilar(persistent id)).

Takes too long to recognize the speaker due to Azure service being on different coast. Is this still an issue? Or do we now have servers in more locations?

Microsoft Speaker Identification should handle, if the voice match is 100% or very close to 100%. This could happen if some one has the voice recordings of others and trying to authenticate or verify.

Hello, Is it possible to use the Speaker Recognition API to perform real time identification.I have been trying to get some help on this. But with not much success.

there are customers in Japan waiting for support of Japanese.

It would be helpful if you provide Sample to use Speaker Recognition API like how you provided for Face Verification /detection samples for android?

we are working on project but only it supports en-us.