From: Takashi Iwai <tiwai@suse.de>
To: tsw@johana.com
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Speaker test "features" request
Date: Wed, 22 Jun 2005 14:49:30 +0200 [thread overview]
Message-ID: <s5hoe9yblph.wl%tiwai@suse.de> (raw)
In-Reply-To: <20050622112617.57823.qmail@web60825.mail.yahoo.com>
At Wed, 22 Jun 2005 04:26:17 -0700 (PDT),
Tom Watson wrote:
>
> > Date: Wed, 22 Jun 2005 18:22:17 +0800
> > From: Raymond <rayau@netvigator.com>
>
> <<<deletia>>>
> >
> > I notice that there are female voice wav files in samples subdirectory.
> >
> > ls speaker-test/samples
> > Front_Center.wav Makefile Noise.wav Rear_Right.wav
> > Side_Right.wav
> > Front_Left.wav Makefile.am Rear_Center.wav sample_map.csv
> > Front_Right.wav Makefile.in Rear_Left.wav Side_Left.wav
> >
> >
> > Is there an option to use female voice instead of pink noise, sine wave ?
> >
>
> As noted in the next message (removed) this isn't supported yet. In doing
> many "more than 2 channel" tests I offer the following suggestions and
> observations for implementation of a voice channel identification:
> 1) Everyone calls the channels by different names
> 2) Many people don't speak English.
The texts are already i18nized on CVS. Provide an appropriate po file
for your locale. Also, we can store voice files in different
directories per locale (if any).
> 3) If you are poking around waiting for the identifiers to come back to
> the channel you are working on is a $%^&*%$#@ pain.
Will be solved when (6) is implemeneted?
> 4) Just call the channels "one" "two" "three", etc...
Doable, but I don't think we have much of this demand.
> 5) Put out an id map in text when the voice identifier starts that
> indicates the correspondence.
I think it's already so?
> 6) Voice ALL the channels at the same time. You could be feeding a mixer
> board (or other similar instrument) and desire to get everything setup.
> Most mixer boards have a "solo" feature which is helpful in this regard.
This would be nice as an option.
> 7) (MCP Comment) Female voice is nice. Takes the geek edge off of it all.
:)
> 8) This is a really nice utility to have around. It proves out the
> playback system.
> 9) Perhaps we can get a "professional voice" to do this. Fame and notoriety
> for the "Open source" voice. Anyone have any contacts?
These are welcome, of course :)
Takashi
-------------------------------------------------------
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
next prev parent reply other threads:[~2005-06-22 12:49 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 [this message]
2005-06-22 21:22 ` Dirk Jagdmann
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=s5hoe9yblph.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.