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
when you register on their website and follow the prompts, a page appears at one point wherethe apikey is listed
I see, but explain, what's the use of the free 10,000 voiced characters per month if every user is going to spend them on the same key crammed into the advisor? They will be gone in the blink of an eye and the limit will be reached.
i.e. I now understand that in the retrievable stream
00000089 is service information, but I don't understand how to make it ignore
it's 0x89 bytes after the string - binary data. Then either another part (again string length, data) or end...
is 0x89 bytes after the string - binary data. Then either another part (again, string length, data) or the end...
Yes, yes I understand, thank you! )
How to ask the server not to specify block sizes, that's what I'm googling now
Use a standard plan that can pay off. $0.02 per 1,000 characters.
In this case, you don't need to look for hacks. Contact their support team and explain the situation. If the MT (webrequest) platform is supportive and they help - it might work out.
Yes, yes I understand, thank you! )
How to ask the server not to specify block sizes, that's what I'm googling now
When you save it to a file, you have to parse the content yourself. Focusing on the headers (oh those headers) sent by the server. It also tells you what kind of data it sends and how it slices/forms it.
WebRequest is pretty low-level stuff and you have to do a lot by yourself. The same curl, when saving file, parses content sent from server, but we don't have such glamour :-)
When saving to a file, you have to parse the content yourself. It should be guided by the headers (oh, the headers) sent by the server. It also tells you what kind of data it sends and how it slices/forms it.
WebRequest is pretty low-level stuff and you have to do a lot by yourself. Same curl, when saving file, parses content sent from server, but we don't have such glamour :-)
There 's a mention of something similarhere.
I am also thinking in this direction. The TTS service was not invented for short phrases, but for a continuous stream. Waiting until a big file is formed, downloading it, so much time passes and they are thrown in the direction of the client in pieces of data.
Use a standard plan that can pay off. $0.02 per 1,000 characters.
In this case, you don't need to look for hacks. Contact their support team and explain the situation. If the MT (webrequest) platform is supportive and they help - it might work out.
For free their support will not talk, here you're right! :)
Their support won't talk for free, you're right! :)
Of course) It's their business. Imagine that you have created a text-to-audio stream converter. They can't just say "screw you" - that's rude, but they want to make some hard-disguised restrictions, so you have to suffer and try to get free money from "suckers" and then just give up or pay - you're welcome)))
These guys aren't stupid!)))
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. We will most likely add it as a standard functionality both in the terminal and in MQL5.