public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Albert Hopkins <marduk@letterboxes.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Typewriter sound
Date: Tue, 17 Aug 2010 13:56:03 -0400	[thread overview]
Message-ID: <1282067763.451766.3.camel@paska> (raw)
In-Reply-To: <20100817172005.GA5110@solfire>

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.




  reply	other threads:[~2010-08-17 18:05 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 [this message]
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           ` [gentoo-user] " Volker Armin Hemmann
2011-08-31 16:20             ` 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=1282067763.451766.3.camel@paska \
    --to=marduk@letterboxes.org \
    --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