› Forums › Speech Synthesis › Festival › Unit Selection exercise – No module named ‘EST_Utterance’
- This topic has 3 replies, 3 voices, and was last updated 6 months, 3 weeks ago by Will L.
-
AuthorPosts
-
-
January 18, 2024 at 18:19 #17423
I’m running Festival on a Mac (OS 13.2.1). Everything has gone fine up to the point of running
bash$ phone_lengths dur lab/*.lab
(step 10.1 in the Unit Selection directions). The error I’m getting is:Traceback (most recent call last):
File “/Users/wlamb/speech_processing/tools//multisyn_build/bin/phone_lengths”, line 17, in <module>
import EST_Utterance
ModuleNotFoundError: No module named ‘EST_Utterance’phone_lengths
has this lineestmoduledir = "%s/wrappers/python" % estbase
– but there is nopython
subdirectory in mywrappers
directory as far as I can tell. Grateful for help or suggestions. -
January 18, 2024 at 18:50 #17436
As noted in the first class, it is non-trivial to build the version of Festival required for this exercise: it requires compilation of Python wrappers for the underlying C++ code using SWIG. Getting this compilation to work correctly involves performing Magic.
We strongly recommend using the lab machines, where everything Just Works.
Anyone really determined to build their own Python wrappers should bring their machine to a lab session and smile very nicely at Korin.
-
January 19, 2024 at 16:01 #17448
Yes, some of the Multisyn build tools are python scripts which need extension module wrapper around Edinburgh Speech Tools (compiled native binaries). There are 2 options:
i) if you look in the $EST/config/config file in your EST directory, you’ll see an option to switch on compilation of those wrappers to match your architecture. That might just work.
ii) The last section of CPSLP was on extension modules and used a wrapper around EST as an exercise. It’s available for Mac (intel) & Linux python versions 3.8 and 3.9. You could try importing that (on a mac you’d need to use a x86_64 version of python). If that works, the interface is *slightly* different to that used by the multisyn build tools, so you’d need to slightly tweak the multisyn build tools python scripts which use it, but nothing major – just a slightly different, updated API.
-
January 21, 2024 at 20:24 #17455
Thanks both. I got everything up and running on a lab machine, just incase.
Korin, I’ve made the change you recommended to the config file. I’ll pick up with you – and smile as nicely as I can – during next week’s lab
-
-
AuthorPosts
- You must be logged in to reply to this topic.