Skip Menu |

This queue is for tickets about the Speech-Google-TTS CPAN distribution.

Report information
The Basics
Id: 90844
Status: open
Worked: 25 min
Priority: 0/
Queue: Speech-Google-TTS

People
Owner: NIELSD [...] cpan.org
Requestors: gisbert.selke [...] wido.bv.aok.de
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)



Subject: Undeclared external dependencies in Speech::Google::TTS
Date: Wed, 27 Nov 2013 03:39:14 +0100
To: <bug-Speech-Google-TTS [...] rt.cpan.org>
From: "Selke, Gisbert W." <gisbert.selke [...] wido.bv.aok.de>
The module contains a number of hard-coded requirements that will not hold anywhere. In particular, there is a hard-coded reference to /usr/bin/mpg123 and one to /usr/bin/sox, which will, in all likelihood, not exist outside Unix systems, and even there these may not be present. Furthermore, the directory for tempfiles is hard-coded to /var/tmp, which again will, in general, not exist on non-Unix systems. This latter requirement can, incidentally, easily be dropped, since File::Temp uses a sensible default for the tmp directory, viz., the one provided by File::Spec->tmpdir. This default should be safe and portable enough. The (as yet, minimal) module tests do not catch these error conditions, because they check nothing beyond successful loading of the module. \Gisbert
Sorry, first sentence should, of course, have read "will not hold *everywhere*" instead of "anywhere".
Subject: fixed Temp
Hi GWS, thanks for your message. The temp file path could be overwritten during configuration after initialization by $self->{'tmpdir'} and usually should be set on larger scale and/or low latency applications (like PBXes / phone IVRs) to a ramdisc or similiar. I've pointed it to system independent temdir from File::Temp temdir now. I'm still developing (and using) a caching mechanism which requires (by performance principles) further changes to the naming conventions within the temp dir and where a ramdisk makes much more sense for many applications too. Will publish it after some further tesing asap too. Changes are gone into 0.74 which i've uploaded now to CPAN. cheerioh, Niels.
Hi GWS, thanks for your message. As described in README sox is not required on any system but mpg123 or mpg321 is required. I did not found any way to define external software requirements in the Build system until now. If you can point me to a resource / example about such a requirement definition this would be nice. May be that at least the wav/mp3 conversion could be performantly done by a full Perl module (without any C/binary stuff), but i did not tried it until today - for me it works perfectly with mpg123/321 so far on Linux and NetBSD. SOX is just ONE possibility to use the file conversion more flexible for peoples which want to use sox explicitely - i.e. to generate mlaw for IVRs on ISDN or similiar. many thanks, Niels.
Subject: AW: [rt.cpan.org #90844] fixed Temp
Date: Wed, 27 Nov 2013 12:16:42 +0100
To: <bug-Speech-Google-TTS [...] rt.cpan.org>
From: "Selke, Gisbert W." <gisbert.selke [...] wido.bv.aok.de>
Hallo Niels -- Vielen Dank für die superschnelle Reaktion! Ich gebe zu, ich hatte nicht ins Readme geguckt, sondern hatte mich auf die formalisierten Dependencies verlassen -- wo ich aber zumindest auf die Schnelle auch nicht sehe, wie man da Non-Perl-Dependencies einträgt :-( Vorschläge: 1. sicherheitshalber ins POD die Abhängigkeit eintragen? 2. einen Test bauen, der tatsächlich etwas zu tun versucht -- dann fliegt einem der Build um die Ohren, dann weiß man wenigstens, dass man ein Problem hat. (Und dafür sind Tests ja da ;-) ) Bis denn -- \Gisbert Show quoted text
> -----Ursprüngliche Nachricht----- > Von: Niels Dettenbach via RT [mailto:bug-Speech-Google-TTS@rt.cpan.org] > Gesendet: Mittwoch, 27. November 2013 10:29 > An: Selke, Gisbert W. > Betreff: [rt.cpan.org #90844] fixed Temp > > <URL: https://rt.cpan.org/Ticket/Display.html?id=90844 > > > Hi GWS, > > thanks for your message. > > The temp file path could be overwritten during configuration after > initialization by $self->{'tmpdir'} and usually should be set on larger scale > and/or low latency applications (like PBXes / phone IVRs) to a ramdisc or > similiar. I've pointed it to system independent temdir from File::Temp temdir > now. > > I'm still developing (and using) a caching mechanism which requires (by > performance principles) further changes to the naming conventions within > the temp dir and where a ramdisk makes much more sense for many > applications too. Will publish it after some further tesing asap too. > > Changes are gone into 0.74 which i've uploaded now to CPAN. > > cheerioh, > > > Niels.