Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - utils 0001174]: Speaker Test fails with error message(s) from alsa lib.  "problem for start_threshold"
Date: Mon, 13 Jun 2005 19:55:18 +0200	[thread overview]
Message-ID: <d156d3a8a2f88cf32f1781e1e623fec4@bugtrack.alsa-project.org> (raw)


A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1174> 
======================================================================
Reported By:                herby
Assigned To:                
======================================================================
Project:                    ALSA - utils
Issue ID:                   1174
Category:                   speakertest
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     new
======================================================================
Date Submitted:             06-09-2005 00:42 CEST
Last Modified:              06-13-2005 19:55 CEST
======================================================================
Summary:                    Speaker Test fails with error message(s) from alsa
lib.  "problem for start_threshold"
Description: 
Running speaker test gets me:
>>>
speaker-test 0.0.8

Playback device is plughw:0,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 16 to 32768
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 = 3764
was set buffer_size = 15052
ALSA lib pcm.c:824:(snd_pcm_sw_params) snd_pcm_sw_params:
params->avail_min problem for start_threshold
Unable to set sw params for playback: Invalid argument
Setting of swparams failed: Invalid argument
<<<
======================================================================

----------------------------------------------------------------------
 herby - 06-13-05 19:55 
----------------------------------------------------------------------
Is this a problem with the library, My interface card (Revolution 7.1), my
(simple) /etc/asound.conf, or with (I doubt) speaker-test?  Perhaps it
should be in a different catagory.  I have working speaker tests in older
versions, and (I assume) the current versions of others.

Issue History
Date Modified  Username       Field                    Change              
======================================================================
06-09-05 00:42 herby          New Issue                                    
06-13-05 19:49 herby          Issue Monitored: herby                       
06-13-05 19:55 herby          Note Added: 0005013                          
======================================================================




-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.  How far can you shotput
a projector? How fast can you ride your desk chair down the office luge track?
If you want to score the big prize, get to know the little guy.  
Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20

             reply	other threads:[~2005-06-13 17:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-13 17:55 bugtrack [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-06-23 10:06 [ALSA - utils 0001174]: Speaker Test fails with error message(s) from alsa lib. "problem for start_threshold" bugtrack
2005-06-22  9:39 bugtrack
2005-06-22 10:22 ` Raymond
2005-06-22  8:19 bugtrack
2005-06-15 12:27 bugtrack
2005-06-08 22:42 bugtrack

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=d156d3a8a2f88cf32f1781e1e623fec4@bugtrack.alsa-project.org \
    --to=bugtrack@alsa-project.org \
    --cc=alsa-devel@alsa-project.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