<P>I'm trying to test this app:<A href="https://github.com/attdevsupport/codekit-java/blob/master/examples/speech/src/main/java/com/att/example/App.java" target="_blank" rel="nofollow noopener noreferrer">https://github.com/attdevsupport/codekit-java/blob/master/examples/speech/src/main/java/com/att/example/App.java</A></P><P>but not success.</P><P> </P><P>Is mising the libs com.att.api.</P><P>From where i can download this libs to be used over Java.</P><P> </P><P>I also try to follow the steps but i'm confused:</P><P><A href="https://developer.att.com/apis/speech/docs?_ga=1.119610891.243916741.1438363536" target="_blank" rel="nofollow noopener noreferrer">https://developer.att.com/apis/speech/docs?_ga=1.119610891.243916741.1438363536</A></P>
Finally I completed the first step, I can send wav file and get text, where is the documentation to use chunked, on live speech to text?, and also for text to speech?,i was looking for examples but i not found nothing.
In my first question i was using netbeans was not possible to create the .jar file, i did it manually, installing maven and the set as java 6 as principal JDK and then run manually the command for maven to create the .jar file.
Here is a snippet taken from the "AT&T¿ Speech SDK Developer Guide for Android" doc
/*The Speech API recognition service supports clients that use HTTP streaming when posting audio data to the service. In a streaming request, the service performs speech processing while receiving data from the client. By contrast, in a non-streaming request, the service waits until it receives all data before performing speech recognition.
A client signals a streaming request to the server through a standard HTTP 1.1 mechanism called chunked transfer encoding. Adding the Transfer-Encoding: chunked header marks a streaming request. When the streaming request is signaled by adding this header, the client segments the posted data into chunks; a chunk size of 512 bytes is good for speech recognition.
If the client does not include a Transfer-Encoding header, it must include a Content-Length header instead, which specifies the number of bytes being sent in the request.*/