Alpha Software Mobile Development Tools:   Alpha Anywhere    |   Alpha TransForm subscribe to our YouTube Channel  Follow Us on LinkedIn  Follow Us on Twitter  Follow Us on Facebook

Announcement

Collapse

The Alpha Software Forum Participation Guidelines

The Alpha Software Forum is a free forum created for Alpha Software Developer Community to ask for help, exchange ideas, and share solutions. Alpha Software strives to create an environment where all members of the community can feel safe to participate. In order to ensure the Alpha Software Forum is a place where all feel welcome, forum participants are expected to behave as follows:
  • Be professional in your conduct
  • Be kind to others
  • Be constructive when giving feedback
  • Be open to new ideas and suggestions
  • Stay on topic


Be sure all comments and threads you post are respectful. Posts that contain any of the following content will be considered a violation of your agreement as a member of the Alpha Software Forum Community and will be moderated:
  • Spam.
  • Vulgar language.
  • Quotes from private conversations without permission, including pricing and other sales related discussions.
  • Personal attacks, insults, or subtle put-downs.
  • Harassment, bullying, threatening, mocking, shaming, or deriding anyone.
  • Sexist, racist, homophobic, transphobic, ableist, or otherwise discriminatory jokes and language.
  • Sexually explicit or violent material, links, or language.
  • Pirated, hacked, or copyright-infringing material.
  • Encouraging of others to engage in the above behaviors.


If a thread or post is found to contain any of the content outlined above, a moderator may choose to take one of the following actions:
  • Remove the Post or Thread - the content is removed from the forum.
  • Place the User in Moderation - all posts and new threads must be approved by a moderator before they are posted.
  • Temporarily Ban the User - user is banned from forum for a period of time.
  • Permanently Ban the User - user is permanently banned from the forum.


Moderators may also rename posts and threads if they are too generic or do not property reflect the content.

Moderators may move threads if they have been posted in the incorrect forum.

Threads/Posts questioning specific moderator decisions or actions (such as "why was a user banned?") are not allowed and will be removed.

The owners of Alpha Software Corporation (Forum Owner) reserve the right to remove, edit, move, or close any thread for any reason; or ban any forum member without notice, reason, or explanation.

Community members are encouraged to click the "Report Post" icon in the lower left of a given post if they feel the post is in violation of the rules. This will alert the Moderators to take a look.

Alpha Software Corporation may amend the guidelines from time to time and may also vary the procedures it sets out where appropriate in a particular case. Your agreement to comply with the guidelines will be deemed agreement to any changes to it.



Bonus TIPS for Successful Posting

Try a Search First
It is highly recommended that a Search be done on your topic before posting, as many questions have been answered in prior posts. As with any search engine, the shorter the search term, the more "hits" will be returned, but the more specific the search term is, the greater the relevance of those "hits". Searching for "table" might well return every message on the board while "tablesum" would greatly restrict the number of messages returned.

When you do post
First, make sure you are posting your question in the correct forum. For example, if you post an issue regarding Desktop applications on the Mobile & Browser Applications board , not only will your question not be seen by the appropriate audience, it may also be removed or relocated.

The more detail you provide about your problem or question, the more likely someone is to understand your request and be able to help. A sample database with a minimum of records (and its support files, zipped together) will make it much easier to diagnose issues with your application. Screen shots of error messages are especially helpful.

When explaining how to reproduce your problem, please be as detailed as possible. Describe every step, click-by-click and keypress-by-keypress. Otherwise when others try to duplicate your problem, they may do something slightly different and end up with different results.

A note about attachments
You may only attach one file to each message. Attachment file size is limited to 2MB. If you need to include several files, you may do so by zipping them into a single archive.

If you forgot to attach your files to your post, please do NOT create a new thread. Instead, reply to your original message and attach the file there.

When attaching screen shots, it is best to attach an image file (.BMP, .JPG, .GIF, .PNG, etc.) or a zip file of several images, as opposed to a Word document containing the screen shots. Because Word documents are prone to viruses, many message board users will not open your Word file, therefore limiting their ability to help you.

Similarly, if you are uploading a zipped archive, you should simply create a .ZIP file and not a self-extracting .EXE as many users will not run your EXE file.
See more
See less

