We have moved at community.getvera.com

Author Topic: New TTS engines  (Read 12124 times)

Offline lolodomo

  • Moderator
  • Master Member
  • *****
  • Posts: 3484
  • Karma: +74/-10
Re: New TTS engines
« Reply #30 on: January 23, 2014, 06:37:13 pm »
@ericonvera : I have committed (in the trunk), it is a first step, improvments are possible.
It only covers the point 1 I mentioned earlier in the day.

New variables:
- DefaultEngineTTS: use either GOOGLE or OSX_TTS_SERVER
- OSXTTSServerURL: set the URL of your personal TTS server, something like http://myserver.org:12345

It is working with the two engines.
« Last Edit: January 23, 2014, 07:41:47 pm by lolodomo »

Offline ericonvera

  • Sr. Newbie
  • *
  • Posts: 24
  • Karma: +0/-0
Re: New TTS engines
« Reply #31 on: January 23, 2014, 07:04:50 pm »
@lolodomo that is great news

Sent from my SCH-I545 using Tapatalk


Offline SM2k

  • Full Member
  • ***
  • Posts: 179
  • Karma: +4/-0
Re: New TTS engines
« Reply #32 on: January 25, 2014, 03:47:50 pm »
@ericonvera : I have committed (in the trunk), it is a first step, improvments are possible.
It only covers the point 1 I mentioned earlier in the day.

New variables:
- DefaultEngineTTS: use either GOOGLE or OSX_TTS_SERVER
- OSXTTSServerURL: set the URL of your personal TTS server, something like http://myserver.org:12345

It is working with the two engines.

I've glanced at trunk, and there's a lot more files than there used to be.

If I wanted to smoke-jump and install from trunk, I assume I'll need everything in the services directory in addition to roughly what the wiki says for beta 2. It looks like S_SonosAVTransport1.xml was renamed to S_AVTransport1.xml and likewise for S_SonosGroupRenderingControl1.xml -> S_RenderingControl1.xml, correct?

Could I safely remove the beta 2 files after uploading everything from trunk?

Offline SM2k

  • Full Member
  • ***
  • Posts: 179
  • Karma: +4/-0
Re: New TTS engines
« Reply #33 on: January 25, 2014, 04:13:12 pm »
Nevermind! I realized the comments on the files in the services directory were along the lines of "hide stuff that isn't ready/doesn't need to be dealt with". I went ahead and installed the files and have text to speech coming from my mac now. :D

Offline allmoney.ws

  • Full Member
  • ***
  • Posts: 105
  • Karma: +0/-0
  • Vera 3
Re: New TTS engines
« Reply #34 on: January 31, 2014, 06:37:59 pm »
One of the best engines I have come across is this one : http://demo.acapela-group.com/

Sounds perfect in my language (Danish)

Oh yes, not too bad in French too 8)
Russian voice better that Google TTS ;)

Offline flyveleder

  • Full Member
  • ***
  • Posts: 191
  • Karma: +5/-14
Re: New TTS engines
« Reply #35 on: February 12, 2014, 06:24:05 am »
Is anyone working on how to get Acapela TTS working with the Sonos Plugin ?

Offline lolodomo

  • Moderator
  • Master Member
  • *****
  • Posts: 3484
  • Karma: +74/-10
Re: New TTS engines
« Reply #36 on: February 12, 2014, 08:36:05 am »
Is anyone working on how to get Acapela TTS working with the Sonos Plugin ?

If you can provide a lua function that returns the URL of the produced (local) audio file and duration (in seconds) with text and language as input parameters, I will add it with pleasure to the plugin and more generally to the TTS library.

First you need to know what kind of API is available. If HTTP API is available, it should be doable relatively easily.

Offline flyveleder

  • Full Member
  • ***
  • Posts: 191
  • Karma: +5/-14
Re: New TTS engines
« Reply #37 on: February 12, 2014, 09:00:55 am »
I can provide you with exactly nothing :-) I don't have a clue about lua programming or know if acapela provides with public API.

My question was merely if someone was looking into it; Otherwise I will lower my expectations ;-)

(Google TTS is doable - but far from perfect).

Thanks,
Martin