All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Sid Spry" <sid@aeam.us>
To: "Subhashini Rao Beerisetty" <subhashbeerisetty@gmail.com>,
	kernelnewbies <kernelnewbies@kernelnewbies.org>,
	alsa-devel@alsa-project.org, linux-usb@vger.kernel.org
Subject: Re: sound over USB
Date: Wed, 13 May 2020 10:22:18 -0500	[thread overview]
Message-ID: <bb16e374-3d9f-427c-8470-3542dc697fdb@www.fastmail.com> (raw)
In-Reply-To: <CAPY=qRRFV4SpNO5pb9vF=U95dbA_gN2ngP+vm34884NMk5q8gQ@mail.gmail.com>

On Tue, May 12, 2020, at 11:43 AM, Subhashini Rao Beerisetty wrote> 
>
> How do I use it for playing and recording an audio?
> 
> Basically first I want to gain knowledge on set of test cases I can
> run on ALSA and then learn ALSA kernel modules stuff including
> snd_usb_audio mdule.
> 
> So please guide me by providing related documentation/Steps.
> 

Hi, searching for an ALSA tutorial will get you far. However on a modern Linux distribution you will likely want to target pulseaudio. There are other libraries like RtAudio or PortAudio that may be easier to use and are cross platform.

ALSA seems to give the most reliable results when enumerating audio devices. This can be done when pulseaudio is installed. The pulseaudio results are harder to interpret.

In my experience, and not necessarily targeted at you, I have experienced massive difficulties getting RtAudio and PortAudio working in a reproducible way. ALSA is the most reliable but an unusual configuration, and pulseaudio is a hot complicated mess.


For what it's worth, the sound API on Linux is so pointlessly complex that I have, in the past, created a custom USB driver to avoid going through the sound API. It was easier to use libusb and get raw samples.

  parent reply	other threads:[~2020-05-13 15:23 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-12 16:43 sound over USB Subhashini Rao Beerisetty
2020-05-12 16:43 ` Subhashini Rao Beerisetty
2020-05-12 16:53 ` Greg KH
2020-05-12 16:53   ` Greg KH
2020-05-12 16:53   ` Greg KH
2020-05-13 13:02   ` Ricard Wanderlof
2020-05-13 13:02     ` Ricard Wanderlof
2020-05-13 13:02     ` Ricard Wanderlof
2020-05-13 15:22 ` Sid Spry [this message]
2020-05-13 15:22   ` Sid Spry
2020-05-14 13:42   ` Subhashini Rao Beerisetty
2020-05-14 13:42     ` Subhashini Rao Beerisetty
2020-05-14 13:42     ` Subhashini Rao Beerisetty

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=bb16e374-3d9f-427c-8470-3542dc697fdb@www.fastmail.com \
    --to=sid@aeam.us \
    --cc=alsa-devel@alsa-project.org \
    --cc=kernelnewbies@kernelnewbies.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=subhashbeerisetty@gmail.com \
    /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.