ReadBeyond

Results 23 issues of ReadBeyond

Right now it is cumbersome to list all the languages/voices/variants for each TTS wrapper. There are several duplications. Moreover, e.g. in the case of Festival, it is not possible to...

functionality
code

Several improvements can be made: 1. The Nuance and the AWS wrappers share some code => move it inside a new base class for cloud TTS services. 2. One might...

bug
functionality
code
architecture

At least ``cdtw`` and ``cew`` can be interesting on their own. Again, that would make packaging more complex.

code
architecture

Most classes uses both the logger and the rconf. In general, I have not seen a good way of handling these "global objects" elegantly.

code
architecture

Rethink and shorten them.

code
architecture

Add support for config file(s) that can hold: * job/task parameters * rconf parameters * other stuff (e.g., auto-update kill switch? exec paths?) Clearly command line parameters should take precedence...

functionality
code
architecture

Only numpy is actually needed by everybody. Suggest to packagers to still include lxml and BeautifulSoup4, and hint at the possibility of including the full set of deps. Maybe create...

code
architecture

As a consequence of #137 , we would need a unified management of optional dependencies that are not installed (e.g., pafy if the user selects the download option, or tgt...

code
architecture

In theory ffmpeg/ffprobe could be avoided, if the input audio file is in WAV (RIFF) format. Audio format conversion could then be decoupled, and called only when needed. To be...

functionality
code
architecture