[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#688349: flite can't write to stdout (or any non-file, e.g. fifo)



Package: flite
Version: 1.4-release-6
Severity: important

flite is not able to write to stdout, which is very important when
trying to use it as part of a scripted toolchain.

For example, I wanted to have flite's generated wav data piped directly
into an ogg encoder. This works perfectly with most on-the-fly
text-to-speech systems, but not flite.

I tried every dirty trick (using "-" as the name of the output file (it
just makes a file called that), pointing it at a fifo, bash redirects to
/dev/stdout, /dev/fd/n after an "exec n>whatever", lots more things) but
to no avail. flite absolutely resists any attempt to pipe it's wav
output to anything but a file.

Obviously I could use libflite and write my own program to do just this
one thing, but it would be best if flite could be fixed to just work
like most programs and be able to output to stdout (or at least a
fifo!) in some simple way.

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (40, 'experimental')
Architecture: i386 (x86_64)

Kernel: Linux 3.4-trunk-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages flite depends on:
ii  dpkg          1.16.8
ii  install-info  4.13a.dfsg.1-10
ii  libasound2    1.0.25-4
ii  libc6         2.13-35
ii  libflite1     1.4-release-6

flite recommends no packages.

Versions of packages flite suggests:
ii  alsa-base  1.0.25+2+nmu2

-- no debconf information


Reply to: