From: Dirk Jagdmann <doj@cubic.org>
To: tsw@johana.com
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Speaker test "features" request
Date: Wed, 22 Jun 2005 23:22:14 +0200 [thread overview]
Message-ID: <42B9D686.6060201@cubic.org> (raw)
In-Reply-To: <20050622112617.57823.qmail@web60825.mail.yahoo.com>
> 4) Just call the channels "one" "two" "three", etc...
I vote for such an option. I don't have any (standardized) x.1 speaker
configuration and assign all my channels as needed and refer to them by
numbers anyway.
> 6) Voice ALL the channels at the same time. You could be feeding a mixer
Does help debugging your cooked up wires/patchboard a lot.
> 9) Perhaps we can get a "professional voice" to do this. Fame and notoriety
> for the "Open source" voice. Anyone have any contacts?
The asterisk PhoneBox software includes samples in english from 1-20 and
then the 10'er until 90, 100's, 1000's, 1M. So a (clever) software can
construct numbers up to 10^9-1. As a start one could use them. Localized
samples of the digits and numbers can then be added later on.
--
---> doj / cubic
----> http://cubic.org/~doj
-----> http://llg.cubic.org
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
prev parent reply other threads:[~2005-06-22 21:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050622104624.B20CF12D0B@sc8-sf-spam2.sourceforge.net>
2005-06-22 11:26 ` Speaker test "features" request Tom Watson
2005-06-22 12:49 ` Takashi Iwai
2005-06-22 21:22 ` Dirk Jagdmann [this message]
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=42B9D686.6060201@cubic.org \
--to=doj@cubic.org \
--cc=alsa-devel@lists.sourceforge.net \
--cc=tsw@johana.com \
/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