07.10.2012 05:20 PM
08.17.2012 02:43 PM
Thanks so much for the guide, it was a huge help! I was able to get the sample app working on my iphone. One thing I note right off the bat, the response time of ATT is much slower than that of Nuance. (2-3 seconds versus 1 second)
Small changes in your guide to get it to work:
In step 3, the application name must be SimpleSpeech, or else rename the sample project to match the name that you onboard.
Down near the bottom of the document,
#define API_KEY @"0x1234"
#define SECRET @"0x567"
#define API_KEY @"1234"
#define API_ SECRET @"567"
(SECRET needs the API_ prefix, and the 0x hex prefix shouldn't be left there when inserting key)
08.17.2012 07:42 PM
Thank you for your corrections! I updated http://brss.us/attSpeechApi and will try them on my sample app in a few days when I reconfigure this darn iPhone which has been rereconfigured so many times, I'm not surprised that the Provisioning Profile is not quite right...
Indeed it seems to be very slow compared to Nuance Dragon SDK. I haven't tried Nuance's new Nina SDK, have you? Do you know anyone who has? AT&T's advantage to us is the ability to save the audio data separately. Our app needs this ability, and Nuance's SDK makes this extremely difficult.
I'm glad you like the Quick Start doc. I'll keep it up there until they create one, or we stop using AT&T - whichever is first.
01.03.2013 10:49 AM
I'm having a problem in iOS 4.3 that does not exist in other versions of the OS. It happens in SimpleSpeech so it's not necessarily related to my own code.
After attempting to login to the API via the SDK (i.e. in "prepareSpeech" in the example), the following message fires:
- (void)speechService:(ATTSpeechService *)speechService failedWithError:(NSError *)error;
And error is NIL, so I cannot tell what the problem is.
Has anyone else encountered this?
- of 1