All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0001210]: Exaudio produces noise on all speakers for 5.1 channels
Date: Fri, 24 Jun 2005 17:22:56 +0200	[thread overview]
Message-ID: <f4a4a2303a9e2dc409ba1600cbb1d614@bugtrack.alsa-project.org> (raw)


A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1210> 
======================================================================
Reported By:                andersin
Assigned To:                Clemens Ladisch
======================================================================
Project:                    ALSA - driver
Issue ID:                   1210
Category:                   USB - usb-audio
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     assigned
Distribution:               
Kernel Version:             
======================================================================
Date Submitted:             06-23-2005 23:54 CEST
Last Modified:              06-24-2005 17:22 CEST
======================================================================
Summary:                    Exaudio produces noise on all speakers for 5.1
channels
Description: 
I am using a soundblaster extigy with ALSA ver. 1.0.9b and am happy to say

that stereo sound works find and that all 6 speakers can produce some
sound.

With more than 2 channel output, I experience problems. speaker-test,
which 
works for 1 and 2 channels, results in a hissing/crackling for 3,5,6 
channels, which changes in pitch depending on the number of channels. For
4 
channels, it loops, producing the following output


speaker-test 0.0.8

Playback device is extigy
Stream parameters are 48000Hz, S16_LE, 4 channels
Using 16 octaves of pink noise
Rate set to 48000Hz (requested 48000Hz)
Buffer size range from 96 to 8192
Period size range from 48 to 4096
Periods = 4
Buffer time size 2525
To choose buffer_size = 8192
To choose period_size = 2048
was set period_size = 2048
was set buffer_size = 8192
Unable to set hw params for playback: Invalid argument
Setting of hwparams failed: Invalid argument
Rate set to 48000Hz (requested 48000Hz)
[ The "Rate set to ..." part is repeated continuously ]


Setting my capture device to mixer, I was able to record the output with 
arecord -c 6 -f dat -r 48000 /root/speaker-test-6ch.wav . The distortion
is 
still present when playing the file, forcing 2 channels in aplay.

In addition to using speaker test, I tried using the route plugin to
isolate 
the rear channels. When I route to any channel, I can hear the same output
on 
all 5 (not sure about Woofer) channels, no matter which channel I route
to. 
Here is the relevant setup:

pcm.route1      {
type            route;
slave.pcm       "extigy";
slave.channels  6;
ttable.0.0      1.0;
}

The music that I played had similar distortions like the one for speaker
test 
and played considerably slower than when player with 2 channels. Again I 
could record and replay the effect. The setup was slightly different in
order 
to route the stereo channels to all 6 speakers.

For routing with 4 slave channels, I get a failure (as expected), this
time 
with the output:

Playing WAVE 'test.wav' : Signed 16 bit Little Endian, Rate 48000 Hz,
Stereo
aplay: set_params:910: Unable to install hw params:
ACCESS:  RW_INTERLEAVED
FORMAT:  S16_LE
SUBFORMAT:  STD
SAMPLE_BITS: 16
FRAME_BITS: 32
CHANNELS: 2
RATE: 48000
PERIOD_TIME: (42666 42667)
PERIOD_SIZE: 2048
PERIOD_BYTES: 8192
PERIODS: 4
BUFFER_TIME: (170666 170667)
BUFFER_SIZE: 8192
BUFFER_BYTES: 32768
TICK_TIME: 1000

This is all the relevant bits that I can think of at the moment. Thank you
for 
reading this far. If anybody thinks it is important to get the recorded 
files, I am happy to sent them. I am grateful for any nudge on what I am 
doing wrong with my setup.

Christoph Burger-Scheidlin
======================================================================

----------------------------------------------------------------------
 andersin - 06-24-05 15:23 
----------------------------------------------------------------------
Sorry, I did not mention it. Everything with 2 speakers works fine.
Playback and Recording.

I assumed that the card did not support 4 speakers. As far as I understand
it, the channel routing mode can be used to select only 4 channels for
playback (and for that matter the routing plugin). If I run speaker-test
then the channel routing mode does turn off certain speakers when I cycle
through the different values (don't know if this is relevant though).

As far as the recording is concerned, I recorded from the "mixer" capture
setting and that should work no matter how many channels I set, shouldn't
it?



----------------------------------------------------------------------
 Clemens Ladisch - 06-24-05 17:22 
----------------------------------------------------------------------
When you're recording with the "mixer" setting, you probably get the two
front channels.

What I meant to say above was:  if you record two channels while playing
more than two channels, the distortion should still be present in the
first two channels you've recorded.  Is it?  Could you upload a _small_
test file?

Issue History
Date Modified  Username       Field                    Change              
======================================================================
06-23-05 23:54 andersin       New Issue                                    
06-24-05 09:21 Clemens LadischFile Added: alsa-lib-start-threshold-check.diff   
                
06-24-05 09:22 Clemens LadischFile Deleted: alsa-lib-start-threshold-check.diff 
                  
06-24-05 09:23 Clemens LadischNote Added: 0005205                          
06-24-05 10:14 andersin       File Added: stream0.txt                      
06-24-05 10:16 andersin       Note Added: 0005208                          
06-24-05 10:25 Clemens LadischNote Added: 0005209                          
06-24-05 13:38 andersin       Note Added: 0005218                          
06-24-05 15:23 andersin       Note Edited: 0005218                         
06-24-05 17:22 Clemens LadischNote Added: 0005239                          
======================================================================




-------------------------------------------------------
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-24 15:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-24 15:22 bugtrack [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-03-11 15:23 [ALSA - driver 0001210]: Exaudio produces noise on all speakers for 5.1 channels bugtrack
2005-08-23 23:03 bugtrack
2005-08-23 22:50 bugtrack
2005-06-24 15:47 bugtrack
2005-06-24 11:38 bugtrack
2005-06-24  8:25 bugtrack
2005-06-24  8:16 bugtrack
2005-06-24  7:23 bugtrack
2005-06-23 21:54 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=f4a4a2303a9e2dc409ba1600cbb1d614@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 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.