Saving Settings?

Saving Settings?

[Hart Larry]

Well I tried changing settings in the /etc/speakup/dectlk directory, but 
obviously just editing with nano won't just save-and-make them affective.
OK, here's the strange part, now when I type a capital letter, each letter is 
surrounded by 2  d  so typing cap f  would say dfd  no pitch changes, even when 
I changed values in capstart-and-stop.
Seemed that a while ago if you changed a parameter-and-it were out-of-range, it 
would mention its alowd values.
I also thought there were some help system for these files?
And lastly, I was most surprised that I type man speakup  and there are no 
entries.
Really I wish I could say any of the DecTalk issues had become better, but 
still even after an upgrade to FC9 and new colonels, still, seemingly when we 
encounter case changes, the pitch-and-rate get knocked down, I must alter the 
values by 1 to fixit, but even when I boot the machine, the pitch is set on 81 
instead of 141, the rate is 10 instead of 7.
Thanks in advance for any suggestions
Hart

Re: Saving Settings?

[Gregory Nowak]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Sun, Aug 24, 2008 at 06:33:51PM -0700, Hart Larry wrote:
> Well I tried changing settings in the /etc/speakup/dectlk directory, but  
> obviously just editing with nano won't just save-and-make them affective.

Obviously not. You need to do:
speakupconf load
after changing something in /etc/speakup/synth_name, in order for it
to take effect.

> Seemed that a while ago if you changed a parameter-and-it were 
> out-of-range, it would mention its alowd values.

It still does. If you didn't get an error, then your value must have
been correct. Whether you actually see the effects of the new value is
a different matter, but I just checked to be sure, and you are still
told what the valid range for a parameter is if you've put in the
wrong value.

> I also thought there were some help system for these files?

There isn't a help system for the speakup parameters as far as I know
specifically, but there is the general speakup help system which you
can access with speakup_key+f1.

> And lastly, I was most surprised that I type man speakup  and there are 
> no entries.

Why should there be? I wasn't aware of anyone having written man pages
for speakup.

Greg


- -- 
web site: http://www.romuald.net.eu.org
gpg public key: http://www.romuald.net.eu.org/pubkey.asc
skype: gregn1
(authorization required, add me to your contacts list first)

- --
Free domains: http://www.eu.org/ or mail dns-manager@EU.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkiyKDwACgkQ7s9z/XlyUyBSAgCgo5rpxgYgN02BhmfaKYAS6ING
LkMAoIb83Q3O6ImaGy/W/ItrRW28mT1z
=joPt
-----END PGP SIGNATURE-----

Re: Saving Settings?

[Tony Baechler]

Gregory Nowak wrote:
>> Seemed that a while ago if you changed a parameter-and-it were 
>> out-of-range, it would mention its alowd values.
>>     
>
> It still does. If you didn't get an error, then your value must have
> been correct. Whether you actually see the effects of the new value is
> a different matter, but I just checked to be sure, and you are still
> told what the valid range for a parameter is if you've put in the
> wrong value.
>   



Hmm, that's very interesting.  I have tried this with the 3.0.2 
20080517, 3.0.3 20080724 and my own git pull from earlier in August.  I 
can write anything I want to the files in /sys/module/speakup/parameters 
and I get no errors.  I thought the same as you, but it left the value 
as it was before, not what I put in.  I was playing with the 
trigger_time as per Samuel's suggestion.  I had no idea what the allowed 
range was so I just started echoing numbers.  I could echo 999 
 >trigger_time and I got no error, but "cat trigger_time" gave me 25 or 
something like that.  If I echoed 0, it still remained at 25.  I finally 
discovered from trial and error that 10 seemed to be about the lowest I 
could go without getting errors.  Maybe for pitch, rate, and volume it 
works better.  On the other hand, if I use the Speakup keys to adjust 
rate and volume, it beeps when it hits the max rate and wraps around to 
0 after it hits volume 9.  I only discovered that by accident because I 
was using the 3.0.2 20080517 version with the bug not letting me write 
to the parameters files directly.

Re: Saving Settings?

