Red Hat Bugzilla – Bug 198908
festival should be built with ESD support.
Last modified: 2007-11-30 17:11:37 EST
Description of problem:
For some reason, the supplied configuration of festival is to build without ESD
support. This can be fixed as easily as uncommenting the line "INCLUDE_MODULES
+= ESD_AUDIO" in speech_tools/config/config.in. I just did a test build that
way and it works fine. (And now my verbalizing chat system, using festival, no
longer conflicts with xmms &c.)
Version-Release number of selected component (if applicable):
Considering that the build lacks ESD..."every time".
Steps to Reproduce:
Put this in .festivalrc:
(Parameter.def 'Audio_Method 'esdaudio)
festival whines about having no compiled ESD support.
Is ESD still the best approach? Because, y'know, it kinda sucks.
Anyway, I'll change it (in my in-progress package) so support is compiled in.
I'm not sure about making it the default, though.... (Note I'm not officially
the maintainer. But I've been working on this package for a while.)
esd should not be default at this point (notably we won't have esd running under
gdm and festival will be used there for accessible login)
The issue was never making esd a default; rather, it is merely having it built
with esd support enabled, so that esd use is available if wanted. It costs
nothing to have it compiled into the binary, considering that the support exists
and needs only to be enabled.
For some reason, enabling the esd module pulls in
MODULE_EXTRA_LIBS += -L$(X11_LIB) -lX11 -lXt
in the makefile.
This is seems pretty silly, so I'm going to try to patch it out. If that doesn't
work, then I'm inclined to let this one sit.
So, that works. But it turns out that the ESD module defaults to higher priority
than plain Linux audio, so I also had to patch the init.scm to make it not the
It'd be even nicer to make it use esd if it's running and not otherwise. And
possible, too. But I'll save that for another day....
See bug #232105 for in-progress updated packages which address this issue.
This issue should be resolved by the release of festival-1.96-0.11, now in the
development tree. (See bug #232105 for details.)
Please reopen if there's still a problem. Thanks.