All of lore.kernel.org
 help / color / mirror / Atom feed
From: Raymond <rayau@netvigator.com>
To: alsa-devel@lists.sourceforge.net
Subject: Re: Speaker-test improvements
Date: Thu, 23 Jun 2005 18:20:59 +0800	[thread overview]
Message-ID: <42BA8D0B.5060501@netvigator.com> (raw)
In-Reply-To: <s5hzmw0chyq.wl@alsa2.suse.de>


>>>Takashi Iwai <tiwai@suse.de> writes:
>>>
>>>
>>>>At Wed, 13 Apr 2005 21:02:31 +0100,
>>>>James Courtier-Dutton wrote:
>>>>
>>>>>Hi,
>>>>>
>>>>>I have got some voice samples saying things like "Front Right" etc. that
>>>>>I want the speaker-test program to output instead of the loud sine wave
>>>>>it currently does. The sine wave will stay there as an option as I find
>>>>>it useful for some things.
>>>>>
>>>>>The samples are 10 .wav files in 48khz mono S16_LE format.
>>>>>Where abouts should I put them in the CVS, and where abouts should they
>>>>>get installed to, so that speaker-test can find them?
>>>>

It seem most onboard audio (intel8x0,hda) have ".channels_min = 2".

You may need to merge the mono "Left" and "Right" wav to a stereo
left_right.wav


static snd_pcm_hardware_t snd_intel8x0_stream =
{
     .channels_min =        2,
     .channels_max =        2,
}


aplay -D hw:1,0 speaker-test/samples/*.wav
Playing WAVE 'speaker-test/samples/Front_Center.wav' : Signed 16 bit
Little Endian, Rate 48000 Hz, Mono
aplay: set_params:887: Channels count non available


aplay -Dplughw:1,0 speaker-test/samples/*.wav
Playing WAVE 'speaker-test/samples/Front_Left.wav' : Signed 16 bit
Little Endian, Rate 48000 Hz, Mono
Playing WAVE 'speaker-test/samples/Front_Right.wav' : Signed 16 bit
Little Endian, Rate 48000 Hz, Mono


>>
>>
>>I made up a sound file similar to this and it was quite helpful.  One of the
>>files had individual voices (one at a time) to identify the speakers, and being
>>with the proper 4-channel specifications for broadcast they were identified as
>>"left front", "right front", "left BACK" and "right BACK".  In doing so it
>>eliminated the abbreviation of "R" being both "rear" and "right" (not very
>>clear).
>>
>>Another test was having all of the channels identified "simultaneously",
>>usually in a loop.  This allowed me to play with mixer controls which always
>>get mixed up and get the correct things in the correct places.  When you hook
>>up sound cards and amplifiers and other external gear, it helps to have the
>>channel identified.  Some mixer controls on some cards fold the "back" channels
>>into the "front" channels, and then you need to poke around in your mixer
>>program ('alsamixer' is but one) to turn on/off "mutes" to get it right. 
> 
> 
> This sounds like a good idea.
> 
> 
>>Having the speaker test "loop" with spoken words was VERY helpful to me.
>>
>>The only "problem" I see is having the samples at one speed.  Sometimes it is
>>helpful to have the program send the sounds out at a specific speed to the ALSA
>>api, where it does further operations (another re-sampling).
> 
> 
> It should be fine when you specify the PCM with "plug" layer, e.g.
> 
> 	% speaker-test -Dplug:surround51 -c6
> 


# speaker-test -D hw:1,0

speaker-test 0.0.8

Playback device is hw:1,0
Stream parameters are 48000Hz, S16_LE, 1 channels
Using 16 octaves of pink noise
Channels count (1) not available for playbacks: Invalid argument
Setting of hwparams failed: Invalid argument


# speaker-test -Dplughw:1,0

speaker-test 0.0.8

Playback device is plughw:1,0
Stream parameters are 48000Hz, S16_LE, 1 channels
Using 16 octaves of pink noise
Rate set to 48000Hz (requested 48000Hz)
Buffer size range from 8 to 16384
Period size range from 8 to 16384
Periods = 4
Buffer time size 2525
To choose buffer_size = 15052
To choose period_size = 3763
was set period_size = 3763
was set buffer_size = 15052
  0 - Front Left
Time per period = 2.667026
  0 - Front Left
Time per period = 2.978708
  0 - Front Left




-------------------------------------------------------
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

  reply	other threads:[~2005-06-23 10:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-14 20:41 Speaker-test improvements Tom Watson
2005-04-15 13:01 ` Takashi Iwai
2005-06-23 10:20   ` Raymond [this message]
2005-06-24 15:16     ` Takashi Iwai
  -- strict thread matches above, loose matches on Subject: below --
2005-04-13 20:02 James Courtier-Dutton
2005-04-14 13:09 ` Takashi Iwai
2005-04-14 13:23   ` Måns Rullgård
2005-04-14 21:16   ` James Courtier-Dutton

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=42BA8D0B.5060501@netvigator.com \
    --to=rayau@netvigator.com \
    --cc=alsa-devel@lists.sourceforge.net \
    /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.