Hi everyone,
can anyone tell me if there is some software for simulate singing voices? It can be cool if there is a spanish oriented one
my OS is Mac OS X 10.4.8 ppc
thanks
Descarga gratis la Barra de Herramientas de MSN http://www.msn.es/usuario/busqueda/barra?XAPID=2031&DI=1055&SU=http%...
vosim, chant, spasm, and Perry Cooks new thing that follows lip positions, and in Pd there if [paf~], and if you can't find it for any reason I have the source.
andy
On Sat, 26 May 2007 19:36:07 +0000 "josue moreno" josuemoreno1@hotmail.com wrote:
Hi everyone,
can anyone tell me if there is some software for simulate singing voices? It can be cool if there is a spanish oriented one
my OS is Mac OS X 10.4.8 ppc
thanks
Descarga gratis la Barra de Herramientas de MSN http://www.msn.es/usuario/busqueda/barra?XAPID=2031&DI=1055&SU=http%...
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
is there a 'pd speak' abstraction or external somewhere?
i have never seen one.
There is an external for Festival Lite - think it's called flite; was tricky to compile the last time I used it; it renders sentences to audio in tables iirc - was a while ago I tried it. I think pd-radio used it too, but I could be wrong...
hard off wrote:
is there a 'pd speak' abstraction or external somewhere?
i have never seen one.
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Hallo, Claude Heiland-Allen hat gesagt: // Claude Heiland-Allen wrote:
There is an external for Festival Lite - think it's called flite; was tricky to compile the last time I used it; it renders sentences to audio in tables iirc - was a while ago I tried it. I think pd-radio used it too, but I could be wrong...
There also is ratts, which is very cool.
Frank Barknecht _ ______footils.org_ __goto10.org__
On Sat, 2007-06-02 at 10:15 +0200, Frank Barknecht wrote:
Hallo, Claude Heiland-Allen hat gesagt: // Claude Heiland-Allen wrote:
There is an external for Festival Lite - think it's called flite; was tricky to compile the last time I used it; it renders sentences to audio in tables iirc - was a while ago I tried it. I think pd-radio used it too, but I could be wrong...
There also is ratts, which is very cool.
i found the external in:
<pd-cvs>/abstractions/rradical/instruments/speakerboxx/ratts.pd_linux
but i couldn't find a help file. also when i create it, i get the message:
ratts: Realtime Analog Text-To-Speech externals v0.04 by Bryan Jurish ratts: Based on text-to-speech code by Nick Ing-Simmons and Jon Iles ratts: and PD external code by Orm Finnendahl and Travis Newhouse
but the object doesn't get any inlets nor outlets. maybe you can tell us a bit more about this external?
___________________________________________________________ Der frühe Vogel fängt den Wurm. Hier gelangen Sie zum neuen Yahoo! Mail: http://mail.yahoo.de
Hallo!
Bryan Jurish is the speech expert in pd world ;) ... you can find all his stuff here: http://www.ling.uni-potsdam.de/~moocow/projects/pd/
There are the ratts and flite externals. I think he also made an external for the mbrola speech synthesizer, but did not release it ...
Yes, for the pd radio I used the flite external, which is quite okay but only english ... If you want to make other languages you can use mbrola via a shell script (I can send you one if you are interested).
LG Georg
moin Georg, moin list,
On 2007-06-02 12:34:18, Georg Holzmann grhPD@gmx.at appears to have written:
Hallo!
Bryan Jurish is the speech expert in pd world ;) ... you can find all his stuff here: http://www.ling.uni-potsdam.de/~moocow/projects/pd/
Thanks for plugging my site Georg... saves me some typing ;-)
There are the ratts and flite externals. I think he also made an external for the mbrola speech synthesizer, but did not release it ...
Sorry, never made an mbrola external -- mbrola is closed-source free-as-in-beer-ware. Somebody (I forget who) wrote a MAX external for mbrola a few years back, and unto him did I praise and extol the wonders and glories of flext, but lo, the release was binary, and it was only unto the Mac, and there was much wailing and gnashing of teeth.
I did make an ugly-hack patch at one point using ext13 (pipein~?) to talk to mbrola over named fifos, but it never worked particularly well.
I have another (far, far uglier but at least functional) system that looks like (pd <--(OSC)--> perl <--(TCP)--> festival --(system calls?)--> mbrola --> temp files --> pd), but the guts are all freely available (SayWhat is the perl part, festival works "out-of-the-box", and my patches basically require my entire patch library, which I'm too lazy to package at the moment). If anyone is terribly interested, I can tar up my whole pd patch library and point you at the relevant patches.
Yes, for the pd radio I used the flite external, which is quite okay but only english ...
It's allegedly possible to compile a flite library for any festival language-model built with the festvox tools (note: this does not include German: AFAIK the only festival support for German is from IMS Stuttgart, they've stopped supporting it, and I personally have never gotten it to compile, even after much wailing, gnashing of teeth, etc.)
I'm not sure how well the pd flite interface actually supports multiple languages -- I've only ever tested it with the default english models. It should be pretty straightforward to compile & link it against an alternate flite library though. If anyone succeeds, I'm happy to discuss how to go about generalizing the build procedure.
marmosets, Bryan
Hello
Le dimanche 03 juin 2007 à 00:40 +0200, Bryan Jurish a écrit :
It's allegedly possible to compile a flite library for any festival language-model built with the festvox tools (note: this does not include German: AFAIK the only festival support for German is from IMS Stuttgart, they've stopped supporting it, and I personally have never gotten it to compile, even after much wailing, gnashing of teeth, etc.)
I'm not sure how well the pd flite interface actually supports multiple languages -- I've only ever tested it with the default english models. It should be pretty straightforward to compile & link it against an alternate flite library though. If anyone succeeds, I'm happy to discuss how to go about generalizing the build procedure.
marmosets, Bryan
thank for making pd speak, I've successfully compiled [flite] for amd64 on ubuntu feisty, but i had to hack the configure file, the -fPIC flag was missing, so I've added this one at line 3845:
WFLAGS="-Wall -fPIC"
I didn't test if this code is compatible with other architectures, I'm not an expert, :D.
It wasn't enough, [flite] dependances has been installed with apt-get, then the flite headers and libraries wasn't in a place expected by the configure file (I didn't have chace with --with-flite-dir option). I didn't modify the configure file very elegantly for having the script finding headers and libraries, but it has worked...
IFLAGS="$IFLAGS -I/usr/include/flite" LFLAGS="$LFLAGS -L/usr/lib"
I hope those informations will help for having availability of clean sources of [flite] for x86_64 arch on ubuntu without pain... Thank in advance.
Also, playing with the help file has been a real fun, because making pd speaking is a kind of drool experience...(thanks hardoff of this resurrection). The attached file is a modification of the help patch I've made for resolving a buffer issue, I've just added a banged message [;array const 0( before flite computes the voice, for emptying the buffer, it's one method among many others...
And finaly, anyone knows how to configure the synthetized voice?
Patko.
Le vendredi 08 juin 2007 à 17:21 +0200, patrice colet a écrit :
the -fPIC flag was missing, so I've added this one at line 3845:
WFLAGS="-Wall -fPIC"
I had to do the same thing with [ratts], at line 4389:
OFLAGS="-O6 -funroll-loops -fomit-frame-pointer -fno-strict-aliasing
-fPIC"
It wasn't enough, [flite] dependances has been installed with apt-get, then the flite headers and libraries wasn't in a place expected by the configure file (I didn't have chace with --with-flite-dir option).
This time, the configure script has found the flite headers without modifying anything or putting any tag, cool!
Patko.
PS: sorry for the bad english...
moin Patrice,
On 2007-06-08 17:21:48, patrice colet megalegoland@yahoo.fr appears to have written:
thank for making pd speak, I've successfully compiled [flite] for amd64 on ubuntu feisty, but i had to hack the configure file, the -fPIC flag was missing, so I've added this one at line 3845:
WFLAGS="-Wall -fPIC"
I didn't test if this code is compatible with other architectures, I'm not an expert, :D.
-fPIC should be linux-safe; I'm actually surprised it wasn't there already... at any rate, it's there now (in cvs): thanks for the report. just for the record, what happened when you tried to compile without -fPIC ?
It wasn't enough, [flite] dependances has been installed with apt-get, then the flite headers and libraries wasn't in a place expected by the configure file (I didn't have chace with --with-flite-dir option). I didn't modify the configure file very elegantly for having the script finding headers and libraries, but it has worked...
IFLAGS="$IFLAGS -I/usr/include/flite" LFLAGS="$LFLAGS -L/usr/lib"
Funny, it works here (debian) with the deb-default flite (and -dev) locations... in such situations (i.e. "non-standard" prefab installation locations), the "official" solution for anything built with the gnu autotools (like flite or any other of my externals) is to set the environment variables such as CPPFLAGS (C preprocessor flags, *not* c-plus-plus flags), CFLAGS (C compiler flags), LDFLAGS (linker flags), LIBS (additional libraries) etc.; so you could do something like:
$ export CPPFLAGS="-I/usr/include/flite" $ export LDFLAGS="-L/usr/lib" $ ./configure ; make ; make install
... and the build ought to work without having to hack the configure script. I think that this is a pretty good way to handle arbitrary installation locations & distribution foibles, so I do not plan on changing this behavior or the default locations.
The attached file is a modification of the help patch I've made for resolving a buffer issue, I've just added a banged message [;array const 0( before flite computes the voice, for emptying the buffer, it's one method among many others...
what happens on your system if you don't explicitly zero the array before re-synthesis?
And finaly, anyone knows how to configure the synthetized voice?
Basically: you can't do that with the pd [flite] object in its current form (sorry).
It is (supposedly) possible, though: there is a bizarre and cryptic C-level flite API to allow tweaking of some of the many configuration parameters that festival offers, but I'm not a festival expert, I rather dislike SCHEME (give me LISP!), and trying to figure out which of festival's SCHEME-coded options got transmogrified into which of flite's C structures & parameters without sufficient documentation or examples is more than I felt like dealing with; I may get around to it some day, but it's not too high on my list of priorities as long as [flite] continues to block the cpu during synthesis. If you want/need user-configurable _offline_ synthesis, consider using festival directly (e.g. from pd with SayWhat over OSC).
marmosets, Bryan
Hello!
Le samedi 09 juin 2007 à 01:22 +0200, Bryan Jurish a écrit :
-fPIC should be linux-safe; I'm actually surprised it wasn't there already... at any rate, it's there now (in cvs): thanks for the report. just for the record, what happened when you tried to compile without -fPIC ?
The source files came from http://www.ling.uni-potsdam.de/~moocow/projects/pd/:
$ ./configure checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for gawk... gawk checking whether make sets $(MAKE)... yes checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking for style of include used by make... GNU checking dependency style of gcc... gcc3 checking for a BSD-compatible install... /usr/bin/install -c checking for flite.h... yes checking for flite_init in -lflite... yes checking for cmu_lex_init in -lflite_cmulex... yes checking for usenglish_init in -lflite_usenglish... yes checking for register_cmu_us_kal in -lflite_cmu_us_kal16... yes checking whether we are building a debug version... no configure: creating ./config.status config.status: creating config/Makefile config.status: WARNING: config/Makefile.in seems to ignore the --datarootdir setting config.status: creating Makefile config.status: WARNING: Makefile.in seems to ignore the --datarootdir setting config.status: creating config.h config.status: config.h is unchanged config.status: executing depfiles commands
$ make
make all-recursive
Making all in config
if gcc -DHAVE_CONFIG_H -I. -I. -I. -DHAVE_CONFIG_H -I/usr/local/pd/src
-I/usr/include/flite -O6 -funroll-loops -fomit-frame-pointer -Wall
-MT flite.o -MD -MP -MF ".deps/flite.Tpo" -c -o flite.o flite.c;
then mv -f ".deps/flite.Tpo" ".deps/flite.Po"; else rm -f
".deps/flite.Tpo"; exit 1; fi
gcc -O6 -funroll-loops -fomit-frame-pointer -Wall -o flite.pd_linux
-L/usr/lib -export_dynamic -shared flite.o -lflite_cmu_us_kal16
-lflite_usenglish -lflite_cmulex -lflite -lm
/usr/bin/ld: flite.o: relocation R_X86_64_32 against `a local symbol'
can not be used when making a shared object; recompile with -fPIC
flite.o: could not read symbols: Bad value
The attached file is a modification of the help patch I've made for resolving a buffer issue, I've just added a banged message [;array const 0( before flite computes the voice, for emptying the buffer, it's one method among many others...
what happens on your system if you don't explicitly zero the array before re-synthesis?
If I want to process a long sentence and after, a short one, I still have the end of the long sentence into the table. Thanks for the configure advice, Patko
Hallo, Roman Haefeli hat gesagt: // Roman Haefeli wrote:
i found the external in:
<pd-cvs>/abstractions/rradical/instruments/speakerboxx/ratts.pd_linux
Oops, that binary doesn't belong there. I'll need to remove it.
See Georg's mail for answers to the other questions.
Frank Barknecht _ ______footils.org_ __goto10.org__
Hi list,
I've toyed around with Ratts quite a bit and when you do have the
help files it makes everything seem more complicated than it really
is. So, here's a little patch that contains the bare essentials that
you need to do start experimenting with Ratts:
ratsass.pd:
#N canvas 87 74 462 312 10; #X obj 259 232 dac~; #X obj 221 96 guessphones; #X obj 221 179 klatt~; #X obj 335 105 tgl 15 0 empty empty empty 0 -6 0 8 -262144 -1 -1 1 1; #X obj 220 117 phones2holmes f; #X obj 271 203 freeverb~; #X obj 335 125 metro 15; #X msg 155 120 basec $1; #X floatatom 155 102 5 0 0 0 - - -; #X msg 14 7 I wanna be your witch doktah oh yeah; #X msg 142 148 f0decl 20; #X obj 216 140 holmes f0decl 0 topc -30; #X msg 14 49 this is SO crazy; #X msg 14 28 yo homes; #X msg 14 71 browthoom koma blessooth yoelin; #X obj 334 85 loadbang; #X connect 1 0 4 0; #X connect 2 0 0 0; #X connect 2 0 0 1; #X connect 2 0 5 0; #X connect 3 0 6 0; #X connect 4 0 11 0; #X connect 5 0 0 0; #X connect 5 1 0 1; #X connect 6 0 11 0; #X connect 7 0 11 0; #X connect 8 0 7 0; #X connect 9 0 1 0; #X connect 10 0 11 0; #X connect 11 0 2 0; #X connect 12 0 1 0; #X connect 13 0 1 0; #X connect 14 0 1 0; #X connect 15 0 3 0;
On 2-Jun-07, at 5:53 AM, Roman Haefeli wrote:
On Sat, 2007-06-02 at 10:15 +0200, Frank Barknecht wrote:
Hallo, Claude Heiland-Allen hat gesagt: // Claude Heiland-Allen wrote:
There is an external for Festival Lite - think it's called flite;
was tricky to compile the last time I used it; it renders sentences
to audio in tables iirc - was a while ago I tried it. I think pd-radio
used it too, but I could be wrong...There also is ratts, which is very cool.
i found the external in:
<pd-cvs>/abstractions/rradical/instruments/speakerboxx/ratts.pd_linux
but i couldn't find a help file. also when i create it, i get the message:
ratts: Realtime Analog Text-To-Speech externals v0.04 by Bryan Jurish ratts: Based on text-to-speech code by Nick Ing-Simmons and Jon Iles ratts: and PD external code by Orm Finnendahl and Travis Newhouse
but the object doesn't get any inlets nor outlets. maybe you can
tell us a bit more about this external?___________________________________________________________ Der frühe Vogel fängt den Wurm. Hier gelangen Sie zum neuen Yahoo!
Mail: http://mail.yahoo.de
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/ listinfo/pd-list
-- Pall Thayer palli@pallit.lhi.is http://www.this.is/pallit
moin Pall, moin list,
Many apologies that the ratts help files seem to be less than entirely intuitive to first-time users; in my defense, I can only say: "sheesh, man, if you folks think the ratts pd API is poorly documented, y'all should see the rsynth code"...
ok, now that I've gotten that out of my system (no flame intended, honestly): do you have an immediate suggestion as to how I could improve things? I realize that a ratts chain has more user-settable parameters than you can shake a proverbial stick at, but the defaults should be sensible (if you want something that sounds vaguely like human speech), and playing with those strange animals is half the fun ;-) I included the 'ratts~' abstraction so that users could get an idea how all those separate objects work together and/or just "make pd talk"; and I rather hoped that the 'ratts-help.pd' help patch would suffice for an overview of the objects in it... oh well...
marmosets, Bryan
On 2007-06-02 15:49:43, Pall Thayer palli@pallit.lhi.is appears to have written:
Hi list,
I've toyed around with Ratts quite a bit and when you do have the help files it makes everything seem more complicated than it really is. So, here's a little patch that contains the bare essentials that you need to do start experimenting with Ratts:
ratsass.pd:
[snip]
Hi Bryan,
No need to apologize. I wasn't trying to suggest that there was
anything wrong with Ratts. I think Ratts is really cool and I used it
in a recent online project called "On Everything" (http://
pallit.lhi.is/on_everything). But when I started looking at voice
synthesis through PD, I wasn't looking for anything complex with lots
of capabilities. I just wanted a really synthy sounding voice inside
PD. It took me a while to glean from the help files, the bare
essentials to getting PD+ratts to "say" something and when I did, it
turned out to be a lot simpler than I felt that the sample and help
files made it look at first. So, perhaps it would be good to have one
patch with the help files that is just the bare minimum. Some of us
like to get that so we can then dive right in and start experimenting
with it ourselves.
But again, ratts is great and I expect to use it in some future
projects as well.
Pall
On 2-Jun-07, at 6:40 PM, Bryan Jurish wrote:
moin Pall, moin list,
Many apologies that the ratts help files seem to be less than entirely intuitive to first-time users; in my defense, I can only say: "sheesh, man, if you folks think the ratts pd API is poorly documented, y'all should see the rsynth code"...
ok, now that I've gotten that out of my system (no flame intended, honestly): do you have an immediate suggestion as to how I could
improve things? I realize that a ratts chain has more user-settable
parameters than you can shake a proverbial stick at, but the defaults should be sensible (if you want something that sounds vaguely like human
speech), and playing with those strange animals is half the fun ;-) I included the 'ratts~' abstraction so that users could get an idea how all those separate objects work together and/or just "make pd talk"; and I
rather hoped that the 'ratts-help.pd' help patch would suffice for an
overview of the objects in it... oh well...marmosets, Bryan
On 2007-06-02 15:49:43, Pall Thayer palli@pallit.lhi.is appears to have written:
Hi list,
I've toyed around with Ratts quite a bit and when you do have the
help files it makes everything seem more complicated than it really is.
So, here's a little patch that contains the bare essentials that you
need to do start experimenting with Ratts:ratsass.pd:
[snip]
-- Bryan Jurish "There is *always* one more
bug." jurish@ling.uni-potsdam.de -Lubarsky's Law of Cybernetic
Entomology
-- Pall Thayer palli@pallit.lhi.is http://www.this.is/pallit
moin Roman, moin all,
On 2007-06-02 11:53:21, Roman Haefeli reduzierer@yahoo.de appears to have written:
but i couldn't find a help file. also when i create it, i get the message:
ratts: Realtime Analog Text-To-Speech externals v0.04 by Bryan Jurish ratts: Based on text-to-speech code by Nick Ing-Simmons and Jon Iles ratts: and PD external code by Orm Finnendahl and Travis Newhouse
but the object doesn't get any inlets nor outlets. maybe you can tell us a bit more about this external?
Since Georg has already plugged my site (thanks, Georg!) , I will refrain from doing so at this juncture.
[ratts] is just a dummy object which causes the whole library to be loaded. <rant>I used to be (actually, I still am) of the opinion that every external *library* should be dynamically loadable (which they are), and that it should be possible for any given abstraction to specify the libraries it requires by placing library-named objects (e.g. [zexy], [ratts], etc.) onto its canvas. Unfortunately, in my case, this practice has lead to much wailing and gnashing of teeth in particular with respect to pd-0.40.x and flext-based externals. Don't ask me why.</rant>
If you grab the "official" ratts distribution, you should have a help-file ratts-help.pd for [ratts] which gives you an overview of the various objects and abstractions in the library. If you just want pd to talk, check out the "ratts~" abstraction: text in, speech signal out.
marmosets, Bryan