public inbox for alsa-devel@alsa-project.org
 help / color / mirror / Atom feed
From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - utils 0001304]: Speaker test hangs
Date: Tue, 9 Aug 2005 06:58:49 +0200	[thread overview]
Message-ID: <58a49ccbf6276b480e154bcf2927459c@bugtrack.alsa-project.org> (raw)


A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1304> 
======================================================================
Reported By:                herby
Assigned To:                
======================================================================
Project:                    ALSA - utils
Issue ID:                   1304
Category:                   speakertest
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     new
======================================================================
Date Submitted:             08-03-2005 02:46 CEST
Last Modified:              08-09-2005 06:58 CEST
======================================================================
Summary:                    Speaker test hangs
Description: 
After applying the patch to the library that took out the check for a
proper "start_threshold" (file .../alsa-lib/src/pcm/pcm.c around lines 834
or so), I attempted to try a speaker test again.  It hung right after
outputting "0 - Front Left".  I did an strace and the results are included
in the file attached.  I attempted to vary the sample rate (to 44.1 kHz)
with little luck.  The wierd thing is that I can execute 'aplay' (with the
default device) and get a '.wav' file to play nicely.  I can even get a
multi-channel (4 to be exact) ".wav" file to go thru 'aplay'.  Why
speaker-test doesn't work is beyond me.  The problem is that I appear to
use similar techniques in my own programming as speaker-test, and my
program doesen't do that well.  Being as how speaker-test IS part of ALSA,
I thought I would submit the bug report against it.

If other tests need be preformed, I'd be VERY happy to do them.
======================================================================

----------------------------------------------------------------------
 herby - 08-04-05 20:21 
----------------------------------------------------------------------
It seems that the problem is only on the Revolution 7.1 card, since it
hangs, and the motherboard audio (Via 8235) can generate the audio. 
Results of the tests:
<<<Revo 7.1 card test (card #0)>>>
[tsw ~]$ speaker-test -c2 -Dplug:front:0

speaker-test 0.0.8

Playback device is plug:front:0
Stream parameters are 48000Hz, S16_LE, 2 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
 0 - Front Left
<<<Hangs, aborted by interupt>>>

<<<Test using the Motherboard audio, card #1>>>
[tsw ~]$ speaker-test -c2 -Dplug:front:1

speaker-test 0.0.8

Playback device is plug:front:1
Stream parameters are 48000Hz, S16_LE, 2 channels
Using 16 octaves of pink noise
Rate set to 48000Hz (requested 48000Hz)
Buffer size range from 16 to 16384
Period size range from 8 to 8192
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
 1 - Front Right
Time per period = 5.649717
 0 - Front Left
 1 - Front Right

<<<Audio cycles as intended>>>

Maybe it is the interaction between the Revo 7.1 driver and the speaker
test.  Any more test to be run??

----------------------------------------------------------------------
 herby - 08-09-05 06:58 
----------------------------------------------------------------------
Now that I see the problem only happens on the Revo 7.1 card, do we
transfer it to that driver?  There are the attempts at trying speaker
test:
[tsw ~]$ speaker-test -c 2 -D plug:front:0  <<Attempting to use Revo 7.1
card>>

speaker-test 0.0.8

Playback device is plug:front:0
Stream parameters are 48000Hz, S16_LE, 2 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
 0 - Front Left
<interupt after waiting for sound to appear. No such luck!>


[tsw ~]$ speaker-test -c 2 -D plug:front:1   <<Using working motherboard
audio>>

speaker-test 0.0.8

Playback device is plug:front:1
Stream parameters are 48000Hz, S16_LE, 2 channels
Using 16 octaves of pink noise
Rate set to 48000Hz (requested 48000Hz)
Buffer size range from 16 to 16384
Period size range from 8 to 8192
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
 1 - Front Right
Time per period = 5.649939
 0 - Front Left
<interupted after success at generating white noise.  Works OK>

For reference:

[tsw ~]$ more /proc/asound/cards
0 [Revolution71   ]: ICE1724 - M Audio Revolution-7.1
                     M Audio Revolution-7.1 at 0xdc00, irq 10
1 [V8235          ]: VIA8233 - VIA 8235
                     VIA 8235 with VT1616i at 0xd400, irq 5

Obviously there is a problem in the Revolution-7.1 software.  Is there any
hope?
Has the Revo 7.1 driver changed from version 1.0.9b to the present??

I'd like to get the Revo driver functional, as I've got a project that
uses it
(all 8 channels it really should be called a Revo 8.0!).

Issue History
Date Modified  Username       Field                    Change              
======================================================================
08-03-05 02:46 herby          New Issue                                    
08-03-05 02:46 herby          File Added: speaker-trace                    
08-03-05 12:18 tiwai          Note Added: 0005621                          
08-04-05 03:21 herby          Note Added: 0005638                          
08-04-05 14:10 jcdutton       Note Added: 0005648                          
08-04-05 20:21 herby          Note Added: 0005652                          
08-09-05 06:58 herby          Note Added: 0005718                          
======================================================================




-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf

             reply	other threads:[~2005-08-09  4:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-09  4:58 bugtrack [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-12-31 21:07 [ALSA - utils 0001304]: Speaker test hangs bugtrack
2005-12-31 20:38 bugtrack
2005-12-30 22:24 bugtrack
2005-08-12 13:47 bugtrack
2005-08-12  6:12 bugtrack
2005-08-04 18:21 bugtrack
2005-08-04 12:10 bugtrack
2005-08-04  1:21 bugtrack
2005-08-03 10:18 bugtrack
2005-08-03  0:46 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=58a49ccbf6276b480e154bcf2927459c@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