Away From UnityWebRequests
Published on 2020-10-07 00:00:00 +0000
When talking with a friend, the thought that endian type is causing my proble came up, however when I tested that fix it still did not work (~30min). Next I decided to try a Unity Store Asset I happened across (which was not easy to find) called Voice Recorder, but after 1hr 30min this didn’t solve my problem, and my friend managed to find an ancient (6 year old) wit.ai in Unity repository available here. After about three hours examining and updating the code, I was using this repository as a basis for my wit.ai successfully, as seen below.
From this working, I determined there were two possibilities for why mine didn’t work.
- UnityWebRequests was messing up the sent info for wav files
- File.ReadAllBytes method and binaryReader.ReadBytes methods had different results for wav files
Sometimes though the response would be null, which I began to look into. After an hour I seemed to fix the issue by using https instead of http. Next, since the method the repo used to “parse” the response would add significant overhead for the developer, I began to create a different parser. At first I tried using the built in JSON parser, but it was failing. After a few hours I was able to parse the intent successfully. Now I just need to parse the entities. The parsing took ~6 hours to figure out.