On Fri, May 13, 2011 at 8:44 PM, Gabriel Gunderson <gabe@gundy.org> wrote:

On Mon, May 2, 2011 at 4:27 PM, Avi Marcus <avi@avimarcus.net> wrote:

...

I've tried this cool formula for streaming TTS via google: http://wiki.freeswitch.org/wiki/TTS and while the link produces a pretty darn nice sounding MP3, I get: 2011-05-03 01:16:47.828769 [ERR] mod_shout.c:804 Error: MPG123 Error at /usr/src/freeswitch/src/mod/formats/mod_shout/mod_shout.c:627. 2011-05-03 01:16:47.828769 [ERR] mod_shout.c:807 Error from mpg123: Invalid mpg123 handle. (code 10) Is anyone else using this reliably?

Yes, I too can confirm that others are using this reliably.

What more can you tell us about your problem?

Best, Gabe

Hello,

Just wanted to find out when you say "reliably" is this being used in production on a relatively small/medium load, like maybe 10-20 look-ups/translations per second? The last I checked (about 4-5 mths ago) after about 10 or so (can't remember the exact number) Google throws out a Captcha as a challenge. Now, that could also be since I was doing this over a web-browser. Does it change or doesn't have that limitation when using mod_shout in freeswitch? Thanks so much

they will do if overload occurs ----- Original Message ----- From: Michael Collins To: FreeSWITCH Users Help Sent: Tuesday, May 17, 2011 12:55 PM Subject: Re: [Freeswitch-users] Is Anyone Using Google TTS? I have to wonder if Google thinks 10-20 lookups per second from a single client is a "light/medium" load. That's 36K - 72K lookups per hour. If I were you I would tcpdump the traffic and see what Google is "really" sending back. I doubt that Google cares about the distinction between a browser and other types of clients. -MC On Mon, May 16, 2011 at 11:19 PM, A E [Gmail] <all.eforums@gmail.com> wrote: On Fri, May 13, 2011 at 8:44 PM, Gabriel Gunderson <gabe@gundy.org> wrote: On Mon, May 2, 2011 at 4:27 PM, Avi Marcus <avi@avimarcus.net> wrote: > I've tried this cool formula for streaming TTS via google: > http://wiki.freeswitch.org/wiki/TTS > and while the link produces a pretty darn nice sounding MP3, I get: > 2011-05-03 01:16:47.828769 [ERR] mod_shout.c:804 Error: MPG123 Error at > /usr/src/freeswitch/src/mod/formats/mod_shout/mod_shout.c:627. > 2011-05-03 01:16:47.828769 [ERR] mod_shout.c:807 Error from mpg123: Invalid > mpg123 handle. (code 10) > Is anyone else using this reliably? Yes, I too can confirm that others are using this reliably. What more can you tell us about your problem? Best, Gabe Hello, Just wanted to find out when you say "reliably" is this being used in production on a relatively small/medium load, like maybe 10-20 look-ups/translations per second? The last I checked (about 4-5 mths ago) after about 10 or so (can't remember the exact number) Google throws out a Captcha as a challenge. Now, that could also be since I was doing this over a web-browser. Does it change or doesn't have that limitation when using mod_shout in freeswitch? Thanks so much _______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org ------------------------------------------------------------------------------ _______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org

On Tue, May 17, 2011 at 1:21 PM, Nicolas Brenner <nico@clickfono.com> wrote:

Be careful about the legal implications of using Google's TTS in your system. There are a few discussions on Google Groups (e.g. http://goo.gl/TvRVR) about the possibility of using Google's TTS for applications other than just Google Translate on the web, and there's a Google employee (DeWitt) saying that there are no Terms of Service (ToS), nor an official API for their TTS system, so that you should abide by their general ToS, and that "[TTS wasn't] designed for internal usage only, will likely change or break over time, and thus shouldn't be accessed by external developers"

Yeah that seems to be getting into a territory that only the big boys can play in. Last thing I want is to be in trouble with the Big 'G', triple OG! Maybe we'll keep the usage of Google TTS just for playing with it and occasional translations to use as a benchmark coz the quality *is* damn good.

On Tue, May 17, 2011 at 12:55 PM, Michael Collins <msc@freeswitch.org>wrote:

I have to wonder if Google thinks 10-20 lookups per second from a single client is a "light/medium" load. That's 36K - 72K lookups per hour. If I were you I would tcpdump the traffic and see what Google is "really" sending back. I doubt that Google cares about the distinction between a browser and other types of clients.

-MC

Haha sorry for that air-headed comment. Didn't really do the math in my head. Really should have said "heavy" load :) As for it caring whether it's a client or a browser, I'm not sure. I read somewhere that seeing some of the header attributes (that typically browsers send) it will either send you an MP3 file or return a "404" but that doesn't seem to be the problem anyone else has mentioned when using it with mod_shout. I do know about the captcha as I saw it on 2-3 occasions but it might have its own rules i.e. 10 translations in one minute from the same IP might throw it out to prevent abuse. No one else seems to have run into it, it seems though so that might mean that kind of a rule doesn't exist. Needs more investigation