All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: Daniel Mack <daniel@caiaq.de>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: some questions regarding multichannel devices
Date: Mon, 23 Jan 2006 11:36:17 -0500	[thread overview]
Message-ID: <1138034178.1354.28.camel@mindpipe> (raw)
In-Reply-To: <B3B8437F-3C75-479C-9F0B-0C5DB07C1E52@caiaq.de>

On Mon, 2006-01-23 at 13:35 +0100, Daniel Mack wrote:
> Hi Lee,
> 
> On Jan 23, 2006, at 1:09 AM, Lee Revell wrote:
> > Look at some existing drivers for details or the "Writing an ALSA
> > driver" document.
> 
> I read that. But besides the fact that it seems to be somewhat
> outdated ('struct snd_pcm' vs. 'snd_pcm_t' confusion all over
> the place), I couldn't find this issue explained. Thanks for
> the hint.
> 

You must be looking at an old version of the document or ALSA.  The
typedefs were removed from the ALSA code. 

> > You have to use "aplay -d plughw:0", not "aplay -d hw:0".
> 
> I guess you mean '-D', not '-d'? Unfortunately, This also does
> not help. I still get:
> 
> $ aplay -D plughw:0 test.wav
> Playing WAVE 'test.wav' : Signed 16 bit Little Endian, Rate 44100 Hz,  
> Stereo
> aplay: set_params:935: Unable to install hw params:
> ACCESS:  RW_INTERLEAVED
> FORMAT:  S16_LE
> SUBFORMAT:  STD
> SAMPLE_BITS: 16
> FRAME_BITS: 32
> CHANNELS: 2
> RATE: 44100
> PERIOD_TIME: (46439 46440)
> PERIOD_SIZE: 2048
> PERIOD_BYTES: 8192
> PERIODS: 4
> BUFFER_TIME: (185759 185760)
> BUFFER_SIZE: 8192
> BUFFER_BYTES: 32768
> TICK_TIME: 4000
> 
> and I suspect the S16_LE to be the reason. My snd_pcm_hardware_t looks
> like this:
> 

It should be a struct snd_pcm_hardware, upgrade your ALSA version.

> {
>          .info           = (SNDRV_PCM_INFO_MMAP |  
> SNDRV_PCM_INFO_DOUBLE | SNDRV_PCM_INFO_INTERLEAVED |
>                             SNDRV_PCM_INFO_BLOCK_TRANSFER),
>          .formats        = SNDRV_PCM_FMTBIT_S24_BE |  
> SNDRV_PCM_FMTBIT_S16_BE,
>          .rates          = (SNDRV_PCM_RATE_44100 |  
> SNDRV_PCM_RATE_48000 |
>                             SNDRV_PCM_RATE_96000 |  
> SNDRV_PCM_RATE_192000),
>          .rate_min       = 44100,
>          .rate_max       = 192000,
>          .channels_min   = 2,
>          .channels_max   = 2,
>          .buffer_bytes_max = 32768,
>          .period_bytes_min = 4096,
>          .period_bytes_max = 32768,
>          .periods_min    = 1,
>          .periods_max    = 1024,
> };
> 
> I have *no* ~/.asoundrc and no special entries about my hardware in
> /etc/asound* or /usr/share/alsa/*/*.
> 
> What do I have to do to get the glue logic working?
> 

AFAICT this should work... maybe someone else on the list can help.

Lee



-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642

      reply	other threads:[~2006-01-23 16:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-22 22:39 some questions regarding multichannel devices Daniel Mack
2006-01-22 22:46 ` Lee Revell
2006-01-22 23:33   ` Daniel Mack
2006-01-23  0:09     ` Lee Revell
2006-01-23 12:35       ` Daniel Mack
2006-01-23 16:36         ` Lee Revell [this message]

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=1138034178.1354.28.camel@mindpipe \
    --to=rlrevell@joe-job.com \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=daniel@caiaq.de \
    /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.