All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Jaroslav Kysela <perex@suse.cz>
Cc: Paul Davis <paul@linuxaudiosystems.com>,
	Ed Wildgoose <lists@wildgooses.com>,
	alsa-devel@lists.sourceforge.net
Subject: Re: Problem with RME 9632 and Plug
Date: Wed, 04 Aug 2004 13:15:49 +0200	[thread overview]
Message-ID: <s5h1xinqhlm.wl@alsa2.suse.de> (raw)
In-Reply-To: <Pine.LNX.4.58.0408041254060.1857@pnote.perex-int.cz>

At Wed, 4 Aug 2004 12:56:28 +0200 (CEST),
Jaroslav wrote:
> 
> On Wed, 4 Aug 2004, Takashi Iwai wrote:
> 
> > Well, HDSP needs at least 14 non-interleaved channels, so we'll need
> > anyway the conversion for normal apps like mplayer.  Then no external
> > timinig source would be needed.
> 
> I don't undestand this. As far as I know, RME cards have 64kB ring buffer 
> for all voices and the two periods constraint is for all voices. Thus 
> there is no correlation between the used channel count and period size.
> The timing is same.

I mean, we need anyway convert the format and the interleave ->
non-interleave in this case.  In comparison with this, introducing an
intermedate buffer with an arbitrary size doesn't influence on the
performance so much.

I don't think to do this in plug as default.  But it would be nice to
have this layer for devices with the limited periods and/or buffer
size (of course only if the extra data transfer doesn't matter).


Takashi


-------------------------------------------------------
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

  reply	other threads:[~2004-08-04 11:15 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
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 [this message]
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=s5h1xinqhlm.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=lists@wildgooses.com \
    --cc=paul@linuxaudiosystems.com \
    --cc=perex@suse.cz \
    /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.