Big accuracy problems with various files format #12
Description
I have tested the Emotion Recognition API with 10 different samples for all the 7 emotions. Out of 70 tests, none of them failed. It was 100% accurate. But this was because I used a particular type of .wav files (find them here: https://tspace.library.utoronto.ca/handle/1807/24487 ). When I use mp3 files or other files expressing exactly the same emotion, the API fails. It identifies a wrong emotion.
I also tried to provide base64 encoded data. The same happened: for this sort of files, it works perfectly, for others it just fails. With curl request, the same happens. A big difference between encoded .wav files and encoded .mp3 or other formats or even .wav files with different properties. And this is even more annoying.
For example, in the MP3 file here, taken directly from your website, the API will not identify fear(as it should and you state it should), but it identifies happiness with a score of 0.6907534228467851:
https://drive.google.com/file/d/1HKkGCzci5GE6ObC8Frm-hMacTINcE9yd/view?usp=sharing
However, for exactly the same content, but in .wav format, it identifies fear correctly with a score of 0.9999930278037144.
https://drive.google.com/file/d/1pc8ekCX_--m5c-e7amxwEz-CCuKJuggy/view?usp=sharing
Please, tell me what are the required properties for the files provided as parameters. I was testing it with files of different sample rate, bit rate, file type, bits per sample, encoding, etc. It just fails.
Activity
[-]Big accuracy problems with various files[/-][+]Big accuracy problems with various files format[/+]royaljain commentedon Aug 30, 2018
Hi Emanuela,
Thanks for your patience. I'll look at the cause of this issue and update you. I have requested access for the google drive links you have shared, can you approve them ?
coltaemanuela commentedon Aug 30, 2018
IshanFx commentedon Jun 3, 2019
@coltaemanuela Is it return score? I tried with node library and it doesn't return any score for emotion Recognition API.