GoogleCodeArchives / marave

Automatically exported from code.google.com/p/marave
GNU General Public License v2.0
0 stars 0 forks source link

Delayed keyclick sounds #80

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Typing
2.
3.

What is the expected output? What do you see instead?
Clicks should be in time with the keyboard.

What version of the product are you using? On what operating system?
0.7.2, on ArchLinux 64 bit, compiled from AUR

Please provide any additional information below.
It also doesn't find opengl when I start it with the --opengl option. I
don't know if the two problems are related.

Original issue reported on code.google.com by karl.sch...@gmail.com on 4 Mar 2010 at 9:07

GoogleCodeExporter commented 9 years ago
The opengl problem is a bug in Arch's PyQt package, it doesn't build that 
module. I had 
reported it in flyspray but it seems to be gone (or I just can't find it).

Some extra questions:

Is this delayed click problem noticeable if you click slowly or only if you 
click quickly?
What phonon bakend are you using?

Original comment by roberto.alsina on 5 Mar 2010 at 8:39

GoogleCodeExporter commented 9 years ago
Ok, I was using phonon-gstreamer, but I changed it to phonon-xine, and it 
worked much 
better, but still a little slower than I can type. Before, when I used phonon-
gstreamer, the clicks were so slow as to be completely unusable.

I also downloaded a few very short click sounds, which seemed to help.

I'm going to try phonon-mplayer to see if it is any better.

Original comment by karl.sch...@gmail.com on 5 Mar 2010 at 9:37

GoogleCodeExporter commented 9 years ago
I use the xine backend, gstreamer was awfully laggy. Coud you try r448? I think 
I may 
have decreased the latency for the clicks a bit.

Original comment by roberto.alsina on 6 Mar 2010 at 1:42

GoogleCodeExporter commented 9 years ago
It is much better with the latest svn checkout.

A problem with the clicks: it makes noise on every key pressed. With a real
typewriter, it wouldn't make any noise when the SHIFT key or the CTRL key or 
anything
similar was pressed. But this is a minor point, since an old IBM clicky keyboard
would have made sounds when those keys were pressed.

Keep up the good work!

Original comment by karl.sch...@gmail.com on 7 Mar 2010 at 2:06

GoogleCodeExporter commented 9 years ago
Cool :-)

I agree shift and click shouldn't click. I'll take a look at that.

I'm closing this issue now.

Original comment by roberto.alsina on 7 Mar 2010 at 12:03