All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jaroslav Kysela <perex@suse.cz>
To: Takashi Iwai <tiwai@suse.de>
Cc: Paul Davis <pbd@op.net>,
	"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: double speed (ADAT), and hw params ordering
Date: Sat, 20 Jul 2002 08:54:18 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.33.0207200851280.809-100000@pnote.perex-int.cz> (raw)
In-Reply-To: <s5hlm88q9u1.wl@alsa2.suse.de>

On Fri, 19 Jul 2002, Takashi Iwai wrote:

> At Thu, 18 Jul 2002 14:58:07 -0400,
> Paul Davis wrote:
> > 
> > i've been wondering what to do about setting sample rates in the
> > hammerfall and h-dsp drivers. fernando and gary from CCRMA have made
> > the excellent suggestion that rather than have the driver pretend that
> > all rates are available all the time, as it currently does, that we
> > have a control switch to go between regular rates and the "double
> > speed" or "bitsplit" rates (64kHz-96kHz) which reduce the channel
> > count.  i think this is an excellent idea. you would not be able to
> > use the switch while the device was open. when you opened it, you
> > would find (for example) a device with 14 channels (12 ADAT plus 2
> > SPDIF) at 64-96kHz or 26 channels (24 ADAT+2 SPDIF) at 32-48kHz.
>  
> i vote for this idea.

Paul, what's wrong to offer all possible configurations? Could

> > if anyone objects to this model, please let me know. right now, its
> > more or less impossible to get access to the higher rates.
> > 
> > on a related note, although the above suggestion will fix this
> > particular problem, it seems that it might be wise to consider adding
> > a parameter order information field to the driver API, so that drivers
> > can say "you have to set param P first, then param N, then param
> > O". the default would obviously be "don't care", but for devices that
> > lose certain capabilities when certain parameters are set, it would
> > make things very much easier.
> 
> agreed that it's good to have such one.
> but how to implement this?
> from the design of hw_constraint, i don't think it's so easy...
> 
> 
> Takashi
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/alsa-devel
> 

						Jaroslav

-----
Jaroslav Kysela <perex@suse.cz>
Linux Kernel Sound Maintainer
ALSA Project  http://www.alsa-project.org
SuSE Linux    http://www.suse.com



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

  reply	other threads:[~2002-07-20  6:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-18 18:58 double speed (ADAT), and hw params ordering Paul Davis
2002-07-19 10:40 ` Takashi Iwai
2002-07-20  6:54   ` Jaroslav Kysela [this message]
2002-07-20  6:57   ` Jaroslav Kysela
2002-07-20 19:20     ` (no subject) Fernando Pablo Lopez-Lezcano
2002-07-20 23:04       ` Abramo Bagnara
2002-07-21  8:28       ` your mail Jaroslav Kysela
2002-07-21 18:56       ` hdsp channel/sample rate issues Gary Scavone

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=Pine.LNX.4.33.0207200851280.809-100000@pnote.perex-int.cz \
    --to=perex@suse.cz \
    --cc=alsa-devel@alsa-project.org \
    --cc=pbd@op.net \
    --cc=tiwai@suse.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.