You are missing trading opportunities:
- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
Registration
Log in
You agree to website policy and terms of use
If you do not have an account, please register
Found out why chunked responses from the IBM service are not accepted:
They had incorrect formatting in the Transfer-Encoding response header, where they put a double space instead of a single space. The protocol allows this, but our parser didn't take it into account.
That's why we misread the chunked/sliced stream and couldn't wait for it to finish.
There will be a fix in the next beta. Most likely today.
We launched an embedded Text2Speech service back in the MetaQuotes platform around 2002, but it was kicked out due to poor implementation. Most likely, it will be added to the terminal and MQL5 as a standard functionality.
This is the manly way!
I was too excited about cocoa :)
that's manly!
I got a little excited about cocoa :)
But, for you, the problem will remain up to the standard TEXT TO SPEECH integration. Either 10,000 characters for ALL users of your EA, or a paid plan from IBM for $0.02/1000 words. What to do with the article then? What will you do, if it's not a secret?
Here's a working script:
Here's a working script:
the script loads some file result.ogg.
only it is not clear, what is this file ? how to listen to it ?
I tried it in a different format.
the script loads some file result.ogg.
only it's not clear, what is this file ? how can i listen to it ?
I tried it in a different format.
and here I am a plain text of two English words (Traders Forum.txt)
I understand that it is possible to send (file.txt) and receive it in ( file.wav) format
------------------------------------------
here is the script WebRequest.mq5 inWebRequest.wav
I understand that you could somehow arrange to send (file.txt) and receive it in ( file.wav) format
At the moment, this is not very cost-effective. That is, IBM's service sends files that are not yet readable by WebRequest (should be fixed soon), but even when they are, free use of theText to Speech serviceis limited to 10,000 characters per month. That is, they'll convert a small paragraph and that's it. There is a paid option (this is for those who really need it). Perhaps if you find a free text dubbing service without restrictions, you can try to make up all over again. But I don't think there are any...
We are reassured by introduction ofText to Speech in terminal and language, which would be certainly gorgeous for AI developers, but, it will take time. Imho, it's better to wait now...
the script loads some result.ogg file.
Beta 2472 is already available and it works with the IBM service.
This service does not output files in wav, but in ogg format.
Here's a working script:
Yes! )