All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Davis <pbd@op.net>
To: Joern Nettingsmeier <nettings@folkwang-hochschule.de>
Cc: "alsa-devel@lists.sourceforge.net" <alsa-devel@lists.sourceforge.net>
Subject: Re: different nperiods for capture and playback when opening a device in duplex mode ?
Date: Wed, 10 Jul 2002 13:34:03 -0400	[thread overview]
Message-ID: <E17SLJx-0003au-00@usw-sf-list1.sourceforge.net> (raw)
In-Reply-To: Your message of "Wed, 10 Jul 2002 18:15:20 +0200." <3D2C5D98.18C4EC22@folkwang-hochschule.de>

>is it possible with alsa to use different settings for capture and
>playback, either periods or buffer size or both ?
>if yes, i might try and add that to jack, but since this is my first
>undertaking with alsa programming, i thought i'd ask first :)
>
>i got this idea from glame, which uses 2 and 4 periods and also
>different sizes and runs dropout-free. it does not however open the card
>full-duplex, but uses two threads that operate in halfduplex mode
>instead.

ALSA doesn't support "full duplex" to start with. You always have to
open two separate handles for this. Hence, the problem is 100% inside
of JACK's ALSA driver/client. It is written to use the same number of
periods in both directions. It would be possible to change this but it
would not be easy.

Your problems with JACK are caused by a different problem as far as I
can tell (so far), and GLAME's design won't help. More on the jack-dev
list later today (i hope).

--p


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Two, two, TWO treats in one.
http://thinkgeek.com/sf

      reply	other threads:[~2002-07-10 17:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-10 16:15 different nperiods for capture and playback when opening a device in duplex mode ? Joern Nettingsmeier
2002-07-10 17:34 ` Paul Davis [this message]

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=E17SLJx-0003au-00@usw-sf-list1.sourceforge.net \
    --to=pbd@op.net \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=nettings@folkwang-hochschule.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.