GNOME Bugzilla – Bug 142839
Changing Absolute Value "pitch" does not take effect with Gnopernicus
Last modified: 2004-12-22 21:47:04 UTC
When trying to change the pitch value within the "edit absolute Voice Values window" there is no real time change. Moving the slider bar from 0 to 100 Hz you do not hear any difference. This is clearly a bug because the other two values Rate of word/min and Volume changes real time when moving their respective slider bars. Steps to recreate the problem. 1. Start gnopernicus with speech preference. 2. Select the voices tab within the "Speech Preference" window. 3. Select the "Edit Absolute" tab within the "Voices" window. 4. Check the box for pitch. 5. Move the slider back and forth and you will notice that there is change with the voice in regards to Pitch.
If you are on the slider bar and you press right arrow key/left arrow key to increase/decrease the pitch, when you release the key you should hear the difference. You should also see the new value in the spin button control (behavior required in bug 142842). But as long as you keep the arrow key pressed, you will not hear any changes. Gnopernicus has the same behavior in case of Value and Rate options, so there is no difference between the three options. Can you confirm this behavior ? If yes, this is not a bug.
Wayne DeAngelo, please see my previous comment and let me know what behavior are you seeing ?
Update, Yes Gnopernicus SHOULD behave the same for all 3 option, BUT at the build level of Gnome 2.6.1 the pitch option behaves differently. Stated above the pitch does not change if you move the slider with the right arrow key/left arrow key, EVEN after you release the pressed key. Note: the new value does change in the spin control window though. As stated above this clearly a bug.
It's been awhile, any update please?
Created attachment 30037 [details] [review] proposed patch this patch should fix the problem
Update, Dragan, what development build level will the patch be dropped in? I built a "garnome" development level which is has gnopernicus as 0.9.5 and still see the reported problem.
Hi, this patch is on CVS HEAD. Tomorow, there will be a new release of gnopernicus : 0.9.7 (I think). This release will contain the the patch I added in comment #5. After you test the new version, if the problem you noticed is still there please reopen this bug.
*** Bug 148552 has been marked as a duplicate of this bug. ***
I am running a garnome built with the nightly tarball of 07/20/04 which yields the gnopernicus level of 0.9.5 and still see the reported problem. Will build a new garnome level later this week to verify that this is fixed in gnopernicus 0.9.7. Reopening bug till I can verify
Update, I have a system running gnopernicus 0.9.7 and I'm still seeing the reported problem. Dana please verify what CVS head level the fix got drop into, thanks in advance Wayne
After compiling, did you run "make install". Otherwise, the new presentation xml files are not installed in proper place.
If you are using festival, then this may be bug 150523. Check if gnopernicus shows something like "Unable to find parameter" I am using freeTTS and everything is fine.
If gnopernicus can't access the parameter, it should "grey out" the UI component in the GUI, and should report the above warning "Unable to find parameter" via speech.
I agree with Bill. However, please do NOT try to fix this now.
Reopening defect.
wayne, please confirm which text-to-speech engine you are using. If you are using festival , then this bug is a duplicate of 150523.
Yes, I am using Festival, so this is a dup of 150523.
Thanks Wayne. *** This bug has been marked as a duplicate of 150523 ***
Update, Bill I noticed that you stated that this is a duplicate of 150523 BUT when you look at 150523, it states that this is a duplicate of this defect 142839. So in other words, these two defects 150523 and 142839 dup each other. There is no resolution for either defect. Also I have recreated this reported problem on the following level: Gnome 2.7.92 build 09/08/04 gnopernicus 0.9.10 Using Festival as our TTS I am reopening this defect for resolution.
Update: Bill I also need to explain that in your statement: ""Gnopernicus has the same behavior in case of Value and Rate options, so there is no difference between the three options."" in related bug 142842 is incorrect. I do see a difference between the three options, the rate and volume work fine, if you change the rate and volume, the change is "realtime" you can hear the change and its immediate. But with the pitch option, you do not hear the change even after you change the slider, even after you release the key as you state.
Wayne, why did you say at comment #19 "these two defects 150523 and 142839 dup each other" ? It's not true! 149839 has been marked as a duplicate of 150523, an UNCONFIRMED gnome-speech bug which will be eveluated and fixed. Please let this bug as a dup of 150523. Thanks! *** This bug has been marked as a duplicate of 150523 ***