All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: latency.c: some feature requests
Date: Sat, 27 Nov 2004 23:58:14 -0500	[thread overview]
Message-ID: <1101617894.21427.9.camel@krustophenia.net> (raw)

While trying to use latency.c to test my full duplex device for the
emu10k1 driver I have found some problems with it.

The first thing that doesn't work is that latency.c sets the sample rate
to 22050Hz.  Both of my hw devices only support 48000Hz.  This is fixed
by not setting the sample rate at all, causing it to default to the
correct rate.

I also need the capture device interleaved and the playback device
noninterleaved.  latency.c does not support this at all, it just assumes
that all hardware supports interleaved format.

I thought about adding command line options but it should just do the
right thing by default because my hw devices only support one sample
rate and one access type.

Anyway since the alsa documentation constantly refers to this file,
sometimes in lieu of any other documentation, it really needs to be more
flexible.

-- 
Lee Revell <rlrevell@joe-job.com>



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/

             reply	other threads:[~2004-11-28  4:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-28  4:58 Lee Revell [this message]
2004-11-28 11:37 ` latency.c: some feature requests Jaroslav Kysela
2004-11-28 18:37   ` Lee Revell
2004-11-28 18:44     ` Jaroslav Kysela
2004-11-28 18:49       ` Lee Revell
2004-11-28 18:57         ` Jaroslav Kysela
2004-11-28 21:32       ` Lee Revell
2004-11-29 12:23         ` Jaroslav Kysela

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=1101617894.21427.9.camel@krustophenia.net \
    --to=rlrevell@joe-job.com \
    --cc=alsa-devel@lists.sourceforge.net \
    /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.