After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 132777 - gnopernicus pitch decreases with prolonged output
gnopernicus pitch decreases with prolonged output
Status: VERIFIED INCOMPLETE
Product: gnopernicus
Classification: Deprecated
Component: speech
unspecified
Other Linux
: Normal minor
: ---
Assigned To: mp
mp
AP4
Depends on:
Blocks:
 
 
Reported: 2004-01-28 15:29 UTC by david.hawthorne
Modified: 2009-08-15 18:40 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description david.hawthorne 2004-01-28 15:29:07 UTC 
Currently running gnopernicus and gnome-speech from CVS HEAD 28 Jan.

Gnopernicus' pitch decreases gradually with a long string of output, like a
robot running out of batteries.

-launch gnopernicus(used freetts speech driver)
-untar a large tarball in verbose mode
.gnopernicus attempts to read all the terminal output
.as it does so, it's pitch gradually decreases

the frequency of such an event is low, but I'm finding it does happen.
Comment 1 korn 2004-01-28 18:24:29 UTC 
This is very likely a bug/issue in FreeTTS.  It may also be a side
effect of an intended feature - sentence prosidy.  When it next
happens, could you please note here what the string is?  We can test
that independently with FreeTTS and other engines.

Finally, I wonder if the priority is set correctly.  I think this is a
low priority bug.
Comment 2 remus draica 2004-02-14 10:59:06 UTC 
This bug seems to be identical with 133386. 

David, please try the patch proposed for bug 133386 and check if the
problem is still present.
Comment 3 david.hawthorne 2004-02-16 16:41:56 UTC 
with the patch applied, there is now no output from the watched.
However, I do hear an attempt to say 'slash' every few 15 seconds or
so throughout the extraction, so I'm presuming that each verbose line
of output is interrupting the next - so in effect it's virtually muted..
Comment 4 remus draica 2004-02-18 14:00:44 UTC 
The remaining issue is described in bug 133964.