Get short, timely messages from Acapela Mobile TTS.

Twitter is a rich source of instantly updated information. It's easy to stay updated on an incredibly wide variety of topics. Join today and follow @Acapela_iPhone.

Get updates via SMS by texting follow Acapela_iPhone to 40404 in the United States
Codes for other countries

Two-way (sending and receiving) short codes:
Country Code For customers of
Australia
  • 0198089488 Telstra
Canada
  • 21212 (any)
United Kingdom
  • 86444 Vodafone, Orange, 3, O2
Indonesia
  • 89887 AXIS, 3, Telkomsel
Ireland
  • 51210 O2
India
  • 53000 Bharti Airtel, Videocon
Jordan
  • 90903 Zain
New Zealand
  • 8987 Vodafone, Telecom NZ
United States
  • 40404 (any)

Acapela_iPhone

  1. @BayanAlArifi could you tell me what you get + name of company by mail contact at Acapela-for-iPhone.com I will check.
  2. facebook.com/acapelagroup ... new Acapela Group Facebook Page #tts
  3. @pepF thanks, link shared on our new facebook page facebook.com/acapelagroup
  4. Saul will be available into the next version of iOS SDK RT @pepF: #AcapelaBox makes a great #rapmachine #TTS - blog.pepf.nl/2012/04/acapel…
  5. Saul is indeed really cool for slaming RT @pepF: @Acapela_iPhone #AcapelaBox makes a great #rapmachine #TTS - blog.pepf.nl/2012/04/acapel…
  6. @remaerd Hi... What's his name? Have you try the contact form on our website (the faster way to be connected to the defined sales manager)
  7. @drewux fyi 1.300 will be natively done and tested for iOS 5.1 SDK. Release in +/- 2 months max
  8. New post iOS: Acapela for iPhone and ARC: Hello As you know, Acapela for iPhone 1.201 is fully compatible with i... bit.ly/IczyvT
  9. Soundcloud Developer contest with acapela Text to Speech ! --> developers.soundcloud.com/blog/contest-s… #TTS #Acapela @SoundCloudAPI
  10. @GadahAlOfisan no need of upgrade, 1.201 IS compatible with iOS5. If not, drop me an email through contact (website)
  11. @valross2 drop me an email with contact form of acapela-tts-for iphone website and I will add you into the list
  12. @valross2 by the way, no need to count in callback ... Word delegate return a NSRange with length and position for each word :-)
  13. @valross2 1.300 version with japanese, chinese (and australian) will be soon in QA ... beta tests will begins soon also.
  14. @valross2 you count the total number before tts, and at each word callback, you increment a counter with strlen of the word
  15. @valross2 so your only reference is the origin of TTS: the text ... probably that count characters is better to count words
  16. @valross2 ... give clue to synthesizer, but not strict rules, allowing him to build the clearest and natural speech as possible
  17. @valross2 and so, he didn't know exactly the final duration of speech (due to Unit Selection technology where language analysis ...
  18. @valross2 yes ... I don't think you have access to remaining duration ... as TTS is realtime, engine begin to stream to audio asap
  19. @valross2 oh yes ... mhm, there is the word callback ... a quick hack would be to count the number of word before tts and incr. meter in cb
  20. @valross2 Hi ... I've plan to add some new tutorials on the blog, later this year ... about time played, what do you mean?