[Gregory Nowak]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Mon, Aug 25, 2008 at 03:00:42AM -0700, Tony Baechler wrote:
> Hmm, that's very interesting.  I have tried this with the 3.0.2  
> 20080517, 3.0.3 20080724 and my own git pull from earlier in August.  I  
> can write anything I want to the files in /sys/module/speakup/parameters  
> and I get no errors.  I thought the same as you, but it left the value  
> as it was before, not what I put in.  I was playing with the  
> trigger_time as per Samuel's suggestion.  I had no idea what the allowed  
> range was so I just started echoing numbers.  I could echo 999  
> >trigger_time and I got no error, but "cat trigger_time" gave me 25 or  
> something like that.  If I echoed 0, it still remained at 25.  I finally  
> discovered from trial and error that 10 seemed to be about the lowest I  
> could go without getting errors.  Maybe for pitch, rate, and volume it  
> works better.

bookpc:/sys/module/speakup/parameters# cat version
Speakup version 3.0.3
dtlk synthesizer driver version 2.6

bookpc:/sys/module/speakup/parameters# cat trigger_time
30
bookpc:/sys/module/speakup/parameters# echo 999 >trigger_time
bookpc:/sys/module/speakup/parameters# cat trigger_time
999
bookpc:/sys/module/speakup/parameters# echo 30 >trigger_time
bookpc:/sys/module/speakup/parameters# echo 100000 >trigger_time
value for trigger_time out of range, expect 10 to 2000
bookpc:/sys/module/speakup/parameters# cat trigger_time
30
bookpc:/sys/module/speakup/parameters# cat vol
1
bookpc:/sys/module/speakup/parameters# echo 500 >vol
value for vol out of range, expect 0 to 9
bookpc:/sys/module/speakup/parameters# cat rate
9
bookpc:/sys/module/speakup/parameters# echo 500 >rate
value for rate out of range, expect 0 to 9
bookpc:/sys/module/speakup/parameters# cat pitch
50
bookpc:/sys/module/speakup/parameters# echo 500 >pitch
value for pitch out of range, expect 0 to 99
bookpc:/sys/module/speakup/parameters# cat pitch
50
bookpc:/sys/module/speakup/parameters# echo 80 >pitch
bookpc:/sys/module/speakup/parameters# cat pitch
80
bookpc:/sys/module/speakup/parameters# echo 20 >pitch
bookpc:/sys/module/speakup/parameters# cat pitch
20
bookpc:/sys/module/speakup/parameters# echo 50 >pitch
bookpc:/sys/module/speakup/parameters# cat pitch
50


> On the other hand, if I use the Speakup keys to adjust  
> rate and volume, it beeps when it hits the max rate and wraps around to  
> 0 after it hits volume 9.

That's not what happens for me, it works like it always used to
(I.E. when I go to volume 9, the max, it just beeps, and stays there),
same is true for the rate. The git-pull I'm using now was done 2-3
weeks ago I think.

Greg


- -- 
web site: http://www.romuald.net.eu.org
gpg public key: http://www.romuald.net.eu.org/pubkey.asc
skype: gregn1
(authorization required, add me to your contacts list first)

- --
Free domains: http://www.eu.org/ or mail dns-manager@EU.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkiy9GoACgkQ7s9z/XlyUyC2hQCfcGOyw5zeoCWUJWtoiIUsgl68
hkoAn2sJHJO9hOjww/VHdkpO94w/zj2O
=cOTk
-----END PGP SIGNATURE-----

Re: Saving Settings?

[Tony Baechler]

Gregory Nowak wrote:
> sys/module/speakup/parameters# cat version
> Speakup version 3.0.3
> dtlk synthesizer driver version 2.6
>   



Hi,

Interesting.  I believe you, but I didn't get that error message about 
values out of range.  It would be helpful if the version included the 
date like it used to in old cvs versions.  I don't use the dtlk driver, 
but the version of the ltlk driver I'm using from my latest git pull is 
2.7.  I can find the exact date of my git pull if necessary, but it 
would be nice to have the date in the version output.  I have at least 
two different sets of source on my system which are both 3.0.3 but are 
obviously from different dates.  I'll try again and see if I was mistaken.