From: James Courtier-Dutton <James@superbug.demon.co.uk>
To: Ed Wildgoose <lists@wildgooses.com>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Problem with RME 9632 and Plug
Date: Wed, 04 Aug 2004 14:35:17 +0100 [thread overview]
Message-ID: <4110E615.2090304@superbug.demon.co.uk> (raw)
In-Reply-To: <4110D9FF.0@wildgooses.com>
Ed Wildgoose wrote:
>
> I'm not sure what you are saying here. I have the source code in front
> of me in an editor, but I physically can't set the options correctly -
> the driver just rejects them?
>
> The issue is the heuristic - I appear to have to try for the period size
> first, then set the number of periods (fails if I do it the other way
> around), however, if I then discover the number of periods * period size
> is lower than I would like, I cant go and adjust these settings (alsa
> returns errors).
>
Why don't you use the alsa api more fully.
You can gather information about min/max period/buffer sizes before
setting any values.
This is not 100% certain to work, as alsa hardware contraints can be
extremely complicated if the hardware so desires.
But I do think that the setting of period_size/time, buffer_size/time
and periods has always been problematic in alsa.
Being able test different period and buffer sizes without having to
close/open the device would be a useful addition to the alsa api.
Cheers
James
-------------------------------------------------------
This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
one more big change to announce. We are now OSTG- Open Source Technology
Group. Come see the changes on the new OSTG site. www.ostg.com
next prev parent reply other threads:[~2004-08-04 13:35 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-03 13:46 Problem with RME 9632 and Plug Ed Wildgoose
2004-08-03 14:36 ` Paul Davis
2004-08-03 15:44 ` Ed Wildgoose
2004-08-03 16:21 ` Ed Wildgoose
2004-08-03 17:32 ` Paul Davis
2004-08-03 23:55 ` Ed Wildgoose
2004-08-04 0:18 ` Paul Davis
2004-08-04 7:39 ` Jaroslav Kysela
2004-08-04 9:35 ` Ed Wildgoose
2004-08-04 10:20 ` Jaroslav Kysela
2004-08-04 11:16 ` Ed Wildgoose
2004-08-04 12:24 ` Paul Davis
2004-08-04 12:43 ` Ed Wildgoose
2004-08-04 13:01 ` Paul Davis
2004-08-04 13:31 ` Ed Wildgoose
2004-08-04 15:13 ` Zsolt Barat
2004-08-04 15:03 ` Zsolt Barat
2004-08-04 15:24 ` Paul Davis
2004-08-04 13:35 ` James Courtier-Dutton [this message]
2004-08-04 9:44 ` Takashi Iwai
2004-08-04 9:55 ` Ed Wildgoose
2004-08-04 10:21 ` Ed Wildgoose
2004-08-04 10:20 ` Jaroslav Kysela
2004-08-04 10:27 ` Takashi Iwai
2004-08-04 10:56 ` Jaroslav Kysela
2004-08-04 11:15 ` Takashi Iwai
2004-08-04 10:30 ` Ed Wildgoose
2004-08-04 10:53 ` Jaroslav Kysela
2004-08-04 11:21 ` Ed Wildgoose
2004-08-04 9:52 ` Ed Wildgoose
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=4110E615.2090304@superbug.demon.co.uk \
--to=james@superbug.demon.co.uk \
--cc=alsa-devel@lists.sourceforge.net \
--cc=lists@wildgooses.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.