Page 1 of 1

Ubuntu install david no sound

PostPosted: Sat Mar 13, 2010 3:41 pm
by flesher
It looks like it installed, but I get not sound; also errors are noted; do I need to purchase license first?

The text to file worked great.
I'm going to purchase the license; as long as that works I'm fine with it.

**************************

Installing voice David...

Creating configuration...

Installing binaries...
Installing symbolic link to swift...
Installing man page...

Setting permissions...

Kill License Server
[: 251: unexpected operator
[: 251: unexpected operator
[: 251: unexpected operator

Testing the installed swift binary...
/opt/swift/bin/swift -o /dev/null 'hello world'

************************************************************
****************** Installation Completed Successfully!
************************************************************

PostPosted: Sun Mar 14, 2010 10:30 am
by AdamW
The voices should function identically whether they are licensed or not, with one exception: an unlicensed voice injects into the spoken stream a licensing reminder at the beginning (a rather long one) and a short one periodically thereafter. If the voice is not working, there is something wrong other than licensing.

From the looks of it, it would seem there is a problem in the shell script performing the installation. We have been informed that the newer ubuntu installations do not use bash as their default bourne shell installation. That might be the cause if /bin/sh is linked to anything other than bash, given that we know some of our scripts depend on bash syntax. We will fix that.

For now, please try to switch the first line of the install script from
#!/bin/sh
to
#!/bin/bash

and rerun it. That should fix the unknown operator. If it doesn't, please let us know.

As for the lack of voice out of the machine, are the OSS audio drivers installed. We are in the process of adding ALSA support but for now OSS is required, and possibly not installed by default.

License is installed now; your right; no effect but...

PostPosted: Sun Mar 14, 2010 11:55 am
by flesher
changing to bash:

Installing voice David...

Creating configuration...

Installing binaries...
Installing symbolic link to swift...
Installing man page...

Setting permissions...

Kill License Server

Testing the installed swift binary...
/opt/swift/bin/swift -o /dev/null 'hello world'
*******
In message log:
Mar 14 09:37:58 myMachineName kernel: [130555.273947] Inbound IN=eth0 OUT= MAC=00:30:48:7f:0a:66:00:02:72:81:2e:5f:08:00 SRC=80.203.53.101 DST=192.168.0.10 LEN=1400 TOS=0x00 PREC=0x00 TTL=104 ID=25211 DF PROTO=TCP SPT=60000 DPT=48367 WINDOW=65266 RES=0x00 ACK URGP=0
*****
Still no sound; I did close Firefox for test; I know that locks out festival.

Ubuntu 9.10 Karmic Koala x64; machine is Supermicro 7045A; Xeon 5450, 32 GB RAM

PostPosted: Wed Mar 17, 2010 7:47 am
by AdamW
A few commands to run to troubleshoot, reporting the result:

> swift --voices

> swift hello

and finally, what is the name of the installer tar you used?

troubleshoot

PostPosted: Wed Mar 17, 2010 11:28 am
by flesher
Swift command-line synthesis program
Version 5.1.0 of July 2008
Copyright (c) 2000-2006, Cepstral LLC.

Voice | Version | Lic? | Gender | Age | Language | Sample Rate
-----------|---------|------|--------|-----|------------------|------------
David | 5.1.0 | Yes | male | 30 | US English | 16000 Hz

swift hello; not sound; but I get this error:

Mar 17 09:18:59 servername kernel: [49833.536882] floppy0: data CRC error: track 0, head 0, sector 3, size 2

No idea why I'd get that error, unless you write to that device; I tried it a few times and I don't always get that error; so it might be unrelated.

Installer
Cepstral_David_x86-64-linux_5.1.0.tar.gz


I have two audio cards; one built in and the other is a Diamond 7.1; not that I think this is the problem; its seems to work fine; I can switch to Fedora 12 and try it there to see if its just this OS.

Update:
I tired this on Fedora 12; same thing; I get this error:
oss_aduio: failed to open audio device /dev/dsp

This does work on another machine running CentOS; so I know its not the program in general; it looks like a hardware issue; or perhaps a device driver issue.