curl Genie Issues

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • curl Genie Issues

    Hello,

    I have been working to connect to the AT&T API's and have been successful in using the curl genie to request/receive the OAuth Token, but I have two issues as I attempt to access the API and upload the .wav file for processing. First, the curl genie dialog window opens for a very brief time and while I can see there are exceptions, it then disappears before I can capture what the text is. Is there an option to freeze that window or capture the dialog in a different way?

    Secondly, the curl statement I'm trying to translate is formatted in the same order as the example on the AT&T developer website and is as follows:

    curl --insecure https://api.att.com/speech/v3/speechToText --header “Authorization: bearer xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" --data-binary @”C:\Users\JK\Documents\Test1_2015-11-18.wav” --header “Content-Type: audio/wav” --header “Accept: application/json”

    I receive a number of aberrant outcomes from the curl genie as soon as I add the --data-binary @ file name. These include the message "Curl call did not produce output" to disfunctional Xbasic output where the only reference to the .wav file is: dim posted_fields as c = ("RIFF\00") and no file name anywhere in the Xbasic output. I did confirm that this is a correct statement in the libCURL library which the Release Notes indicate is used by the curl genie.

    The ce.setOpt("HTTPHEADER",slist1) is correct with the order above and just to be sure there isn't an order dependency in the curl statement I have rearranged the order to group all of the --header statements together and the posted_fields statement remains as previously stated.

    As background, I'm running V12.3 Build 2999 with System Addins Build 4519. Any thoughts? Your comments are appreciated and if the genie isn't capable of working with a binary file, suggestions on any other approaches (http_post ?) would be of value.

    Thanks,
    Joe

  • #2
    Re: curl Genie Issues

    See if this gets you closer. Part of the problem is that your cURL request is badly formatted - maybe you didn't paste it into this message. Your https stuff is unquoted and you've got mixed quotes in the balance of the statement.

    Code:
    curl --insecure "https://api.att.com/speech/v3/speechToText" --header "Authorization: bearer xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" --data-binary @"C:\Users\JK\Documents\Test1_2015-11-18.wav" --header "Content-Type: audio/wav" --header "Accept: application/json"

    Comment


    • #3
      Re: curl Genie Issues

      Originally posted by Davidk View Post
      See if this gets you closer. Part of the problem is that your cURL request is badly formatted - maybe you didn't paste it into this message. Your https stuff is unquoted and you've got mixed quotes in the balance of the statement.

      Code:
      curl --insecure "https://api.att.com/speech/v3/speechToText" --header "Authorization: bearer xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" --data-binary @"C:\Users\JK\Documents\Test1_2015-11-18.wav" --header "Content-Type: audio/wav" --header "Accept: application/json"

      Comment


      • #4
        Re: curl Genie Issues

        Hi David,

        Thanks for the reply and catching an annoying error. I lost the quotes on the URL in Word when it converted the string to a hyperlink & didn't catch it when I pasted it into my original post. I think the same happened on the mixed quotes so now I'm using a simple text editor that won't "fix" my typing. However I did take your string as structured (with a new OAuth token) and received a ""{audioBytes":0,"audioTime":0}}" response from the AT&t server. Unfortunately, the dim posted_fields as c = ("RIFF\00") statement in the Xbasic remains and the response from the server indicates that there isn't data being passed, so the question on how to reference and upload the .wav file in the Xbasic routine remains. It appears that the --data-binary @"C:\xxxxx" isn't being parsed (or passed) as the documentation suggests. Am I missing something simple in how the file name is defined, either in the curl statement or in the Xbasic script?

        Thanks,
        Joe

        Comment


        • #5
          Re: curl Genie Issues

          Joe, I did a quick search about the "riff" message you're getting. Is it possible the .wav file is not encoded properly for at&t speech to text? This is the line of code I'm getting when I use a .wav file I have.

          Code:
          dim posted_fields as c = ("RIFF.r")
          As you've found, the actual file name doesn't make it through the genie. I'm out of my depth at this point. It's really interesting stuff... I hope someone can jump in and help out. Seems close.

          Comment


          • #6
            Re: curl Genie Issues

            Hi David,

            Again, I appreciate your help. I have analyzed the .wav file I'm using and it nominally meets all of the parameters AT&T mandates. It's puzzling to say the least and I also hope someone with a deeper insight into the curl genie can offer some guidance.

            Regards,
            Joe

            Comment


            • #7
              Re: curl Genie Issues

              I feel it may be a tall order... but any help from AT&T?

              Comment


              • #8
                Re: curl Genie Issues

                I'm reluctant to approach them until I have some level of confidence that I'm even attaching the data file to the request stream. The Xbasic code stream declares posted_fields as c and when I checked the contents, in fact it is text with length of 7 - i.e. "RIFF/00"

                Comment

                Working...
                X