public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Volker Armin Hemmann <volkerarmin@googlemail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Typewriter sound
Date: Wed, 31 Aug 2011 17:54:15 +0200	[thread overview]
Message-ID: <1370152.yyKSa8dbEO@localhost> (raw)
In-Reply-To: <4E5E50C2.30900@gmail.com>

Am Mittwoch 31 August 2011, 17:18:26 schrieb Space Cake:
> 2010-08-17 21:34 keltezéssel, Albert Hopkins írta:
> > On Tue, 2010-08-17 at 20:43 +0200, meino.cramer@gmx.de wrote:
> >> Bill Longman <bill.longman@gmail.com> [10-08-17 20:16]:
> >>> On 08/17/2010 10:56 AM, Albert Hopkins wrote:
> >>>> On Tue, 2010-08-17 at 19:20 +0200, meino.cramer@gmx.de
> >>>> 
> >>>> wrote:
> >>>>> Hi,
> >>>>> 
> >>>>> on YouTube there was a Blender-2.5 tutorial with audio.
> >>>>> There was an interesting detail: While there were spoken
> >>>>> instructions one can hear one typing on its keyboard. Each
> >>>>> hit on one of the keys made the sound of an old typewriter
> >>>>> (no, it was not the sound of the legendary "IBM Model M"
> >>>>> keyboard ;) ).
> >>>>> 
> >>>>> How can I achieve this? What software can I use to make
> >>>>> this geeky feature to come true. Unfortunately I have no
> >>>>> idea, how to name this kind of what(?) ...
> >>>>> 
> >>>>> Thank you very much for any hint in advance! Best regards,
> >>>>> mcc
> >>>> 
> >>>> There probably a number of ways to do this.
> >>>> 
> >>>> A cheap and easy way would be to use xev to monitor a window
> >>>> and then pipe the stderr to a a program that waits for a
> >>>> keypress event and then plays an apropriate.
> >>>> 
> >>>> A less cheap way would be to have our program do what xev
> >>>> does instead of using a pipe.
> >>> 
> >>> Or you could set your X keyclick using xset.
> >> 
> >> Hi,
> >> 
> >> thanks a lot for your replies! :) Is there any program already,
> >> which does this? A daemon or...<insert missing words here>
> >> 
> >> Best regards, mcc
> > 
> > Well I found out that when you pass window id to xev it does not
> > trap keyboard presses per-sé.  But there is another way...
> > 
> > Anway the following is a quick hack (in python).  It pretty much
> > works except it also seems to trap mouse presses.  I got the .wav
> > file at http://www.soundjay.com/typewriter-sounds.html
> > 
> > I tried using 'xset c' but it basically does nothing for me.  My
> > guess is that it does work it basically sends the a BELL to the
> > console.
> > 
> > 
> > --- 8< CUT HERE
> > --------------------------------------------------- import sys
> > import subprocess
> > 
> > soundfile = 'typewriter-key-1.wav'
> > 
> > def main(): window_id = sys.argv[1] cmd = ['xev', '-id',
> > window_id]
> > 
> > p1 = subprocess.Popen(cmd, stdout=subprocess.PIPE) while True: line
> > = p1.stdout.readline() if line.find('atom 0x14d') > -1:
> > subprocess.Popen(['aplay', soundfile], stderr=open('/dev/null',
> > 'w'))
> > 
> > 
> > if __name__ == '__main__': main()
> 
> Guys, this is awesome :) Let's make an ebuild and put in portage :)
> 
> L:

why? 
man xset

 really guys. Why do it the long, hard and stupid way if there have been 
simple, built in solutions for longer than some of you live?

-- 
#163933



  parent reply	other threads:[~2011-08-31 15:56 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-17 17:20 [gentoo-user] Typewriter sound meino.cramer
2010-08-17 17:56 ` Albert Hopkins
2010-08-17 18:13   ` Bill Longman
2010-08-17 18:43     ` meino.cramer
2010-08-17 19:34       ` Albert Hopkins
2010-08-17 21:44         ` Mick
2010-08-17 23:11           ` Bill Longman
2011-08-31 15:18         ` Space Cake
2011-08-31 15:41           ` [gentoo-user] " Grant Edwards
2011-08-31 15:54           ` Volker Armin Hemmann [this message]
2011-08-31 16:20             ` [gentoo-user] " Space Cake
2011-08-31 16:27             ` [gentoo-user] " Grant Edwards
2011-08-31 16:49               ` Paul Hartman
2011-08-31 17:46                 ` Grant Edwards
2011-08-31 18:50                   ` Paul Hartman
2011-08-31 20:18                     ` Grant Edwards
2011-08-31 21:58                       ` Paul Hartman
2011-09-01  0:57                         ` Grant Edwards
2011-09-01  2:43                           ` Paul Hartman
2011-09-01 13:53                             ` Grant Edwards
2011-09-01 14:22                           ` Frank Steinmetzger
2011-09-01 18:58                             ` Mick
2011-09-01 16:36                           ` Volker Armin Hemmann
2011-09-01 19:11                             ` Grant Edwards
2011-09-04 12:55                       ` Alex Schuster
2010-08-17 22:14 ` [gentoo-user] " Paul Hartman
2010-08-17 22:47   ` meino.cramer
2010-08-18  3:42     ` Paul Hartman
2010-08-18  3:53       ` Dale
2010-08-18 13:45         ` [gentoo-user] " Grant Edwards
2010-08-18 15:56       ` [gentoo-user] " meino.cramer
2010-08-17 23:17   ` Albert Hopkins
2010-08-17 23:41     ` Albert Hopkins
2010-08-17 23:44       ` Albert Hopkins
2010-08-18 14:14         ` Stefan G. Weichinger
2010-08-18 15:10           ` Peter Ruskin
2010-08-18 16:46             ` Stefan G. Weichinger
2010-08-18 16:20         ` meino.cramer
2010-08-18 16:43           ` Albert Hopkins
2010-08-18 16:06   ` meino.cramer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1370152.yyKSa8dbEO@localhost \
    --to=volkerarmin@googlemail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox