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: Sun, 22 Jan 2006 17:46:49 -0500	[thread overview]
Message-ID: <1137970009.1354.2.camel@mindpipe> (raw)
In-Reply-To: <43E897D5-9150-4960-8946-F6760B627283@caiaq.de>

On Sun, 2006-01-22 at 23:39 +0100, Daniel Mack wrote:
> Hi all,
> 
> I'm somehow confused about is the relationship between
> 
> 	- the number of registered snd_pcm_t instances
> 	- the number of substreams (4th and 5th param to snd_pcm_new()) and
> 	- the value of channels_min, channels_max in my snd_pcm_hardware_t
> 	  struct
> 

These should be set to reflect the capabilities of the hardware.
alsa-lib takes care of translating various formats and channel counts to
something the hardware can understand.  You don't have to worry about it
in the driver.

Substreams are only relevant if your device supports hardware mixing.

> If the device has multiple stereo input and outputs, where and how do I
> note that? Is it up to the caller how many streams are actually read/ 
> written?
> The hardware is not capable of only using some of the hardware channels,
> so I would have to throw away data after reception and fake data when  
> sending
> the stream, repectively.
> 
> Also, does a driver need to take care about supporting as much data  
> formats
> as possible (16/24/32 bits, LE/BE, ...)? Or is there any layer taking  
> care
> about proper conversion? And if there is such a layer, does any tool  
> make
> use of that? At least, aplay refused to play a big-endian wave file thru
> a device which only supports little-endian data transport according  
> to the
> snd_pcm_hardware_t struct.
> 
> I couldn't find any comprehensive information about that.
> 

See above - alsa-lib handles all these details for you, all you need to
consider when writing the driver is what the hardware supports.

> Thanks for any hint.
> Again, please Cc: me personally in replies, I'm still not subscribed.
> 
> Greets,
> Daniel
> 
> 
> 
> -------------------------------------------------------
> 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
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/alsa-devel
> 



-------------------------------------------------------
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-22 22:46 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 [this message]
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

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=1137970009.1354.2.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.